Everything after OobeOEMRegisteration is the prompts for OneDrive, Edge, Office, Gamepass {those 4 are skipped when using a local account} and then a Telemetry Flush. As far as I know, the Telemetry Flush doesn't make a massive difference, but I would still let it run as it does a few things if you are connected to the internet and runs even when using a local account, don't want anything unexpected to happen. In order to skip updates, modify the following to replace OobeNDUP with OobeExit. OobeNDUP is what runs Windows Update, OobeExit is what kills the setup and logs you in to your new account. Code: "OobeTelemetryFlush": { "successID": "OobeNDUP", "failID": "OobeNDUP", "cancelID": "OobeNDUP", "abortID": "OobeNDUP", },
Be aware that dism operations will fail if you do "DISM.exe /Image:\a /Cleanup-Image /RestoreHealth" or probably if you update. Unfortunately editing system files not result good. There is so many protection day by day. Code: 2024-11-01 13:03:36, Info CSI 00000009 Hashes for file member [l:15]'navigation.json' do not match. Expected: {l:32 ml:33 b:cb13f045006606b15d3a97594fc4b120558e4b7e837d42ea408d354fc9229288}. Actual: {l:32 b:322ce030d460f4aa31dde66391aac1c87c6feb063f026b8ff6ca02acf08963e7}. 2024-11-01 13:03:36, Info CSI 0000000a Warning: Unable to repair payload file ([l:15]'navigation.json') for component ([l:98 ml:140]'amd64_microsoft-windows-c..riencehost.appxmain_31bf3856ad364e35_10.0.26100.1_none_ffac2132b62c9074') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU. 2024-11-01 13:07:41, Error CSI 0000000b@2024/11/1:10:07:41.402 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
Users should be aware that their component base store will be marked as corrupted if they change "navigation.json". Dism will give famous (0x800f081f) errors. When i change with original file my cbs store corruption solved. Best way to get rid of wireless setup is just add one line registry value to offline wim. I also was glad and hope changing "navigation.json" could be good way but unfortunately it showed not. Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE_00\Microsoft\Windows\CurrentVersion\OOBE] "BypassNRO"=dword:00000001
If you do not care of updates ok. But users should be aware of if they want to update their system usually if dism restore health or resetbase gives error adding/online updating system gives error too. If restore health says cbs corrupted means all system health is corrupted. It is not just something that omg who cares. I warned and do not care too. Go on good luck.
At the end of the day I wasn't expecting this patch to be used a lot. Its more so an experimentation to see how the setup works if you want to call it that. Don't forget this isn't the main purpose of this thread. It all started from a completely different method that I shared to do the same thing that doesn't require any file modifications.