Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - noelBlanc

Pages: [1] 2 3 ... 5
Hello JFX,
Thank you very much. Merci beaucoup.
My ask was about the tools you use for find it
And i understand that it's only your experience of programmer  that puts you on the track of the solution.
I also understand that this only sendmessage is not enough for you, because you are in front of many différents contexts.
Once again, thank you for taking the time to answer me

In microWinpeBuilder context, I use this PS attached script with a GUI to change screen resolution with your tips. It's OK for me.

Hello JFX,
Thank you very much to share your code .
I hope you understand my poor English, i am trying without translator.

May i ask you an other question? How do you find the need of the "sendmessage WM_SETTINGCHANGE" ?

I think i don't use the good tool or good method to investigate. I try spy++ in winpe without result. On internet, i founded only reference to "WM_ChangeDisplay".
Thanks again

Note : i'll test more but i think that WM_SETTINGCHANGE is the only one msg  needed in "my winpe" when changing screen resolution.

Bonsoir ChrisR,

Mais comment JFX a t-il bien pu trouver qu'il fallait envoyer un WM_DISPLAYCHANGE lors de la réception d'un WM_SETTINGCHANGE  ?
Ca marche !

How does JFX find that to adapt task bar on the desktop (explorer), it needs to send WM_DISPLAYCHANGE  after system sends WM_SETTINGCHANGE ?
And why winpe doesn't do that?
Many questions without response, i suppose.

I'll put scripts Ps for anyone can see by itself how to change the screen resolution from winpe, dynamically and manually.


I play with "ChangeResolution" to modify width and height of the screen in PS for Winpe.

Msdn says that the WM_DISPLAYCHANGE  is sent to all windows when the display resolution has changed.
And here, Msdn says "When the display mode is changed dynamically, the WM_DISPLAYCHANGE message is sent to all running applications with the following message parameters." But with my PS script, the desktop don't adapte itself. I must kill the task explorer.exe and launch again for a good desktop.

If someone knows the solution, please, says to me.

@Lancelot : thank you, you are right.
A space was added by the translator at the begining of the name. I have a bad habit to rename by adding a "-" at the beginning of the name and not change the extension. I'll change this very bad habit in 2017.

happy new year 2017 !


Only with 1607 build 14393 :
In the case of a boot from a VHD mode "flat" (from a VM hyperV or from USB disk), the session "Administrator" does not open.

Rename Windows.UI.Logon.dll to - Windows.UI.Logon.dll

In the current state of the scripts, it is possible to create a file x:\noAdm which prohibits the launch of "tsdiscon.exe". We can do all the necessary investigations before  to launch tsdiscon manually .
And if you find a solution, please tell me.


A said cdob, my VM needs more 512Mo ( near 1024Mo)  to boot with my miroWinpeBuilder ( with dotnet4, PowerShell... )

Perhaps ...
Are you sure you have the time to select the second BCD entry from keboard  when you boot virtual hard disk? I see in your BCD :
" default                 {default}
timeout                 1
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}"

In my VM under HyperV on my old AMD E1, i can't get time to choose the entry with "timeout =1"
Perhaps also ...
You can active the log when OS load the drivers with "Bcdedit /store ...\boot.bcd /set {your entry} bootlog Yes". During boot,  log file is created in "your vhd":\windows\NtBtLog.txt. It will visible, if created, when you mount the vhd. It's only for knowing if boot phase arrive to this step

Excuse me to insist.
I'm a baby in English....
May i undestand that "inram" in a vhd is OK for you with 7Z and BcdBoot.exe ? ( "" of your text says not !!! )
Please, can you explain to me the difference between "inram" and "normal" ?
Note : it seems to me that, in the projet directory, the directory "target" contains all files to copy to VHD, like a complete flat tree. Only need bcdboot  after the copy ( adm rights for copy?)

Because of my bad English, need to hear as a baby, with very short sentences and browned the various scenarios if necessary.

