This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I have a Dell laptop that I will be getting rid of and need to wipe clean the hard drive. I cannot use the DVD drive as Windows is cannot read the CD-RW Disc, so I cannot download the data removal software DBan. Since I purchased a new laptop in Sept, I have not used the Dell laptop; hence, no updates have been installed. Now, in order to for me to try to fix the DVD drive issue, I need to run updates; otherwise, I can do nothing on the laptop.
The latest cumulative update, KB5008212 is holding everything up to where I cannot do anything. It took most of the afternoon, into the evening to download. Now, it is stuck at Installing 100%. I went to the Windows Update catalog website to manually download and install the update, but I think there was an issue with the offline installer, it took forever to find the update on the computer.
I've run Windows Update over and over, but it just goes back to KB5008212 stuck at Installing 100%. I uninstalled the third-party security software app and that has not helped. In addition, there is a Microsoft Defender Antivirus security update that is attempting to download; it is stuck at Downloading: 10%.
Is there anything I can do to get this update to install or should just leave the laptop on overnight and see what happens?
Thanks.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Glad this was helpful.
Regarding the caution one poster expressed concerning this procedure (which he called "a workaround"), as far as I can tell, there's no risk in trying this because, right at the beginning the Update Assistant checks the computer for compatibility, sufficient free space, and one other parameter that I can't recall. I'm sure if there is an issue with any of those three items, an appropriate warning or notice will appear on the monitor.
Glad this was helpful.
Regarding the caution one poster expressed concerning this procedure (which he called "a workaround"), as far as I can tell, there's no risk in trying this because, right at the beginning the Update Assistant checks the computer for compatibility, sufficient free space, and one other parameter that I can't recall. I'm sure if there is an issue with any of those three items, an appropriate warning or notice will appear on the monitor.
Absolutely....and this is NOT a workaround...it's an actual update which, at least at my end, works flawlessly.
Microsoft DO have a problem, IMO, when they sort of leave it up to their customers to find solutions to problems
that they actually brought on themselves....not good customer policy.....
Thanks again and a happy newyear to you :-)
You're missing the point this is DEFINITELY a workaround if you need to go through all that just to install a wonky security update that MS has released. We need to hold them accountable when they release these dodgy updates so they'll issue a proper fix and be incentivized to make sure future updates don't fail as well.
There are people who are not tech savvy enough to jump through a bunch of hoops to do the workaround just to install a simple update that should install automatically. I'm just not willing to put my main working studio system at risk by applying a workaround that shouldn't be needed. I have far too much valuable data on that system and many of the plugins and other software I own have not been tested for 21H2. I have had windows updates break copy protection for plugins before so it's never a good idea to update to a new version right away until developers have time to test.
If you wish not to hold MS accountable for their actions in order to force them to stop issuing buggy updates and put your system at risk that's on you.
But again I urge caution to anyone considering this workaround.
I will continue to pause updates until MS releases a proper fix as they did with the WasSMedic bug that we hounded them about for months.
I guess that we can argue on whether this is, or isn't, a workaround. Yet, here is some personal data. We have these five (5) old computers (BTW, none of them qualify for upgrading to Windows 11):
On four of the above five computers KB5008212 installed automatically and successfully - on #s 1, 3, 4, & 5. All four of these computer received the notification from Microsoft that the 21H2 Feature update is available to download & install, and when I initiated that process, the update to 21H2 successfully installed in less than 15 minutes on each of them. It was only #2 that had the problem I described in an earlier detailed post.
So, IMHO, since the KB5008212 installed successfully on four of the above computers, the issue with installing that particular update on #2 may have been caused by something specific to that computer and, similarly, it may be due to something specific on the computers of those who are having a problem with installing it. I am sure that the update installed successfully on many more computers than on those where it didn't install. From that perspective, I suppose that the process I described can be considered as a workaround, albeit a risk-free one, as I pointed out previously.
Thank You, very much, UY41. You made my day! Applied your solution and my system is now working fine, with all the issues related to the actualizations solved.
