Reserve Manager enabled with Low Disk Space block

%3CLINGO-SUB%20id%3D%22lingo-sub-2073132%22%20slang%3D%22en-US%22%3EReserve%20Manager%20enabled%20with%20Low%20Disk%20Space%20block%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2073132%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Servicing%20Gurus%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20starting%20to%20plan%20to%20upgrade%20our%20fleet%20from%201909%20to%2020H2%20using%20WUfB.%20From%20the%20Log%20Analytics%20I%20am%20finding%20the%20a%20decent%20number%20of%20our%20workstations%20are%20blocked%20with%20safeguard%20hold%20ID%26nbsp%3B29745406.%20Looking%20through%20the%20Appraiser%20Data%2C%20this%20seems%20to%20be%20caused%20by%20the%20system%20drive%20have%20less%20than%2030GB%20free%20and%20SOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CReserveManager%5CPassedPolicy%20being%20set%20to%201%20(meaning%20that%20reserved%20storage%20is%20enabled).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20computers%20that%20we%20have%20piloted%20the%20upgrade%20to%20that%20have%20low%20free%20disk%20have%20prompted%20the%20user%20to%20perform%20a%20disk%20cleanup%20or%20connect%20an%20external%20hard%20drive%2C%20but%20with%20this%20block%20they%20are%20not%20offered%20the%20update%20at%20all.%20I%20have%20enabled%20the%20%22Disable%20safeguards%20for%20Feature%20Updates%22%20policy%20on%20a%20test%20machine%20and%20it%20was%20able%20to%20complete%20the%20upgrade%20fine%20without%20any%20apparent%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20thought%20one%20of%20the%20major%20benefits%20of%20reserved%20storage%20would%20be%20the%20ability%20for%20Feature%20Updates%20to%20be%20able%20to%20be%20work%20more%20successfully%20because%20it%20could%20reclaim%20disk%20space%20from%20the%20reserved%20storage.%20But%20it%20seems%20the%20way%20the%20block%20is%20set%20up%20it%20is%20preventing%20it%20completely%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20an%20issue%20with%20Reserved%20Storage%20and%20upgrades%20at%20the%20moment%20that%20Microsoft%20is%20currently%20blocking%20the%20upgrades%20for%3F%20Or%20is%20there%20a%20problem%20here%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2146929%22%20slang%3D%22en-US%22%3ERe%3A%20Reserve%20Manager%20enabled%20with%20Low%20Disk%20Space%20block%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2146929%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F205691%22%20target%3D%22_blank%22%3E%40AndrewT%3C%2FA%3E%26nbsp%3Bthanks%20for%20sharing%20your%20feedback!%20Did%20you%20end%20up%20submitting%20feedback%20in%20Feedback%20Hub%20or%20to%20customer%20support%20%2F%20your%20account%20manager%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20passed%20along%20this%20feedback%20as%20well.%20Hopefully%20you%20are%20no%20longer%20hitting%20this%20issue!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Hi Servicing Gurus

 

We are starting to plan to upgrade our fleet from 1909 to 20H2 using WUfB. From the Log Analytics I am finding the a decent number of our workstations are blocked with safeguard hold ID 29745406. Looking through the Appraiser Data, this seems to be caused by the system drive have less than 30GB free and SOFTWARE\Microsoft\Windows\CurrentVersion\ReserveManager\PassedPolicy being set to 1 (meaning that reserved storage is enabled).

 

Other computers that we have piloted the upgrade to that have low free disk have prompted the user to perform a disk cleanup or connect an external hard drive, but with this block they are not offered the update at all. I have enabled the "Disable safeguards for Feature Updates" policy on a test machine and it was able to complete the upgrade fine without any apparent issue.

 

I thought one of the major benefits of reserved storage would be the ability for Feature Updates to be able to be work more successfully because it could reclaim disk space from the reserved storage. But it seems the way the block is set up it is preventing it completely?

 

Is there an issue with Reserved Storage and upgrades at the moment that Microsoft is currently blocking the upgrades for? Or is there a problem here?

 

Thanks

2 Replies

@AndrewT thanks for sharing your feedback! Did you end up submitting feedback in Feedback Hub or to customer support / your account manager? 

 

I have passed along this feedback as well. Hopefully you are no longer hitting this issue! 

Thanks for replying Aria. I didn't submit this issue anywhere else. 11% of our Windows 10 fleet are still showing as blocked by this safeguard hold for the 1909 to 20H2 upgrade according to Update Insights.

I am just working through upgrading our other machines for now. If the hold is still in place in a couple of months once I'm finished I can still work around the issue by disabling reserved storage which should release the hold.

It still would be great to have it listed on the release health dashboard!