Your observation:
-If I understand the first "post", your WinpeSE does not start (.. .the swirling circles...)
Your goal:
-put Boot.wim in a vhd and boot ( MS give the name "Winpe mode Flat" in the documentation )
Your tests:
-you use two options of winbuilder, "inram" and "normal"
-for each file, you have completed the vhd with DISM
My hypothesis:
-The BCD into your VHD is not properly rebuilt. I guess that DISM does not rebuild entierely ( from scratch ).

Note1: I've never used the "normal" option because I understand little English in the help of WinBuilder
Note 2 : mode flat and VHD.
         they use the script MakeWinPEMedia.cmd ( in ADK )

What I did very often to put "my" boot.wim file in a VHD:
1 - created a VHD with disk management (right click "disk management" + creation + boot + activation...)
2 - unzipped the boot.wim with 7Z v15 (I sometimes used DISM but the command line is longer ;-)
3 - copy system file with "BCDBOOT. EXE /S..." (see bcdboot settings)
             from my memory, and if G: is your VHD : "bcdboot G:\windows /s G: /f all"
4 - sometime ( not always ) rebuilt the BCD with bcdedit /store ( see below... )
        from my memory, and if G: is your VHD :
             to view bcd  : "bcdedit /store g:\boot\bcd" ( see below ...)
             to modify the property "device"   : "bcdedit /store g:\boot\bcd /set {default} device [boot]"
             to modify the property "osdevice" : "bcdedit /store g:\boot\bcd /set {default} osdevice [boot]"

For you, one last point to confirm:
-can you check the BCD to your VHD with the command "bcdedit /store..."?
and one other test :
-perhaps try your VHD with the "basic" boot.wim from ADK

1 - The file BCD in my VHD during my tests with WinPeSe boot.wim:

C:\WINDOWS\system32>bcdedit /store G:\Boot\bcd

Gestionnaire de démarrage Windows
identificateur          {bootmgr}
description             Windows Boot Manager
locale                  fr-fr
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Chargeur de démarrage Windows
identificateur          {default}
device                  boot
path                    \windows\system32\boot\winload.exe
description             MicroWinpeBuilder
locale                  fr-fr
inherit                 {bootloadersettings}
testsigning             Yes
osdevice                boot
systemroot              \windows
detecthal               Yes
winpe                   Yes
bootlog                 Yes
debug                   Yes
ems                     No

2 - This morning, to verify before i reply, i do :
- create a VHD file ( make a volume H:, activation ...)
- mount this vhd
- 7Z a file boot.wim ( from my microWinpeBuilder ) in this VHD H:
- bcdboot h: ...
- create a VM in hyper V on my windows10 PRO
- use the VHD in the VM
- boot this vm
- and it's OK

some comands i use :

C:\WINDOWS\system32>bcdboot  h:\windows /s h: /f all
Les fichiers de démarrage ont bien été créés.

C:\WINDOWS\system32>bcdedit /store h:\boot\bcd

Gestionnaire de démarrage Windows
identificateur          {bootmgr}
device                  unknown
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Chargeur de démarrage Windows
identificateur          {default}
device                  unknown
path                    \windows\system32\winload.exe
description             Windows PreInstallation Environment
locale                  en-us
inherit                 {bootloadersettings}
allowedinmemorysettings 0x15000075
osdevice                unknown
systemroot              \windows
nx                      OptOut
winpe                   Yes

I'm not a guru of WinpeSE, I do not understand English and I use extensively bing.translator. Also, my information may be irrelevant.
If I understand correctly, you used Dism/apply-image to put Boot.wim of WinPeSe inside a VHD disk.
For my tests, I very often use a VHD disk.
To place a Boot.wim file (from an ISO) in the VHD, I abandoned DISM and I use 7Z version 15.10 or above.
Then you must create the BCD with BCDBOOT that copy useful files.
I've never had problems with the WinPeSe's Boot.wim. I did very often this operation when I analyzed the differences with my MicroWinpeBuilder.

