noelblanc

I found a solution ... Background of my winpe10build10240:- dwm-coremessagingRegistrar installed with regedit- hdaudio.inf installed in off-line mode with dism /add-driver Then, after starting winpe and launched by startnet.cmd, this powershell code loads hdaudio, starts the AudioEndpointBuilder service modifies acl of the key created by the AudioEndpointBuilder, start the service AudioSrv, and then modifdie key "shell" to launch "explorer" the code PS ( yes, it's bad, too many start-sleep but it's work for me ) : drvload d:\sourceDesAjouts\audio\hdaudio\hdaudio.infstart-sleep -s 1 # start service AudioEndpointBuilder write-host -ForegroundColor green "`nAudio : start service AudioEndpointBuilder" Start-Service AudioEndpointBuilder start-sleep -s 1 # modif acl write-host -ForegroundColor green "`nAudio : on modifie les acl de $c" $c='HKLM:\SOFTWARE\MICROSOFT\Windows\CurrentVersion\MMDevices\Audio\Render\' $cibles = gci $c | %{$_.pspath}|%{gci $_}|?{$_.name -ilike "*\properties"}|%{$_.pspath} # on lit une acl $aclBase = get-acl 'HKLM:\SOFTWARE\MICROSOFT\Windows\CurrentVersion\MMDevices\Audio\Render' # on crée les ace pour les comptes de service $rule1=New-Object System.Security.AccessControl.RegistryAccessRule("NT SERVICE\Audiosrv","FullControl","Allow") $rule2=New-Object System.Security.AccessControl.RegistryAccessRule("NT SERVICE\AudioEndpointBuilder","FullControl","Allow") # on ajoute ces 2 ace dans l'acl finale pour les 4 clés foreach ($cible in $cibles){ $aclBase.SetAccessRule($rule1) $aclBase.SetAccessRule($rule2) $aclBase | set-acl -Path $cible } # start service audiosrv write-host -ForegroundColor green "`nAudio : start service audiosrv" Start-Service audiosrv it is surprising accounts and they work in theses acl of my winpe10.

Hello Kullenen_ask, I know this topic is very old but ... I hope you work on winpe10. I appreciate your work and your comments in forums. I hope i don't disturb you. My English is very poor. With winpe10, the desktop of explorer is more confortable than winpe5. The taskbar is ok. I also get wifi, mmc... Actually, i'm trying to put audio/sound in winpe10 manually. ​ But it doen't work. To avoid the problems with the registry, I copy entierly some sections clsid, svchost,etc.i also copy Ks.inf in x:\windows\inf and many other files.I track with procmon​64. With PowerShell, I install the 2 services AudioEndPointBulder and AusioSrv. I modify the requestPrivilege as you said. I install with drvload the driver for my sound card. I get icône and all animations in the notification bar are aok. With a right clic, I open "speakers". I clic on "test" and get the messagebox "Unable to read the test tone". And in devmgmt.msc, y see in "others périphériques" that "Audio evice on Hight Definition Audio Bus" have no installed drivers​. Is it necessary ? I try "update driver" and ask to search in the hard disk where Windows10 is ok with this card ( on the same pc ). I get the message " file not found". I look in x:\windows\inf\setupapi.dev.log and found : "driver package 'hdaudio​​' is configurable copying 'e:\Windows\inf\hda​udio.inf' to x:\windows\system32\driverstore\temp\...' error installing file (​0x00000002) error 2​ the system cannot find the file specified SourceFile : 'e:\Windows\inf\hdaudio.sys " So i copy hdaudio.inf, hdaudio.sys in x:\inf and try again to update driver. I get the message​​​ "no .cat". I look again in x:\windows\inf\setupapi.dev.log and found : " copying 'x:\inf\hdaudio.inf' to x:\...\driverstore\...​ copying 'x:\inf\hdaudio.sys' to x:\...\driverstore\...​​ {driverstore import valid​ate} driver package does not contain a catalog file and code integrity is in 'test signing" mode --> i modified bcd for that " i don't find the .cat in E:\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}, the sound Ok in this os. the file hdaudio​.inf does not contain in section [version] a reference to the cat Same error with drvload​.exe of course. so my questions : is hdaudio.sys necessary? if yes, where is the .cat? how can i install this hdaudio.sys in the boot.wim? Offline? manually in registry after loaded it? Have you get audio in winpe10? ​thanks for your help Merci.​​

hello ^Miki^ hvandrie said in http://www.msfn.org/board/topic/162453-winpe-40-enable-wireless-support/ : "First, you do not need to implement "WcmSvc", or "Windows Connection Manager", service. When you create the wlansvc service and it's listed in the "DependsOnService" entry of the server, just remove the entry wcmsvc from the reg_multi_sz key." hvandrie said also : "you now are able to start the wlansvc without a problem and use netshell command (netsh) to see and add wireless network profiles to connect to." For adding wireless network profiles to connect to : on a working computer, connect to the wifi network, export the profile with text password. After, on winpe, import this profile. See here : http://superuser.com/questions/133097/netsh-wlan-add-profile-not-importing-encrypted-passphrase So, I don't use these two files (wcmsvc.dll and wcmsvc.dll.mui) for wifi in winpe10. But if you really need them, you can find them in the install.Wim of Win10 Entreprise Eval ( be carefull for the build of the downloaded iso ) in Windows\system32 not in Windows\system32\drivers.

