"Package Microsoft.MinecraftUWP_1.2.306.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image." I suppose you created an user and installed some software in the account? If yes, delete the user accound first, reboot in the administrator account and try again.
the user here is the administrator itself meaning the administrator has the access for it. "Package Microsoft.MinecraftUWP_1.2.306.0_x64__8wekyb3d8bbwe" need to be preinstall on image to be provisioned for all user. I want a Microsoft edge with extension will get same result as mention to the problem. Same to all other Metro Apps/ Windows App that not preinstalled. Native Windows.exe application works fine. Now I'm having a difficulties to sideload official appx file since I cant download directly from Microsoft Store.
Hum.... Windows 10 1709 seems to have a problem with Sysprep. It doesn't run my First Logon script which add WinRE. Car anyone who tested with Windows 10 1709 with 4.0.8 give me the content of the log fil Under c:\Recovery\OEM\Log ? Thanks.
Ok. I found the problem. And I testing a workaround. Normally, "x86" section are run Under both x86 and X64 architecture. So, the "First logon script" just add to be put Under the "x86" section. Now, the "x86" section is executed only Under x86 architecture and X64 Under x64 architecture. This apply to 1709 but not previous build. So I had to add both section. On 1709, only one execution of OOBE will be done but Under previous version of Windows 10, this will run 2 times. So I have to put a "tag" somewhere so the second execution won't run and be ignored on previous build. I'm testing that.
Here the log file of earlier beta 4.08 (edited unattend.xml as shown on above) Code: 02/11/2017-14:31:50.46-Sysprep 02/11/2017-14:57:42.19-OOBE 02/11/2017-14:57:59.68-WinREUpdate Thu 11/02/2017-16:17:49.22-Recovery 02/11/2017-17:29:49.55-OOBE 02/11/2017-17:30:06.36-WinREUpdate After testing the recovery after the first oobe (resetting windows all drive and just file options), WinREupdate to enable file browser still keep appearing is this normal? or i need another reset, and I thought ReCreatePartitions.txt will use again to repartition the disk. here what i used on recreate partition on laptop. Code: REM - MBR for BIOS REM Partition 1 : System / NTFS / 100mb / S: REM Partition 2 : Windows / NTFS / 120go / W: REM Partition 3 : Data / NTFS / All drive / H: REM Partition 4 : Recovery Tools / NTFS / 450mb / R: select disk 0 clean create partition primary size=100 format quick fs=ntfs label="System" assign letter="S" active create partition primary size=120000 format quick fs=ntfs label="OS" unit=16k assign letter="W" create partition primary shrink minimum=450 format quick fs=ntfs label="Data" compress assign letter="H" create partition primary format quick fs=ntfs label="Windows RE tools" set id=27 assign letter="R" exit
I have created a upgrade script to update the recovery tool on a computer running Windows 10 which alreayd have them. This is to fix de possibility that, after an upgrade to 1709, the first logon script won't be run after restore (since when doing a recovery, the current build of Windows is used).
@AnarethoS Thanks for answering my question. I didnt encounter a problem on reset on my desktop which is upgraded to 1709 using 4.0.7 of your tools but edited unattend.xml script. Should i upgrade it to 4.0.8? What is the use of Config.AppAndSettings.xml and Can i retain my unattend.xml since it has same content with both architecture with custom name.?
On the copy of 1709 I have, the "OOBE.CMD" script was not executed which prevented adding the "Recovery Tools" icon in the start menu and updating the Windows Recovery Environment. I found that in the past, the X86 section was executed both on AMD64 and X86 architecture but now, AMD64 is run on AMD64 computer and X86 on X86 computer. So I have to have 2 different XML file depending of the arthitecture. Both file execute the same CMD file. It is executed after OOBE (on first boot and after a restore). Since I am unsure is a computer updating from 1703 to 1709 will execute correctly the script, I decided to create an update fonction just in case. The "Config_AppAndSettings.xml" file is used to configure ScanState to tells it waht to capture and what not. It come with ScanState. Now I don't include the XML file itself in the package since you copy it from Scanstate. This way I will always be using the version of XML file suited for the version of ScanState. If you changed the Unattend.xml file, I recommend you to split it in two files, one for X86 and one for AMD64 I did. But can do the same thing. If you have a file with X86 and AMD64 in the same file, the OOBE.CMD will be runned twice, at the same time. I can have unpredictable results. Please be aware that 4.0.8 is not completed. I have a few things to test : - Capture with a few app - Full restore - Adding some apps + recapture - Restore - Update the Tools - Restore Once everything of this "test scenario" will be OK I will consider the Windows 10 part completed. I will then have to test Windows 8 and Windows 8-Wim since I made a few change there also.
Thanks for the hard work. Waiting for stable release for "adding some apps +recapture . Will not update for now on my other laptops. My desktop which just updated to 1709 got upgraded its recovery tool to the latest beta version. I will try to reset it later. Anyway thanks. By the way, some setting like system restore option i set during audit didnt capture and other i dont remember and i used the lated beta version to date of this post.