If I didn't understand your request, forget my answer.

the last week has been difficult. I wanted to test 'Windows To Go'. I bought a 32 GB USB3 key.
But PWCREATOR. EXE has consider that it would be inappropriate because he found only a little more than 29 GB.
So I used the "manual" method with "dism and bootbcd".
The construction was very long, as if the key were USB2.
I got started with this USB3 key on a port USB3. The installation is successful, but it's very long also.
But the worst is when using Windows To Go. Everything was slowed down. Unusable.
The performance monitor indicated that the drive corresponding to the key was used 100% continuously.
I therefore rebuilt WTG on an old key USB2. But no luck. DISM reported an error.
I wasn't in front of the PC. The key had become unusable: write-protected.
I was looking for the "wonderful" softwares available on or
It took several days to find softwares compatibles with my key (alcor Au6983) controller.
A misguided click started installing a software on my PC under Windows 10.
And I said to myself: I just caught a virus.
The curiosity was too strong. I launched the software. Windows 10 reported that he refused to load a driver.
I am grateful to him for that. I got a little integration of this software in the OS.
And so I took out my old laptop which is always under XP SP3.
With XP, I was able to launch many of these softwares. None detected my key.
I tried to modify an .ini file with the hope to steer the recognition of my key.
When it was recognized, I even modified random parameters. Then I clicked on "start".
Of course the software reported errors. I did it again. In less than a minute, it was over.
And my key was operational again.
I launched the antivirus on my Pc on windows 10. Two days. Malware :"JS/Fashack.G" serious and active!
Found only in Firefox. Surprise for me.
One day I'll take care of the PC under XP.
So I tested this USB2 with WTG key. Same slow. Unusable.

I've moved on a bit with Windows Media Player: now I can read MP3 files. I will modify my scripts later.
I can also read files .wav with powershell ( 2 lines !) with "MCISendString API" of winmp.dll.
But WMP will not play the .wav files.

I updated v10 ( scripts ans pdf ) for printer PDF/XPS.

I put details in the script "traitement.ps1" because it evolved during the investigation. But it's in french.

I'm taking a break because I'm stuck on all tracks.

Everyone can respond to the various anomalies that I can't fix (invisible printers in the control panel for example...)

See you later.


Printers PDF and XPS are OK. I'll write a text for that. And i'll update scripts.
It was long, very long. And nor really usefull, i admit.

My wrong idea : using GUI to install printers pdf and xps
The good way : it's the spooler who install theses two printers automaticaly. it needs only to put the good files in the good place.
And "start-service spooler" with the modification od systemSetupInProgress. And after 1 or 2 minutes, printers are there.
Not visibles in control panel but visibles in Notepad.

It's difficult to put a picture to display the creation of file by printer pdf/Xps. So believe or not .....

"gwmi win32_printer" displays capabilities but not "printing".

it's time to sleep for me.

I can print (usb and network) and scan but it needs manuals steps.

For a summary of my investigation around my printer/scanner:
1 - when connecting the USB port on the PC, the installation of :
-the printer managed correctly. However, it needs the following treatment:
After you select the printer and before printing, there are changes the SystemSetupInProgress key
Eventually, do net start/net stop spooler.
-Scan works properly. Nevertheless, certain keys are not entered in the register
Therefore, treatment: adding keys, net start/net stop stisvc

