Solved During an unattended setup, how can I skip the check for updates?

hsehestedt · Mar 20, 2025

Just saw your post after I posted mine.

Maybe I'm simply not doing this right...

I added that registry entry in like this:

garlin · Mar 20, 2025

reg add (on the command line) is always in decimal.
reg import (in the .reg file) is always in hex.

/t REG_DWORD /d 1

krism · Mar 20, 2025

garlin said:
Run the reg command during specialize pass. Specialize always finishes before OOBE.

@krism, you miss the point. 24H2 introduced two major changes:
1. WinPE Setup defaults to a newer setuphost client. This change has broken many tried-and-true process steps that worked prior to 24H2.

No, my point is exactly that - use customization and you increase the likelihood that things won't work the same. QED.

garlin said:
2. Forcing mandatory OOBE updates, even though users previously had the choice to use Dynamic Updates to perform the same task. MS doesn't force anyone to use Dynamic Update, but now they're making an arbitrary choice for you.

Further this change was originally expressed as for enterprise (ie. Autopilot) customers only, and not for retail users.

pseymour · Mar 20, 2025

It has nothing to do with the customization, mate. Some apps break when Windows is updated beyond a certain point, because of some change to the OS. Same thing happens sometimes with frameworks and runtimes, although less common in my experience. Sounds like garlin has seen that in his career; I know I have.

krism · Mar 20, 2025

as you wish! :)

hsehestedt · Mar 20, 2025

garlin said:
reg add (on the command line) is always in decimal.
reg import (in the .reg file) is always in hex.

/t REG_DWORD /d 1

In this case it does not matter because "1" is the same in decimal as it is in hex as it is in binary.

garlin · Mar 20, 2025

OK, I tried the reg command by hand. 0x00000001 is accepted :crys:

dacrone · Mar 20, 2025

hsehestedt · Mar 20, 2025

Okay, just tried integrating it directly into the boot.wim and it still does not work.

For now, I will simply make sure to disable networking.

hsehestedt · Mar 20, 2025

garlin said:
OK, I tried the reg command by hand. 0x00000001 is accepted

Yeah, I have literally dozens of registry entries working like that which is why I was so confident in my response

dacrone · Mar 20, 2025

Code:

<File path="C:\Windows\Setup\Scripts\unattend-01.cmd"> start "" REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\CloudContent /v DisableCloudOptimizedContent /t REG_DWORD /d 1 </File>

<File path="C:\Windows\Setup\Scripts\unattend-02.reg"> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent] "DisableCloudOptimizedContent"=dword:00000001 </File>

throw em both in there (cmd and reg) and see if it takes lol

hsehestedt · Friday at 12:00 AM

dacrone said:

Code:

<File path="C:\Windows\Setup\Scripts\unattend-01.cmd"> start "" REG ADD HKLM\SOFTWARE\Policies\Microsoft\Windows\CloudContent /v DisableCloudOptimizedContent /t REG_DWORD /d 1 </File>

<File path="C:\Windows\Setup\Scripts\unattend-02.reg"> Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent] "DisableCloudOptimizedContent"=dword:00000001 </File>

throw em both in there (cmd and reg) and see if it takes lol

Maybe I'm misunderstanding, but I already know with 100% certainty that the registry entry has been successfully applied. It just is not solving the issue for me.

dacrone · Friday at 12:42 AM

hsehestedt said:
Maybe I'm misunderstanding, but I already know with 100% certainty that the registry entry has been successfully applied. It just is not solving the issue for me.

gotcha. my misunderstanding then. i interpreted that as the you know the reg was correct but it wasn't applying it. so it is applying it but does not have the desired effect is what you're stating, correct?

hsehestedt · Friday at 1:13 AM

dacrone said:
gotcha. my misunderstanding then. i interpreted that as the you know the reg was correct but it wasn't applying it. so it is applying it but does not have the desired effect is what you're stating, correct?

Bingo. That is precisely correct.

But in the meantime, I have figured out a solution. It's not pretty or elegant, but it works. The solution was to simply disable networking in the Specialize phase like this:

