Jump to content

Recommended Posts

Posted

Not really sure which forum to put this in, as it seems to be an issue for lots of servers and clients.

 

MS released a security update in Jan that would fail due to the Windows recovery partition not being large enough for the update.

 

I blocked the update until I could see if MS were going to fix the issue, but it now seems like MS are just going to deploy this update as part of the monthly CU updates in Feb.

 

I have just done some testing and managed to resize the recovery partition on a test 2022 server, using cmd diskpart, but I don't really want to have do do that on production systems.

 

Just wondering how many of you have,

Already come across this issue and have you already increased the recovery partition size? or are you waiting to see what happens in Feb updates?

Posted

If you are not using Bitlocker on the server/client there isn’t a risk.

 

The vulnerability requires physically access.

 

If it’s only clients that are using bitlocker. Then I would be tempted to wait to get them upgraded to win11 and do the resizing then.

 

I did a script for clients and some servers that aren’t using WSUS/MECM.

 

The fact that MS didn’t push to WSUS says something about the confidence of the patch.

 

I’m going to see what patch Wednesday brings.

  • Thanks 1
Posted
If you are not using Bitlocker on the server/client there isn’t a risk.

But having the update rolled into February CU updates, means the entire CU update could fail.

 

If it’s only clients that are using bitlocker. Then I would be tempted to wait to get them upgraded to win11 and do the resizing then.

Again, this wouldn't be an issue if its not part of the next CU update.

 

Lets see what happens next week :-)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...