2. for PDF and XPS printers, I failed installation.
Fact: due to the method of installation of ntprint.inf and ntprint4.inf with DISM, the hive Drivers does not point
entry ntprint.inf or ntprint4.inf. Indeed the mechanism "DISM" renames these entries with names starting with OEMxxxx.inf.
Consequence: in the session System, i load the hive Drivers and change these entries.
To find good entries to rename, you can consult the file...\mount\...\inf\
Pre installation: when the spooler starts with SystemSetupInProgress = 0, it pre-installs (IMPORT section in
inf files in the directory under x:\windows\system32\spool\tools\microsoft... ( copied in boot.wim ).
Then, you must install these printers with "control.exe/devices and printers" for example.
To select: use the last choice 'add a local printer...', then select the port "PortPrompt". Are displayed on left side "manufacturer" (microsoft)
and on the right, the 2 printers PDF and XPS.
Then we start the installation ... and error message appears:
"cannot install the printer.
Invalid descriptor".

The procmon trace does not tell me more. I don't know from where this descriptor comes. ( translator : ggrrrrr )

Next week, I will compare with installation on a windows 10 OS.

I'm trying to find the package "scx4500.inf_amd64_47a7ea2a0d75d8c7".
On my windows10Pro, I look in the file and i found a surprise :
"     sto: {Setup Import Driver Package: c:\programdata\microsoft\windows\devicesoftwareupdates\1f79ef28-b3f9-4de5-8b6e-26332c0c3f65\scx4500.inf} 22:38:04.617
     inf:      Catalog File:
It's really my package but i don't know this "temporary" repository "devicesoftwareupdates".
And after in the log, i see that this directory is copied in the driverstore.
But i can't find this package in the ISO Windows10Entreprise.

Please, can someone explain to me where to find my package and describe the mecanisme "import driver package" ?
Thank you very much


Ma première numérisation avec le scan de mon imprimante Samsung SCX4500 : OK
My fisrt scan with my printer is ok.

I make an other test in the calm. I think i have the good elements but not the good sequence.

But the question is still : during installation, why some keys are missing under ....\control\class\{6BB... ?

it's not very usefull but it's a good game. I saw in the forum that a guy ask about printer and i say to me : can i play with printer?

I know, each printer and scan is particular and it's not easy for anyone to put his printer. I use dism because it's a simple way for me.
I isole my drivers and put them in my scripts. Not really reproductible. But it's a good way to learn, not to "eat a raw steack".

I 'll make more modifications to automatise the work.

For the scan, i modify somme keys and i see the scan in imagingdevices.exe.
With wfs.exe, i get a new message "scan can't continue".
I see the architecture of WIA here
And i get more info in the log \debug\wiadebug.log.
I active the log with the keys
I can see in this log that WIA see one hardware but there is an error "access denied" in DCOM :
ERROR: CreateLocalDevice, Initialize of root item failed (0x80070005)
I put a picture to see the contexte and the log wia

Q : why keys are not completed during installation? because of methode of installation ? i first install wiasa003.inf with DISM during preparation boot.wim, and after, when winpe is started, PNP install the step wiasa003. And after, i launch "drvload scx4500.inf" for complete the installation

an idea ....

i try to play with the scan of my printer.
I think the installation of driver is ok, as i can see in devmgmt.msc.
But with wfs.exe or with imagingdevices.exe, i get the error message "no scan is detected".
I put a picture to see the context .

Some think is wrong : if you have an idea .....

tips before modify :
- wifi : disable and enable card before using wificonnexion.ps1
- session adm :
    use tscon 1 and tscon 2 to prevent the message "editor not verified"
    error message at the begining of session adm is not important


My first print via USB in winpe !

My printer have many 32 bits programs. I add many files in WOW64. And now i can print from my printer connected USB.
I install it in the adm session. And after the installation, it is disponible in teh system session ( tscon 1 to go ...). And i can also print in this system session.
a picture but it's true, you can't see the paper go out of the printer.
On the picture, you can see that the printer in not connected. I want to show the document in the spooler. But the document go to the printer if i connect it.
BUT it is not visible in the "control pannel\devices ans printers".
To see the printer and interact with it, a open a Notepad, clic "print" and after right clic on the printer and chose "open" or "properties".
At the begining, I got the error for a long time: "startdocprinter error" ( i'll put a picture when i get it). And to bypass this, i modify the key "SystemSetupInProgress".
I must do more about it for a good work automalicaly.

Pages: [1] 2 3 ... 5
Powered by EzPortal