This looks like a great way to debloat Windows on Install.

[wade7575]

I seen this video and thought I would try making a file and use it the next time I reinstall Windows 10 or 11.

It allows you to get rid of a ton a crap that's included within Windows and it also makes a 1000mb recovery partition to stop the error with Windows that you get as well.

This a link to the website that you can use to generate the file.

https://schneegans.de/windows/unattend-generator/

 

[EarthDog]

it also makes a 1000mb recovery partition to stop the error with Windows that you get as well.

....what is that? I don't get an error in windows without....

I dont understand this. Why would we want to expand that partition?


It's been so long since I stripped an OS...and even then, it was only for benchmarking. With today's processors, it's not really needed, but a good way to be cleeean. lol



Also, is it just me... text talks about stripping windows, then an unrelated video about expanding a partiton, then back to a link for stripping windows??

 

[Woomack]

....what is that? I don't get an error in windows without....

I dont understand this. Why would we want to expand that partition?


It's been so long since I stripped an OS...and even then, it was only for benchmarking. With today's processors, it's not really needed, but a good way to be cleeean. lol



Also, is it just me... text talks about stripping windows, then an unrelated video about expanding a partiton, then back to a link for stripping windows??

There is an error in some of the latest cumulative updates. It affects Win10 and Server 2022. In short, the update has ~600MB. The installation requires a Windows recovery partition, but the partition has 500MB. This is why you need more than 600MB (a safe option seems to be 1GB).

Install Win11, and there won't be any problem, but Server 2022 is like Win10 and there is nothing newer. I just don't get how MS could release an update that requires manually resizing a locked partition (it's not so simple to do that).

 

[EarthDog]

Thank you for the clarification!! Good to understand reasons WHY to do things.........thread is all over the map to me, lol.

Since I'm on 11 and not seeing these errors, there's no need to expand that partition.

 

[Railgun]

Would be nice to also have a list to disable unneeded services as part of the config. Would also be nice to be able to easily slipstream drivers too.

Surely wouldn't put anything of use in that site...product key? Nope.

 

[Woomack]

Some weeks ago, I checked Ghost Spectre Win11, and it works fine - link. I still disabled some things, but most useless (at least for me) services are not installed.
Generally, I don't care, as if you run Win11 Pro, you can easily disable most things, and even if you won't, it doesn't slow down the OS much (or I can barely see it). Worse is when you keep some hardware manufacturer software, like 10 ASUS services or other things like that.
A quick way can be to install a fresh OS, update it, install CCleaner, turn off whatever you dislike, and uninstall MS services/programs you won't ever need.

 

[JLK03F150]

There is an error in some of the latest cumulative updates. It affects Win10 and Server 2022. In short, the update has ~600MB. The installation requires a Windows recovery partition, but the partition has 500MB. This is why you need more than 600MB (a safe option seems to be 1GB).

Install Win11, and there won't be any problem, but Server 2022 is like Win10 and there is nothing newer. I just don't get how MS could release an update that requires manually resizing a locked partition (it's not so simple to do that).

There was one Win 10 update at the root of the problem & it is my understanding that it was a file size mistake by MS. I thought they pulled the update, but showed up during an update recently. The update is the 2024-01 Security Update (KB5034441). I am not going to manually resize that partition on multiple machines, instead I've used "Win Update Show Hide" to remove the failed update from the Check for Updates lists.

 

[Woomack]

When you install Server 2022, after the initial few small updates, it will get stuck at this cumulative one. I don't know if you can turn it off as it locks all next updates. Once the recovery partition is larger, then are many other updates. I had that some weeks ago when I was reinstalling virtual machines.

If you know how to use diskpart, then it's 5 minutes tops, and you make it.

Btw., I'm surprised there is no Server 2022 R2 or 2024/25 announcement. The 2022 version was released three years ago, even though it's based on a nine-year-old Win10. It doesn't matter much, until you wish to use devices with Win11 drivers. Officially, many devices are not designed for Server 2022, even less than for Server 2016. Usually, Win10/11 drivers work, but more often there is an installation error. I had that with some newer network cards. For example, some Intel drivers won't work, while Realtek always works. The same Realtek audio works on Server 2022, while most other brands do not. Maybe 1% of users will need audio on Server OS, but still.

 

[Flamethrower1972]

I seen this video and thought I would try making a file and use it the next time I reinstall Windows 10 or 11.

It allows you to get rid of a ton a crap that's included within Windows and it also makes a 1000mb recovery partition to stop the error with Windows that you get as well.

This a link to the website that you can use to generate the file.

https://schneegans.de/windows/unattend-generator/

I like the video to me it makes sense but that is a lot of stuff to type in a common prompt.

 

[wade7575]

....what is that? I don't get an error in windows without....

I dont understand this. Why would we want to expand that partition?


It's been so long since I stripped an OS...and even then, it was only for benchmarking. With today's processors, it's not really needed, but a good way to be cleeean. lol



Also, is it just me... text talks about stripping windows, then an unrelated video about expanding a partiton, then back to a link for stripping windows??

I didn't bother explaining a lot about the recovery partition because I figured most people had that problem and would know right away what I was getting at.

 

[EarthDog]

I didn't bother explaining a lot about the recovery partition because I figured most people had that problem and would know right away what I was getting at.

No worries! Just a W11 user who dodged that bullet, LOL!

 

[Janus67]

Honestly have not had the issues on my windows 10 machines or anywhere in our enterprise

 

[dejo]

the windows update that causes the issues is KB xxxxx4041

 

[EarthDog]

the windows update that causes the issues is KB xxxxx4041

The update is the 2024-01 Security Update (KB5034441).

Which one is it?

 

[JLK03F150]

 

[Woomack]

I don't remember exactly, but more than two KBs cause problems. It depends on your OS version and if you had other updates before. I can't find it now, but also for Server 2022 is a different one.
I haven't used Win10 for a long time, and at work, no one has used Win10 for about two years. However, there is still a problem with a clean/freshly installed Server 2022 (so I assume that with a fresh Win10, too). It seems like there is no problem when the OS was up to date before the cumulative update was released. At least I have no problems with any of the older Server 2022 installations at work.

 

[dejo]

it is the 4441, sorry- its been a while

 

[Kenrou]

it's stuff like this that makes me glad I don't let windows auto update