1 Reply Latest reply on Nov 30, 2017 1:24 AM by MarkusMichalski

    W10, 1709, WINPE4, W10 Setup Fails after third reboot and W10 setup itself with NEW BOOT ENVIROMENT

    bretzeli Expert

      * LATEST DSM 2016.2 R2 download and working installation

      * AIK 8.1 on SRV2012R2, WINPE4.0

      * Had 1709 W10 64Bit running and working fine NOW with change of Boot Enviroment DOES not work at latest REBOOT of W10 Setup

       

      We had an existing SETUP with 1709 W10 FALL UPDATE with the workaround Trick of the Edition. > THIS worked under VMWARE

       

      We now wanted to change our working existing "Boot Enviroment WIN PE4/5 64BIT" and UPDATE Storage and Mass Drivers.

       

      Since then:

       

      1) PE runs OK

      2) Formating and Part runs through

      3) OSD copyed the 1709 and beginn installing

      4) AFTER the third reboot we get an error

       

       

       

      We have BELOW WARNING in CBS_UNATTEND.* also on MACHINES/CLIENTS where

      the setup worked. So the below Yellow marks are NOT the source of ours problemes:

       

      2017-11-15 12:07:10, Warning               DISM   DISM Provider Store: PID=1140 TID=1112 Failed to load the provider: O:\Extern$\sources\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

      2017-11-15 12:07:10, Warning               DISM   DISM Provider Store: PID=1140 TID=1112 Failed to load the provider: O:\Extern$\sources\FfuProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

       

       

       

      In the $EXTERN package of the OS Setup we use we DO NOT see the files Ffuprovider.dll or SILOEDpackageprovider.dll.

      With the SAME OS Setuüp package HOWEVEVER we already installed several other W10 1709 VM machines. VM also does not work now.

       

       

       

       

      The ONLY "Boot Enviroment" which seems to work with ACTUAL DSM Release is the one we made 19.01.2017 (Where we did not now about 1709)

      1) We copied the Existing > Changed etc.

      2) Made a complete new one last few days

      > Nothing solved it > We where searching on drivers issues not knowing that all version we made did not work under VM ANYMORE.

       

       

       

      Some reference we used:

      https://www.jc-tech.info/tag/windows-pe/

      Referenced files:

      FILE: setuperr.log ERROR > +"d:\windows\system32\config\systemprofile\netuser.dat"

       

      Remark 04.12.2017, WE also see the ERROR on machines WHICH SETUP was fully DONE OK 100% so this is also not the SOURCE of our problem.

      2017-11-15 12:07:07, Error      [0x0606ae] IBS    [SetupCl library] Required profile hive does not exist: [\??\C:\WINDOWS\system32\config\systemprofile\NTUSER.DAT].