Sorry for the french text. I beg your pardon. i think the construct for winpe5 is similar. A picture to see the result : wifi on intel Centrino Wireless N2200 with winpe10 build 10075 winpe10-wifi.bmp The more longer is to get ncpa.cpl and a desktop screen with taskbar for the confort. This taskbar comes a minute after the desktop screen : i don't know why ! It is also possible to pin application. i taked the screen copy with a simple .ps1 script because i don't how to get snippingtools.exe in winpe. I can use winpe10 from my pc with wifi with a few commands : in winpe10 : wpeutil /disableFireWall ------>>>> perhaps not needed net start server ------------------->>> i put all packages when i create the boot.wim de winpe10 net user toto toto /add net localgroup administrators toto /add in my pc : net use \\192.168.0.4\x$ /user:toto toto dir \\192.168.0.4\x$ it's funny to construct a puzzle around winpe with only scripts and procmon. But many things are broken : - i can create a shortcut on the desktop but i can't give the name of the programme to launch - ie doesn't works but it is possible to download a page with a simple .ps1 ( with system.net.webclient ) - In" mmc devmgmt.msc", i can't see the hidden devices because the view menu is broken. - "mmc WF.msc" doesn't works ...

hello, Today, i use wifi in wipe for windows 10 Winpe_10 build is 10075 and i use files from windows 10074 upgraded to 10130. It's important for the .cat files. With winpe_10, wifi is easy to get. if you still have this need, i can send my cmd files to use starting point. And desktop in winpe_10 have the taskbar : confortable with a very few work ( also ncpa.cpl ) In a few words, for wifi in winpe_10 : 4 - Pour le wifi : préparation de boot.wim de winpe_10 avec "dism /add-driver" Respecter l'ordre de lancement des "dism /add-driver" note : ne pas mélanger les versions des fichiers Identifier et collecter les fichiers inf, sys ... Mes références : http://pcloadletter.co.uk/2011/12/03/windows-pe-builder-script-for-waik-including-wifi-support/ http://blogs.technet.com/cfs-filesystemfile.ashx/__key/telligent-evolution-components-attachments/01-6127-00-00-03-31-62-58/Windows-7-Deployment-Procedures-in-802-1X-Wired-Networks.pdf http://www.msfn.org/board/topic/162453-winpe-40-enable-wireless-support/ 4-1 Les NetServices pour netcfg.exe - netnwifi.inf pour le service MS_NativeWifiP ( et aussi pour installer le pilote NativeWifiP ? ) - netvwififlt.inf pour le service MS_vWifi 4-2 Le pilote de la carte wifi ( intel dans mon cas ) Pour le pilote intel de ma carte, le .inf possède un include ( voir le log windows\inf\setupapi.offline.log) pour la carte: netwew00.inf, NETwew00.sys, Netwfw00.dat pour l'include: netvwifibus.inf, vwifibus.sys, vwifibus.sys.mui (En-us) Mais la commande "dism /add-driver" ira aussi chercher %mount%windows\inf\vwifibus.sys : donc copier au préalable ce fichier dans ce répertoire 4-3 Les pilotes utilisés par les couches réseau wifi : je ne sais pas pourquoi. note : Les noms correspondent aux entrées de la base de registre "services" - NativeWifiP : est il installé par le NetService ? - vwifibus : il est installé par l'include netvwifibus.inf - vwififlt : le seul que j'installe manuellement ( je ne sais pas à quoi il sert ) Je n'ai pas trouvé d'autre méthode que de créer les clés de registre avec des fichiers .reg depuis un export de W10Ent 4-4 Copier le répertoire L2Schemas depuis une machine sous windows10 4-5 Exporter le profil wifi depuis une machine sous windows10, export avec mot de passe en clair 5 - Pour le wifi : après le démarrage de winpe créer le service wlansvc importer le profil lancer la connexion Verifier avec powershell et une page http : $wc = New-Object system.net.webclient $url="https://qwant.com" $wc.DownloadFile($url, "x:\q.txt") notepad "x:\q.txt" NoelBlanc​

Hello, Thanks for this information. Please, may i ask you if you try to inject a "MS's" driver with regedit. I want to inject the nativewifip.sys but i can't do this with dism ( no inf file !) . And i don't find the .cat in the catroot of install.Wim (w10). Do you know how to do with the .cat? Note : I try to inject http.sys with regedit and the copy of the good "cat" files of http. And it's ok when winpe10 start. Thank you very much