Windows 11 KB5121003 Integrated install on unsupported hardware

Z

zapbuzz

New Member
Messages
4
Reaction score
0
Hello.
I use an online autounattend.xml generator to bypass windows 11 requirements.
With Windows 11 KB5121003 included in my USB installer (thanks to DISM) the computer runs fine but after awhile it starts an update loop to install KB5121003.
Can I prevent this with an autounattend.xml with the mosetup bypass reg key?
Could this update loop be kernel error caused by the windows defender updates?
 
I am currently working on this, I think the reason my integration failed to prevent the loop is that it requires an interactive user to be logged in.

So I am about to make a new image where it is installed post setup after login.

This is a very weird update.
 
A pre release cumulative patch kb5120998 has been released. I integrated it into my install USB with DISM and so far after 2 days no update loop. . I think its worth mentioning this has happened before but I forget when. I brushed it off as a bad patch last time. I remember the online activation refused to work for days with KB5121003 also and I had to use a powershell command to resynchronise the activation server. The Microsoft article on KB5121003 known issues only scrapes the surface of issues as many are not documented for being on hardware bypassed unsupported perfectly capable machines that are being replaced very slowly due to AI companies acquisition of the majority of consumer level hardware sending prices soaring and contributing to global economical inflation. Due to the nature of windows 11 on unsupported machines I recommend stay with windows 10 until the security updates expire in 2027.
 
Last edited:
For me it half solved it.
Basically both methods of integration did not prevent the update been offered post install, however when I installed the update via WU, it was instant in one second and was no longer offered.
The downside is that the update is registered as installed twice, so is noise from an audit perspective, but this is better than both alternatives of not installing the update at alll (hiding it), or the well known fix of wiping the entire local update repo (which removes all record of updates installed, very bad for auditing).
 
What I did to obtain a quiet audit experience was I used 7zip to extract SSU cab from kb5120998 and added that to the official windows 11 ISO then I added kb5120998. After this I used an ISO editing tool to replace install.wim in the windows 11 ISO. Finally I used RUFUS tool to write the ISO to my USB drive with the 2026 secure boot key option enabled. This provides a fresh quiet kb5120998 audit install of windows and probably a small update next final cumulative patch.
 
Last edited:
Your idea of doing the SSU only, to ensure the latest SSU is an interesting one.

So your method I assume if the kb5120998 was added in the updates section on ntlite, succeeded even though thats done before interactive login, as apparently the update needs a desktop session open.
 
You must log in or register to reply here.
Back
Top