Olie

Anyone ever find a solution to this? One of my (many) current problems with Windows 10 and SCCM is very similar. If I use a WinPE v10.0.10586.0 boot image to deploy my Windows 10 OSD Task Sequence then the CM Package fails to install at the Setup Windows and Configuration Manager step. The msi logs show that the problem is caused by a failure to register StatusAgentProxy.dll. This happens every time (well over a dozen attempts now). I am also unable to install the CM agent once Windows 10 is then booted, each time getting the same error about StatusAgentProxy.dll. Everything on the web indicates VC++ 2008, but installing various versions of this makes no difference, and it isn't required on clients that DO successfully install the CM Client. Now interestingly if I use a WinPE v6.3.9600.16384 boot image to deploy the same Windows 10 Task Sequence then the CM Package successfully installs, with no issues. I'm utterly confused by this and it seems to make no logical sense - why would the boot image used affect the capability of installing the client in Windows itself!? I have other issues with using WinPE 6, so am desperate to get WinPE 10 working. For info I have tried building the WinPE 10 boot image at least 6 times in various ways (MDT in SCCM, script, removing/adding extra components etc) but every time I get the StatusAgentProxy.dll error. Totally