Windows 10: [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?

Discus and support [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files? in Windows 10 Installation and Upgrade to solve the problem; I'm trying to create a clean and updated Windows 10 Pro installation and updated an official 16299.64 build to 16299.125 using wimlib-imagex. All... Discussion in 'Windows 10 Installation and Upgrade' started by copyitright, Dec 17, 2017.

  1. [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?


    I'm trying to create a clean and updated Windows 10 Pro installation and updated an official 16299.64 build to 16299.125 using wimlib-imagex.

    All went fine but after inspecting the resulting install.wim's file/folder structure i noticed that the update process created many \WinSxS\Temp\InFlight\ files (there's also a WinSxS\pending.xml) and some \Windows\servicing\Sessions\ .xml's (also a Sessions.xml and Sessions.back.xml) .

    Now i'm wondering if there's a way to clean this all up, because MSFT apparently knows how to release ISO's/ESD's without any temp WinSxS files present.

    Thank you in advance!
    [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files? [​IMG]


    (for your information: both Pending(Deletes/Renames) folders are empty, and TransformerRollbackData is non-existing)

    :)
     
    copyitright, Dec 17, 2017
    #1

  2. Update KB4054517 crashed my machine, so I am now stuck in 16299.64 . Should I install one by one each next patch?

    Thank you Andre Da Costa for your reply.

    I am not sure this patch KB3073930 applies to my win version, since I have Fall installed 1709, and not 1607.

    After reverting to a previous restore point, I am now in build 16299.64

    But in the windows catalog, I see 16299.98 and 16299.124 which come before 16299.125.

    The install of 16299.125 caused a mayor crash. But shall I download and install the previous patches for builds 16299.98 and 16299.124?

    Or wait for another patch that would be higher than 16299.125 and solve all the issues in one step?

    Confusing

    Thanks
     
    ChrisOnMicro, Dec 17, 2017
    #2
  3. Game Mode ON/Off Button Missing But Says Ur laptop Support It

    Try installing the latest cumulative update 16299.125

    Notice you are still on 16299.64.

    If that does not work, perform a repair upgrade:

    http://answers.microsoft.com/en-us/insider/wiki...
     
    Andre Da Costa, Dec 17, 2017
    #3
  4. SIW2 Win User

    [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?

    The updates are pending. That is normal when installing updates into a wim.
     
  5. Hmm, peraps that's the reason why i noticed a sh*tload of BackgroundTask processes/instances at first boot.
    But.. Microsoft delivers updated ISO/ESD releases without these temp/pending files. I want to achieve that too ;-/
     
    copyitright, Dec 17, 2017
    #5
  6. SIW2 Win User
    Either d/l the updated version, or install, sysprep and capture your existing wim.

    There is some kind of issue with store apps with sysprep/generalise on win10. Can't recall exactly what it is, because I don't bother doing it.
     
  7. lx07 Win User
    Why are you using imagex?

    Not saying you shouldn't (as you wish of course) but you may find using dism (or the equivalent powershell commands) would work better. They were not deprecated a decade ago.

    I guess it is all these old MDL people with their old scripts - rather than use oscdimg they'll copy in some old rubbish from a decade ago.

    Nothing wrong with that but better write it yourself I reckon.
     
  8. [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?

    AFAIK there's no official 16299.125 ISO/ESD out. The store apps problem was resolved by a hotfix (can't recall where i found it though).

    I'm using wimlib, it has some improved DISM (and imagex) functions and some new things that aren't found in DISM/imagex. I wouldn't call a DISM/imagex fork deprecated yet (it has more/better compression options/algorithms too).

    Speaking of MDL: abbodi1406's Windows 10 Updates Installer makes use of oscdimg (or cdimage), is still being worked on and has been updated very recent.
     
    copyitright, Dec 17, 2017
    #8
  9. lx07 Win User
    I know what wimlib is. Perhaps it does do better compression - that is easy - you could use xpress:16k instead of xpress:4k or whatever.

    The easiest (clearest, supportable) way to make an ISO is like this: PHP Code: # Unmount the WinPE image
    Get-WindowsImage -Mounted -ErrorAction Stop | ForEach-Object {
    Dismount-WindowsImage -Path $_.Path -Save -ErrorAction Stop
    }

    # Set the correct boot argument based on availability of boot apps
    if (Test-Path $WorkDir\fwfiles\etfsboot.com) {
    $BOOTDATA="2#p0,e,b`"$WorkDir\fwfiles\etfsboot.com`"#pEF,e,b`"$WorkDir\fwfiles\efisys.bin`""
    } else { $BOOTDATA="1#pEF,e,b`"$WorkDir\fwfiles\efisys.bin`"" }

    # Make ISO
    $command="$ADK\Deployment Tools\$PEArch\Oscdimg\oscdimg.exe"
    &$command -l:$ISOLabel -h -m -o -u1 -bootdata:$bootdata "$WorkDir\media" "$ISOPath"
    No-one really cares how big an ISO is unles the contents will (or will not) fit under 4GB.

    I do wish we could get rid of the "2#p0,e,b" stuff though but it is required - presumably for CD's or DVD's or cassette tapes or something.
     
  10. Superfly Win User
    "2#p0,e,b" are parameters required by IMAPI API for image creation - not related to legacy media.

    ie:
    2 = # of boot images

    e = Disables floppy disk emulation in the El Torito catalog.

    p0 = Specifies the value to use for the platform ID - 0 to represent a BIOS system.

    pEF = platform ID UEFI system.

    Not sure about the b param tho'....

    I recall having struggled getting a boot array to work in .Net until I came across some little known C++ safe-array code and had to adapt it.
     
    Superfly, Dec 17, 2017
    #10
  11. lx07 Win User
    I copied the whole lot from some Italian site.

    Apparently b means this
    https://docs.microsoft.com/en-us/pre...49036(v=ws.10)

    Anyway my point was it would be nice if there was a command like Make-ISO that would convert a directory with the correct structure into an ISO without having to use a command requiring gobblegook to be put into text strings like we are in 1988 not 2018.
     
  12. Superfly Win User
    O.I.C... btw that link gives me 404 page error

    Anyway it''s not needed - this is how I create the required params - I havent got it to wor'k in PS yet.

    Code: psaBoot = Array.CreateInstance(typeof(Object), 2); FsiStream MBRbootStream,EFIbootStream; iso.ChooseImageDefaultsForMediaType(IMAPI_MEDIA_PHYSICAL_TYPE.IMAPI_MEDIA_TYPE_DISK); iso.FileSystemsToCreate = FsiFileSystems.FsiFileSystemUDF; iso.VolumeName = VolID; // Create MBR boot stream MBRbootStream = IBootStream(MBRbootFile); BootOptions MBRbootOptions = new BootOptions(); MBRbootOptions.Manufacturer = "Microsoft"; MBRbootOptions.PlatformId = PlatformId.PlatformX86; MBRbootOptions.Emulation = EmulationType.EmulationNone; MBRbootOptions.AssignBootImage(MBRbootStream); ///<!-- EFI boot is architecture specific --> // Create EFI boot stream EFIbootStream = IBootStream(EFIbootFile); BootOptions EFIbootOptions = new BootOptions(); EFIbootOptions.Manufacturer = "Microsoft"; EFIbootOptions.PlatformId = PlatformId.PlatformEFI; EFIbootOptions.Emulation = EmulationType.EmulationNone; EFIbootOptions.AssignBootImage(EFIbootStream); psaBoot.SetValue(MBRbootOptions, 0); psaBoot.SetValue(EFIbootOptions, 1); iso.BootImageOptionsArray = psaBoot;[/quote]
     
    Superfly, Dec 17, 2017
    #12
  13. lx07 Win User

    [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?

    Fixed - it is a forum bug - it drops last ")" on URL.
     
  14. Well, i have an off topic question for you guys (not sure if its worth a new thread).

    Is it possible to add/create a new Windows service by using REG ADD only and typing all the required registry keys/entries?
    I normally use the command SC CREATE for this but possibly it can also be done in another way?

    This is the script i used:

    Code: @ECHO OFF :: of course ran with admin privileges SET "REG_KEY=REG ADD HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\example_service /v" %REG_KEY% Type /t REG_DWORD /d 16 /F %REG_KEY% Start /t REG_DWORD /d 2 /F %REG_KEY% ErrorControl /t REG_DWORD /d 1 /F %REG_KEY% ImagePath /t REG_EXPAND_SZ /d "%%SystemRoot%%\System32\examplesvc.exe -something" /F %REG_KEY% DisplayName /d "Exmple Service" /F %REG_KEY% ObjectName /d LocalSystem /F %REG_KEY% Description /d "Example Description" /F[/quote] However, after running the script i didn't see a new service appear in services.msc (also not after a restart).
     
    copyitright, Dec 19, 2017
    #14
  15. lx07 Win User
    It certainly is possible.

    I add Wifi to my PE image like this and it works.

    Not sure it is the most efficient way but certainly you can. Code: # Add WiFi Services if ($WifiRequired) { # # Unified Windows PE 3.1 builder script for WAIK, with wifi and EFI support mkdir $WorkDir\mount\Windows\schemas\AvailableNetwork copy "$env:SystemRoot\schemas\AvailableNetwork\AvailableNetworkInfo.xsd" "$WorkDir\mount\Windows\schemas\AvailableNetwork\AvailableNetworkInfo.xsd" # exe copy "$env:SystemRoot\system32\wifitask.exe" "$WorkDir\mount\Windows\system32\wifitask.exe" copy "$env:SystemRoot\system32\wlanext.exe" "$WorkDir\mount\Windows\system32\wlanext.exe" copy "$env:SystemRoot\system32\en-US\wlanext.exe.mui" "$WorkDir\mount\Windows\system32\en-US\wlanext.exe.mui" # wlan* Dlls copy "$env:SystemRoot\system32\wlanapi.dll" "$WorkDir\mount\Windows\system32\wlanapi.dll" copy "$env:SystemRoot\system32\en-US\wlanapi.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlanapi.dll.mui" copy "$env:SystemRoot\system32\wlancfg.dll" "$WorkDir\mount\Windows\system32\wlancfg.dll" copy "$env:SystemRoot\system32\en-US\wlancfg.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlancfg.dll.mui" copy "$env:SystemRoot\system32\WLanConn.dll" "$WorkDir\mount\Windows\system32\WLanConn.dll" copy "$env:SystemRoot\system32\en-US\WLanConn.dll.mui" "$WorkDir\mount\Windows\system32\en-US\WLanConn.dll.mui" copy "$env:SystemRoot\system32\wlandlg.dll" "$WorkDir\mount\Windows\system32\wlandlg.dll" copy "$env:SystemRoot\system32\en-US\wlandlg.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlandlg.dll.mui" copy "$env:SystemRoot\system32\wlangpui.dll" "$WorkDir\mount\Windows\system32\wlangpui.dll" copy "$env:SystemRoot\system32\en-US\wlangpui.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlangpui.dll.mui" copy "$env:SystemRoot\system32\WLanHC.dll" "$WorkDir\mount\Windows\system32\WLanHC.dll" copy "$env:SystemRoot\system32\en-US\WLanHC.dll.mui" "$WorkDir\mount\Windows\system32\en-US\WLanHC.dll.mui" copy "$env:SystemRoot\system32\wlanhlp.dll" "$WorkDir\mount\Windows\system32\wlanhlp.dll" copy "$env:SystemRoot\system32\WlanMediaManager.dll" "$WorkDir\mount\Windows\system32\WlanMediaManager.dll" copy "$env:SystemRoot\system32\WlanMM.dll" "$WorkDir\mount\Windows\system32\wlanmm.dll" copy "$env:SystemRoot\system32\en-US\WlanMM.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlanmm.dll.mui" copy "$env:SystemRoot\system32\wlanmsm.dll" "$WorkDir\mount\Windows\system32\wlanmsm.dll" copy "$env:SystemRoot\system32\wlanpref.dll" "$WorkDir\mount\Windows\system32\wlanpref.dll" copy "$env:SystemRoot\system32\en-US\wlanpref.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlanpref.dll.mui" copy "$env:SystemRoot\system32\WlanRadioManager.dll" "$WorkDir\mount\Windows\system32\WlanRadioManager.dll" copy "$env:SystemRoot\system32\wlansec.dll" "$WorkDir\mount\Windows\system32\wlansec.dll" copy "$env:SystemRoot\system32\wlansvc.dll" "$WorkDir\mount\Windows\system32\wlansvc.dll" copy "$env:SystemRoot\system32\en-US\wlansvc.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlansvc.dll.mui" copy "$env:SystemRoot\system32\wlansvcpal.dll" "$WorkDir\mount\Windows\system32\wlansvcpal.dll" copy "$env:SystemRoot\system32\wlanui.dll" "$WorkDir\mount\Windows\system32\wlanui.dll" copy "$env:SystemRoot\system32\en-US\wlanui.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlanui.dll.mui" # Already in WinPE image #copy "$env:SystemRoot\system32\wlanutil.dll" "$WorkDir\mount\Windows\system32\wlanutil.dll" #copy "$env:SystemRoot\system32\en-US\wlanutil.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlanutil.dll.mui" # Wifi* dll copy "$env:SystemRoot\system32\WiFiConfigSP.dll" "$WorkDir\mount\Windows\system32\WiFiConfigSP.dll" copy "$env:SystemRoot\system32\wificonnapi.dll" "$WorkDir\mount\Windows\system32\wificonnapi.dll" copy "$env:SystemRoot\system32\WiFiDisplay.dll" "$WorkDir\mount\Windows\system32\WiFiDisplay.dll" copy "$env:SystemRoot\system32\en-US\WiFiDisplay.dll.mui" "$WorkDir\mount\Windows\system32\en-US\WiFiDisplay.dll.mui" copy "$env:SystemRoot\system32\wifinetworkmanager.dll" "$WorkDir\mount\Windows\system32\wifinetworkmanager.dll" copy "$env:SystemRoot\system32\en-US\wifinetworkmanager.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wifinetworkmanager.dll.mui" copy "$env:SystemRoot\system32\wifiprofilessettinghandler.dll" "$WorkDir\mount\Windows\system32\wifiprofilessettinghandler.dll" # Other dll copy "$env:SystemRoot\system32\wfdprov.dll" "$WorkDir\mount\Windows\system32\wfdprov.dll" copy "$env:SystemRoot\system32\wlgpclnt.dll" "$WorkDir\mount\Windows\system32\wlgpclnt.dll" copy "$env:SystemRoot\system32\en-US\wlgpclnt.dll.mui" "$WorkDir\mount\Windows\system32\en-US\wlgpclnt.dll.mui" copy "$env:SystemRoot\System32\WcnNetsh.dll" "$WorkDir\mount\Windows\System32\WcnNetsh.dll" copy "$env:SystemRoot\System32\en-US\WcnNetsh.dll.mui" "$WorkDir\mount\Windows\System32\en-US\WcnNetsh.dll.mui" copy "$env:SystemRoot\System32\whhelper.dll" "$WorkDir\mount\Windows\System32\whhelper.dll" copy "$env:SystemRoot\System32\en-US\whhelper.dll.mui" "$WorkDir\mount\Windows\System32\en-US\whhelper.dll.mui" # drivers copy "$env:SystemRoot\System32\Drivers\nwifi.sys" "$WorkDir\mount\Windows\System32\Drivers\nwifi.sys" copy "$env:SystemRoot\System32\Drivers\en-US\nwifi.sys.mui" "$WorkDir\mount\Windows\System32\Drivers\en-US\nwifi.sys.mui" # net start NativeWifiP failed due to missing signatures. These are from sysinternals sigcheck -i c:\Windows\System32\drivers\nwifi.sys etc copy "$env:SystemRoot\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_297_for_KB3081444~31bf3856ad364e35~amd64~~10.0.1.0.cat" ` "$WorkDir\mount\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_297_for_KB3081444~31bf3856ad364e35~amd64~~10.0.1.0.cat" copy "$env:SystemRoot\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Features-Package-AutoMerged-net~31bf3856ad364e35~amd64~en-US~10.0.10240.16384.cat" ` "$WorkDir\mount\Windows\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Microsoft-Windows-Client-Features-Package-AutoMerged-net~31bf3856ad364e35~amd64~en-US~10.0.10240.16384.cat" copy "$env:SystemRoot\System32\Drivers\vwififlt.sys" "$WorkDir\mount\Windows\System32\Drivers\vwififlt.sys" copy "$env:SystemRoot\System32\Drivers\vwifimp.sys" "$WorkDir\mount\Windows\System32\Drivers\vwifimp.sys" copy "$env:SystemRoot\System32\Drivers\WdiWiFi.sys" "$WorkDir\mount\Windows\System32\Drivers\WdiWiFi.sys" copy "$env:SystemRoot\Inf\netnwifi.inf" "$WorkDir\mount\Windows\Inf\netnwifi.inf" Add-WindowsDriver -Path "$WorkDir\mount" -Driver "$env:SystemRoot\Inf\netnwifi.inf" copy "$env:SystemRoot\Inf\netvwififlt.inf" "$WorkDir\mount\Windows\Inf\netvwififlt.inf" Add-WindowsDriver -Path "$WorkDir\mount" -Driver "$env:SystemRoot\Inf\netvwififlt.inf" copy "$env:SystemRoot\Inf\netvwifimp.inf" "$WorkDir\mount\Windows\Inf\netvwifimp.inf" Add-WindowsDriver -Path "$WorkDir\mount" -Driver "$env:SystemRoot\Inf\netvwifimp.inf" # WinPE 4.0 - Enable Wireless Support copy "$env:SystemRoot\Inf\netvwifibus.inf" "$WorkDir\mount\Windows\Inf\netvwifibus.inf" copy "$env:SystemRoot\System32\Drivers\vwifibus.sys" "$WorkDir\mount\Windows\System32\Drivers\vwifibus.sys" copy "$env:SystemRoot\System32\Drivers\en-US\vwifibus.sys.mui" "$WorkDir\mount\Windows\System32\Drivers\en-US\vwifibus.sys.mui" copy "$env:SystemRoot\System32\Drivers\vwifibus.sys" "$WorkDir\mount\Windows\Inf\vwifibus.sys" # Dism fails if vwifibus.sys is not added to C:\Windows\INF $AddedToInf = $False if (-not(Test-Path $env:SystemRoot\Inf\netvwifibus.sys)){ $AddedToInf = $True copy "$env:SystemRoot\System32\Drivers\vwifibus.sys" "$env:SystemRoot\Inf\vwifibus.sys" Write-Host "Added $env:SystemRoot\Inf\vwifibus.sys" -f Red } Add-WindowsDriver -Path "$WorkDir\mount" -Driver "$env:SystemRoot\Inf\netvwifibus.inf" if ($AddedToInf) { Remove-Item "$env:SystemRoot\Inf\vwifibus.sys" -ErrorAction 0 Write-Host "Deleted $env:SystemRoot\Inf\vwifibus.sys" -f Red } # L2Schemas - copy any missing files robocopy /xc /xn /xo /copyall "$env:SystemRoot\L2Schemas" "$WorkDir\mount\Windows\L2Schemas" # Registry Changes reg load HKLM\WinPE_SYSTEM $WorkDir\mount\windows\system32\config\SYSTEM reg load HKLM\WinPE_SOFTWARE $WorkDir\mount\windows\system32\config\SOFTWARE $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\NetSh" reg add $RegKey /v wlancfg /t REG_SZ /d wlancfg.dll /f $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\Windows NT\CurrentVersion\Svchost" reg add $RegKey /v LocalSystemNetworkRestricted /t REG_MULTI_SZ /d Netman\0hidserv\0svsvc\0dot3svc\0wlansvc /f # wlansvc reg add HKLM\WinPE_SOFTWARE\Microsoft\WlanSvc\bmr /ve $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\WlanSvc\PowerProfiles\ClassAC" reg add $RegKey /v PowerIdle /t REG_DWORD /d 15 # numbers are decimal reg add $RegKey /v PowerTail /t REG_DWORD /d 280 reg add $RegKey /v PowerTxRx /t REG_DWORD /d 400 reg add $RegKey /v TailDuration /t REG_DWORD /d 300 $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\WlanSvc\PowerProfiles\ClassB" reg add $RegKey /v PowerIdle /t REG_DWORD /d 15 reg add $RegKey /v PowerTail /t REG_DWORD /d 280 reg add $RegKey /v PowerTxRx /t REG_DWORD /d 400 reg add $RegKey /v TailDuration /t REG_DWORD /d 300 $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\WlanSvc\PowerProfiles\ClassG" reg add $RegKey /v PowerIdle /t REG_DWORD /d 15 reg add $RegKey /v PowerTail /t REG_DWORD /d 280 reg add $RegKey /v PowerTxRx /t REG_DWORD /d 400 reg add $RegKey /v TailDuration /t REG_DWORD /d 300 $RegKey="HKLM\WinPE_SOFTWARE\Microsoft\WlanSvc\PowerProfiles\ClassN" reg add $RegKey /v PowerIdle /t REG_DWORD /d 15 reg add $RegKey /v PowerTail /t REG_DWORD /d 280 reg add $RegKey /v PowerTxRx /t REG_DWORD /d 400 reg add $RegKey /v TailDuration /t REG_DWORD /d 300 $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc" reg add $RegKey /v DisplayName /d "@%SystemRoot%\System32\wlansvc.dll,-257" reg add $RegKey /v ErrorControl /t REG_DWORD /d 1 reg add $RegKey /v Group /d TDI reg add $RegKey /v ImagePath /t REG_EXPAND_SZ /d "%SystemRoot%\system32\svchost.exe -k LocalSystemNetworkRestricted" reg add $RegKey /v Start /t REG_DWORD /d 2 # (automatic start) in clean install system this is 3(manual start) reg add $RegKey /v Type /t REG_DWORD /d 32 reg add $RegKey /v Description /d "@%SystemRoot%\System32\wlansvc.dll,-258" # Remove the Windows Connection Manager (wcmsvc) service dependany reg add $RegKey /v DependOnService /t REG_MULTI_SZ /d nativewifip\0RpcSs\0Ndisuio reg add $RegKey /v ObjectName /d LocalSystem reg add $RegKey /v ServiceSidType /t REG_DWORD /d 1 reg add $RegKey /v RequiredPrivileges /t REG_MULTI_SZ /d "SeChangeNotifyPrivilege\0SeImpersonatePrivilege\0SeAuditPrivilege\0SeTcbPrivilege\0SeDebugPrivilege" reg add $RegKey /v FailureActions /t REG_BINARY /d 805101000000000000000000030000001400000001000000c0d4010001000000e09304000000000000000000 $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters" reg add $RegKey /v ServiceDll /t REG_EXPAND_SZ /d "%SystemRoot%\System32\wlansvc.dll" reg add $RegKey /v ServiceDllUnloadOnStop /t REG_DWORD /d 1 reg add $RegKey /v ServiceMain /d WlanSvcMain $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\ComInterfaceProviders" reg add $RegKey /v IHNetIcsSettings /d "{46C166AA-3108-11D4-9348-00C04F8EEB71}" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\EapolKeyIpAddress" reg add $RegKey /v LocalAddress /d "192.168.173.1" reg add $RegKey /v PrefixLength /t REG_DWORD /d 24 $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\OEM\SystemCapabilities" reg add $RegKey /ve #***************** no value $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\OneXAuthenticator" reg add $RegKey /ve /t REG_EXPAND_SZ /d "%SystemRoot%\System32\WcnEapAuthProxy.dll" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\VendorSpecificIEProviders\02166b50-0459-44d9-9ec1-073431b7d9c9" reg add $RegKey /v Path /t REG_EXPAND_SZ /d "%SYSTEMROOT%\System32\TetheringIeProvider.dll" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\VendorSpecificIEProviders\4D50EE01-EEE0-4E5D-9A41-2F5F32044192" reg add $RegKey /v Path /t REG_EXPAND_SZ /d "%SYSTEMROOT%\System32\WlanSvc.dll" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\VendorSpecificIEProviders\B7D94B4D-5DB1-4E70-B5C3-DD003EEEBE66" reg add $RegKey /v Path /t REG_EXPAND_SZ /d "%SYSTEMROOT%\System32\WiFiDisplay.dll" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Parameters\WFDProvPlugin" reg add $RegKey /ve /t REG_EXPAND_SZ /d "%SystemRoot%\System32\wfdprov.dll" reg add $RegKey /v DllEntryPoint /d WFDProvGetInfo $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Security" reg add $RegKey /v Security /t REG_BINARY /d 0100048098000000a40000000000000014000000020084000500000000001400fd01020001010000000000051200000000001800ff010f0001020000000000052000000020020000000014008d010200010100000000000504000000000014008d01020001010000000000050600000000002800700000000106000000000005500000002e25d9e85a67cd58c504f3dc32c0cb09ab704571010100000000000512000000010100000000000512000000 $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\VirtualizationManager" reg add $RegKey /v WindowsPushNotificationPlatformClsid /d "0C9281F9-6DA1-4006-8729-DE6E6B61581C" # Native Wifi Filter (dependancy of wlansvc) $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\NativeWifiP" reg add $RegKey /v DisplayName /d "@%SystemRoot%\System32\drivers\nwifi.sys,-101" reg add $RegKey /v ErrorControl /t REG_DWORD /d 1 reg add $RegKey /v Group /d NDIS reg add $RegKey /v ImagePath /t REG_EXPAND_SZ /d "system32\DRIVERS\nwifi.sys" reg add $RegKey /v Start /t REG_DWORD /d 3 reg add $RegKey /v Type /t REG_DWORD /d 1 # vwififlt $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\vwififlt" reg add $RegKey /v DisplayName /d "@%SystemRoot%\System32\drivers\vwififlt.sys,-259" reg add $RegKey /v ErrorControl /t REG_DWORD /d 1 reg add $RegKey /v Group /d NDIS reg add $RegKey /v ImagePath /t REG_EXPAND_SZ /d "System32\drivers\vwififlt.sys" reg add $RegKey /v Start /t REG_DWORD /d 1 reg add $RegKey /v Type /t REG_DWORD /d 1 reg add $RegKey /v Description /d "@%SystemRoot%\System32\drivers\vwififlt.sys,-260" reg add $RegKey /v NdisMajorVersion /t REG_DWORD /d 6 reg add $RegKey /v NdisMinorVersion /t REG_DWORD /d 50 reg add $RegKey /v DriverMajorVersion /t REG_DWORD /d 1 reg add $RegKey /v DriverMinorVersion /t REG_DWORD /d 0 $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\vwififlt\Parameters" reg add $RegKey /v DefaultFilterSettings /t REG_DWORD /d 1 # vwifimp not in core image #$RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\vwifimp" #reg add $RegKey /v Type /t REG_DWORD /d 1 #reg add $RegKey /v Start /t REG_DWORD /d 3 #reg add $RegKey /v ErrorControl /t REG_DWORD /d 1 #reg add $RegKey /v Tag /t REG_DWORD /d 15 #reg add $RegKey /v ImagePath /t REG_EXPAND_SZ /d "\SystemRoot\System32\drivers\vwifimp.sys" #reg add $RegKey /v DisplayName /d "@%SystemRoot%\System32\drivers\vwifimp.sys,-261" #reg add $RegKey /v Group /d NDIS #reg add $RegKey /v Owners /t REG_MULTI_SZ /d "netvwifimp.inf" #reg add $RegKey /v TextModeFlags /t REG_DWORD /d 1 #reg add $RegKey /v NdisMajorVersion /t REG_DWORD /d 6 #reg add $RegKey /v NdisMinorVersion /t REG_DWORD /d 40 #reg add $RegKey /v DriverMajorVersion /t REG_DWORD /d 1 #reg add $RegKey /v DriverMinorVersion /t REG_DWORD /d 1 #$RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\vwififlt\Enum" #reg add $RegKey /v Count /t REG_DWORD /d 1 #reg add $RegKey /v NextInstancet /t REG_DWORD /d 1 #reg add $RegKey /v 0 /d "{5d624f94-8850-40c3-a3fa-a4fd2080baf3}\vwifimp_wfd\5&e58d9b&0&01" # WdiWifi $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\wdiwifi" reg add $RegKey /v DisplayName /d "WDI Driver Framework" reg add $RegKey /v ErrorControl /t REG_DWORD /d 1 reg add $RegKey /v ImagePath /t REG_EXPAND_SZ /d "system32\DRIVERS\wdiwifi.sys" reg add $RegKey /v Start /t REG_DWORD /d 3 reg add $RegKey /v Type /t REG_DWORD /d 1 # legacy WiFi adapter - recommended by Unified Windows PE 3.1 builder script for WAIK, with wifi and EFI support $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\Enum\Root\LEGACY_WLANSVC" reg add $RegKey /v NextInstance /t REG_DWORD /d 1 # numbers are decimal reg add $RegKey\0000 /v Service /t REG_SZ /d Wlansvc reg add $RegKey\0000 /v Legacy /t REG_DWORD /d 1 reg add $RegKey\0000 /v ConfigFlags /t REG_DWORD /d 0 reg add $RegKey\0000 /v Class /t REG_SZ /d LegacyDriver reg add $RegKey\0000 /v ClassGUID /t REG_SZ /d "{8ECC055D-047F-11D1-A537-0000F8753ED1}" reg add $RegKey\0000 /v DeviceDesc /t REG_SZ /d "@%SystemRoot%\System32\wlansvc.dll,-257" $RegKey="HKLM\WinPE_SYSTEM\ControlSet001\services\WlanSvc\Enum" reg add $RegKey /v 0 /t REG_SZ /d "Root\LEGACY_WLANSVC\0000" reg add $RegKey /v Count /t REG_DWORD /d 1 reg add $RegKey /v NextInstance /t REG_DWORD /d 1 reg unload HKLM\WinPE_SYSTEM reg unload HKLM\WinPE_SOFTWARE # Windows Connection Manager - Wcmsvc ** Not required and removed as dependancy ** # Startup Wifi Add-Content "$WorkDir\mount\Windows\System32\Startnet.cmd" "netcfg -l %SystemRoot%\Inf\netnwifi.inf -c s -i MS_NativeWifiP" Add-Content "$WorkDir\mount\Windows\System32\Startnet.cmd" "netcfg -l %SystemRoot%\Inf\netvwififlt.inf -c s -i ms_vwifi" Add-Content "$WorkDir\mount\Windows\System32\Startnet.cmd" "net start dot3svc" Add-Content "$WorkDir\mount\Windows\System32\Startnet.cmd" "net start wlansvc" }[/quote]
     
Thema:

[wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files?

Loading...
  1. [wimlib-imagex] From 16299.64 to 16299.125 leaves WinSxS\Temp\ files? - Similar Threads - wimlib imagex 16299

  2. Notification toast on windows 1703 build 16299

    in Windows 10 Installation and Upgrade
    Notification toast on windows 1703 build 16299: Hi there, We are using an API to send notification toast to windows 10 we have several builds, and we saw that the image in the toast using the XML template instead the old blue info icon / yellow warning. On 1903/1909 other builds we have, we have the nice notifications...
  3. Windows 10 ver.1709 build 16299

    in Windows 10 Performance & Maintenance
    Windows 10 ver.1709 build 16299: Hi, I have tried versions 1809, 1903 and now I'm using 1709 build 16299. I have Windows updates turned off in gpedit.msc. I'm into benchmarking with Futuremark programs like 3DMark which comes with Firestrike, Time Spy and several others. I also have VRMark installed and...
  4. Window 10 16299 update

    in Windows 10 Installation and Upgrade
    Window 10 16299 update: What is the download size of window 10 16299 update? https://answers.microsoft.com/en-us/windows/forum/all/window-10-16299-update/c3a5a7e5-85b9-4e0b-9955-68201c30ec76
  5. Windows 10 update Issue, 16299

    in Windows 10 Installation and Upgrade
    Windows 10 update Issue, 16299: Current Version : Windows 10 Pro , 1709KB 16299 Error messages on updating Windows 10 (alreday tried Windows10upgrade9252.exe) Feature update to Windows 10, version 1803 - Error 0x8007007e2018-05 2018-05 Update for Windows 10 Version 1709 for x64-based Systems (KB4134661)...
  6. Update from Windows 10 Version 14393.2214 to Version 16299.

    in Windows 10 BSOD Crashes and Debugging
    Update from Windows 10 Version 14393.2214 to Version 16299.: I have tried to update from Windows 10 Version 14393.2214 to Version 16299. Long waits and many false dawns later, the software spools back to the original version. There is plenty of memory, so that is not the problem. What to do?...
  7. upgade Win 10 from 16299 to 1709 only and no further

    in Windows 10 Installation and Upgrade
    upgade Win 10 from 16299 to 1709 only and no further: Hi, I have a 16299 installer of Windows 10 pro. For some software testing I'm performing, I only want to go as high as 1709 without going to 1803 or above. How can I accomplish this? Thanks!!...
  8. Cannot update from 10586, v 1511, to 16299, v 1803

    in Windows 10 Updates and Activation
    Cannot update from 10586, v 1511, to 16299, v 1803: My laptop runs Win10, 10586 and when I boot up I have been getting the message to update. No matter what I do like follow the instructions, use an iso file to update the update fails. Loading, verification and installation seem o.k., but everytime it fails. The error code...
  9. Cannot access C drive from android devices since upgraded to 16299

    in Windows 10 Network and Sharing
    Cannot access C drive from android devices since upgraded to 16299: I have an irritating problem since 16299 came out. I have set up full shares on laptop on C, F and G partitions (F and G on separate drive) N&S is setup up so all shares are visible etc, no passwords required, permissions set to everyone with full access rights. If I...
  10. Insisting not responding - win 10 build 16299 -

    in Windows 10 Performance & Maintenance
    Insisting not responding - win 10 build 16299 -: I would like to know the best approach to investigate on why most of applications randomly not responding. I have about 30 machines with several applications with this continuously and general not responding issue > specially with the domain users ( with the local admin...