<RunSynchronousCommand wcm:action="add">
<Description>Disable Networking</Description>
<Order>1</Order>
<Path>powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"</Path>
</RunSynchronousCommand>

The only thing remaining now is to run a command after Windows starts for the first time to enable networking like this:

powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"

The interesting thing is that I have never had a need to run anything after setup has completed, so I've never done this before, but I think that I am familiar with the procedure. I just need to test it. But in the very worst case I would simply need to go into Device Manager and enable the net adapter(s), but I think that I got this

dacrone · Friday at 1:49 AM

hsehestedt said:
Bingo. That is precisely correct.

But in the meantime, I have figured out a solution. It's not pretty or elegant, but it works. The solution was to simply disable networking in the Specialize phase like this:

<RunSynchronousCommand wcm:action="add">
<Description>Disable Networking</Description>
<Order>1</Order>
<Path>powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"</Path>
</RunSynchronousCommand>

The only thing remaining now is to run a command after Windows starts for the first time to enable networking like this:

powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"

The interesting thing is that I have never had a need to run anything after setup has completed, so I've never done this before, but I think that I am familiar with the procedure. I just need to test it. But in the very worst case I would simply need to go into Device Manager and enable the net adapter(s), but I think that I got this

I’m not on your level with install media manipulation but executing commands post-install is something I can do. So if you need help and Garlin is busy, let me know

hsehestedt · Friday at 2:20 AM

dacrone, I saw your message while I was typing this. Thankfully, I already have it all sorted out.

The solution was to add another RunSynchronousCommand entry but this time under oobe System > Shell-Setup > FirstLogonCommands that is identical to the one that disables the network, except that I replace "Disable" with "Enable".

But for all your help and offer of further help, I am really grateful and gave you 10 points for the excellent support

dacrone · Friday at 2:23 AM

hsehestedt said:
dacrone, I saw your message while I was typing this. Thankfully, I already have it all sorted out.

The solution was to add another RunSynchronousCommand entry but this time under oobe System > Shell-Setup > FirstLogonCommands that is identical to the one that disables the network, except that I replace "Disable" with "Enable".

But for all your help and offer of further help, I am really grateful and gave you 10 points for the excellent support

I try. I learn from Magnificent 7 here. I’ll join y’all in the major league one day!

hsehestedt · Friday at 2:36 AM

Here is a final summary before I mark this issue as resolved:

How to prevent Windows updates from being applied during Windows setup using an Autounattend.xml Answer File.

Add to pass 4 specialize > Windows-Deployment > RunSynchronous > RunSynchronousCommand with the following values:

Order: 1 (if 1 is in use, use next available number)
Path: powershell.exe -Command "Get-NetAdapter | Disable-NetAdapter -Confirm:$false"

This will disable all network adapters which will also cause bypassing of Windows updates during setup.

Next, we need to re-enable network adapters at the end of setup. To do so, add this:

Add to pass 7 oobe System > Windows-Shell-Setup > FirstLogonCommans > RunSynchronous > SynchronousCommand with the following values:

Order: 1 (if 1 is in use, use next available number)
Path: powershell.exe -Command "Get-NetAdapter | Enable-NetAdapter -Confirm:$false"

Amazing how simple it is, once you finally figure it out with the help of some really helpful folks like @garlin and @dacrone.

hsehestedt · Friday at 2:54 AM

dacrone said:
I try. I learn from Magnificent 7 here. I’ll join y’all in the major league one day!

Don't sell yourself short! You've been kicking a$$ and taking names

.

BTW, apologies, I may be a little slow here but I'm not following the "Magnificent 7" reference in this context.

dacrone · Friday at 12:34 PM

Magnificent 7, 4 Horsemen, Kliq... just meaning the best at each respective 'position' (SMEs or subject-matter experts for different aspects). You're the WIMaster, Edwin is VisualVoyager, and some more. i have my list of whom to take notes from for certain topics

Solved During an unattended setup, how can I skip the check for updates?

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

incompatible with most users and devices

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Similar threads