Customize Windows 10 Image in Audit Mode with Sysprep  

So has anyone tried RTM and seen if there are any fixes to Sysprep? I highly doubt there are, but I've got my fingers crossed.

I should be able to test it in the next 48 hours.

Number one on my fix list is making sure the Modern apps are no longer broken after generalizing the image, especially when making a local user account before generalizing. This successfully worked in Windows 7 without breaking anything and Windows 8.1 without breaking the apps, so this should be possible on Windows 10, as well.

Tested Scenario:
1. Install Windows.
2. Enter Audit Mode.
3. Generalize the image (without an unattend file or any customizations).
4. Go through OOBE, answering all questions with defaults, except not using a Microsoft user account but instead a local user account and not adding the computer to a domain.
5. Login to the computer using the newly created local user account.

I would give this scenario an overall pass. Unlike the Insider 10240 build, all of the Modern apps that I tested worked.

One minor annoyance is that when I clicked on the tile of each app, a little progress bar appeared within the tile, and it took quite a few seconds before each one started. I’m not sure what that’s about, and it could be an annoyance in an academic environment that uses DeepFreeze (or similar)

Next, I want to test another scenario: basically the same as above, with the addition of an extra two steps between Step 3 and Step 4: (a) create a local user account and (b) login to that local user account.

They fixed Updates within Audit Mode - you can now run Windows Update and install them and everything works fine.

Running Sysprep with "Enter Audit Mode" and Generalize ticked still breaks the start menu, search etc though.

Kari said:

I have some mixed results, more successes than failures using certain workarounds. I will continue testing and post my results in a few days.

Amazing news. I've posted it up here too so hopefully Microsoft asknowledge it and fix it :)
Audit Mode Shutdown

Hello Kari,

I'm using Micrsoft Windows 10 Enterprise 10240 X64.
Before I know you couldn't change the Start Menu with Sysprep, I have installed Classic Shell: http://www.classicshell.net/, a custom Start Menu program for getting the Real Start Menu back. Because you told me that it didn't work and I also have tested it you're absolutely right. So I have removed Classic Shell, and sysprep all the thing made a username, programs works great, but here is the problem when I want to try to reinstall Classic Shell, the Start menu doesn't work anymore, when you click onto Start it will open and then about a few seconds without clicking anything he will kick you're out of the Menu. Do you know how I can fix this?

Greetings: DJHallo.

P.S. I think there is a problem because the pc used the Settings from Classic Shell what I installed before, do you know where to removed that, so I can make it work again? If this isn't the problem then can you please help me.

DJHallo said:

Hello Kari,

I'm using Micrsoft Windows 10 Enterprise 10240 X64.
Before I know you couldn't change the Start Menu with Sysprep, I have installed Classic Shell: http://www.classicshell.net/, a custom Start Menu program for getting the Real Start Menu back. Because you told me that it didn't work and I also have tested it you're absolutely right. So I have removed Classic Shell, and sysprep all the thing made a username, programs works great, but here is the problem when I want to try to reinstall Classic Shell, the Start menu doesn't work anymore, when you click onto Start it will open and then about a few seconds without clicking anything he will kick you're out of the Menu. Do you know how I can fix this?

Greetings: DJHallo.

P.S. I think there is a problem because the pc used the Settings from Classic Shell what I installed before, do you know where to removed that, so I can make it work again? If this isn't the problem then can you please help me.

Try the "release candidate" version from Classic Shell's website

cbjason said:

Try the "release candidate" version from Classic Shell's website

I'm already using: Release candidate 4.2.3.

Kari said:

Checking "under the hood" reveals that although native apps are shown in Start when setting up Windows with an initial local account, they are in fact not always installed for that user. The progress bar indicates the installation and should only appear when the app in question is launched first time.

I think you are right. I could see this being a problem in educational environments.

In schools, they often deploy the machines with products like Deepfreeze. This lets students do whatever they want and then the changes are reverted after reboot.

So, what will happen is that a student will start an app and it's then installed. But when the student reboots the machine, that installation is wiped away.

Could be a problem, but the apps I've used installed in just a second or two so maybe not a huge problem. Have they is stalled fast for you?

Great News Classic Shell does work, the only problem was you have to wait for loading all the stuff onto it, and I got many Apllications on there because my ISO is 17,5GB.
And I'm still not done.