Author: Jörgen Nilsson

Winpe 1607 Dot3svc fails to load – Workaround

In WinPE 1607 Dot3svc fails to load as I and many others have noted before. Today on the comment to my post “Robert” posted the following workaround which seems to be working just fine! Copy the following files from a windows 10 1607 installation to winpe: %windir%\l2schemas\OneX_v1.xsd %winpewindir%\l2schemas\OneX_v1.xsd %windir%\system32\l2gpstore.dll %winpewindir%\system32\l2gpstore.dll %windir%\system32\onex.dll %winpewindir%\system32\onex.dll %windir%\system32\en-US\onex.dll.mui %winpewindir%\system32\en-US\onex.dll.mui

New version of OSDBackground published with support for a specific background on error

I wrote a blog post a while ago on a tool my college Johan Schrewelius has published which sets the OSDbackground during OSD and gives us the possibility to troubelshoot without F8 support enabled which should be avoided. An update of OSDBackground is now published with som bug fixes like: 1. Added Management Point to

Dump Task Sequence variables during OSD the safe way

I have used Michael Niehaus excellent script for dumping all task sequence variables during OSD which is great for troubleshooting. However it dumps all TS variables including: _SMSTSReserved variables which for instance contains the Network access account username and password in clear text. The same goes for the Domain Join account used in the

MBAM TPM Password Hash and Windows 10 1607

In Windows 10 1607 the TPM Password Hash is no longer accessible from within windows. This is design change to increase the Security in windows 10 which you can read more about here: Quote: “Starting with Windows 10, version 1607, Windows will not retain the TPM owner password when provisioning the TPM. The password