New
#21
I thought that the newly released KB5001330 (build 1904x.928) was supposed to fix that problem?
I thought that the newly released KB5001330 (build 1904x.928) was supposed to fix that problem?
Was it written somewhere?
The update fixes the 0x800f081f error that existed in the Insider Channel.
It does not fix error 0x8007000d or, as with them, 0x800f0984.
Ok understood...I went ahead and did the "in place upgrade" and that seemed to fix the Windows update error 0x800f0984.
All is good now and I'm presently on W10 Pro version 21H1 build 19043.928 and all is up to date with no errors.
Thanks again for your assistance...
Thanks for your feedback.
Glad to hear you fixed it.
You’re welcome.
well the new update from this tuesday..pffft.. same as last one. NO go. update error again. Funny how when they offered 21H1 to the insider beta. How could I install it. then over the course of the first week using it there was multiple updates and cumulative ones and they ALL worked perfect no errors. Then once this one KB5000842 showed in my updates I get error? I didnt do anything different on my PC nothing I set up. My PC is exactly the same as it was when I first installed 21H1. I have reinstalled windows like 10 time now in the last 6 months from errors on microsfots end. I am not doing some crazy in place upgrade etc I am so sick of RE doing all my settings etc. So now what I am going to do is just live without the updates until 21H2 comes out then ill upgrade/update and deal with redoing settings then..im fine with that. Just felt like posting my experience with this recent catastrophe here guys. And yes I know if I dont like it DONT JOIN THE INSIDER PROGRAM..lol..nough said. Good luck to those trying to cure this headache.
@imanalien
Unfortunately I can’t understand.
I haven't had any update errors so far and I've been using the 21h1 since the first day of publication.
I recently wrote it in another community:
I never use the disk cleanup feature except on the computer where I installed Windows Insider Dev Build.
But then only before installing the new build.
And I never clean up the WinSxS folder as described there:
Clean Up the WinSxS Folder | Microsoft Docs
These are the two most common problems.
Except for corrupt files if there is another problem on the system.
Which doesn’t mean that I’m protecting Microsoft.
From my point of view, such errors should of course not happen when I use disk cleanup, for example.
Friendly greetings
Last edited by Tekkie Boy; 16 Apr 2021 at 02:52.
Very interesting about Disk Cleanup. I run that every now and then, thinking I do a good thing. Where in fact, it seems to have been the other way around.
I fully agree, it's really bad if MS's own system tools designed to keep the system fresh and clean instead make it not work correctly if used.
And I do use the Disk Cleanup feature Simply because everywhere I read its the only true way to delete Old Windows files. Because I use SSDs which according to many using an app like Ccleaner is not the way to go even though I use to use Ccleaner for years without issue. So I cant imagine its a bad thing to use Disk Cleanup? So how do you delete old Windows files that as you know can be many GB worth of Hard Drive space?
Window.old is deleted by itself after 10 days.
Otherwise I sometimes clean up temp files with the help of the Farbar Recovery Scan Tool.
But I don't clean anything else.
I also have very few programs installed for my purposes.
So instead of battling the constant crazy errors, I switched to the Dev channel and installed that update and guess what..it worked perfect..lol..windows what a nightmare.