Search Results for 'AKB2000013'

Scroll down in AKB2000013 and use the method used by @Matador – it is easier. The original method I posted was long ago when it was first needed to clear the queue.

Realize, you need to use @Matador ‘s method when you are ready to update, because it initiates download/install. It initiates a new search by Windows Update (which clears the queue. And it will respect the updates you have hidden with wushowhide and not include them.

1 user thanked author for this post.

Deo

3. testing ‘pretty link’ AKB2000013AKB2000013

No. Windows Update will search for updates, but they will remain in the queue (not download) until you click on “Download” (NOT “Check for updates”). What you see in the queue is what will download. So when you HIDE updates with wushowhide, you have to wait till Windows Update rescans and the “bad” updates disappear from the queue before you download.

Sections 3-5 of AKB2000016 may help you understand how this works (ignore about deferral).
AKB2000013 discusses clearing the WU queue. Read the top part to explain the issue, then scroll down and use @Matador ‘s method starting here. It is the best way to clear the queue.

Windows Update and wushowhide both use the Windows Update Service to search for updates.
Windows Update only searches periodically. The list of updates is finds is stored in a cache between searchings, and it is the cache you see in the WU queue. So it is STATIC between times and NOT CURRENT.
wushowhide is DYNAMIC, its update list is CURRENT when you run it. So it MAY NOT match what you see in the WU cache.
After you run wushowhide, you need to clear the WU cache and WU has to re-scan to make its list current. See AKB2000013 for how to clear the cache. It is easiest to use @Matador ‘s method (scroll down to till you see his comments).

2 users thanked author for this post.

Pim, bagman

When using AKB2000013 to clear the WU queue, scroll down and use @Matador ‘s method. It is much easier than the original method that was developed before more experimenting was done.

1 user thanked author for this post.

Deo

Just another Forum Poster wrote:

Simply select the “Pause updates for 7 days” option and then use the registry trick I discovered to “unpause” updates without having to press the Resume updates button.

Actually, that Pause/Resume procedure was discovered by @Matador back in August, 2020. See #2286979. That is the procedure being referred to in the above post. AKB2000013 was written in Nov. 2018, long before other methods were developed.
Your procedure was written in 2022.
Credit where credit is due.

The purpose of AKB2000013 is to clear the WU queue of previously hidden updates before updating, because what’s in the queue is what will be downloaded and installed.

What would possibly be a better attempt at a solution here would be to clear the DataStore\Software Distribution so that the downloaded\pending installs are eliminated. To do that, in an elevated Command Prompt (Run as Administrator) run the following commands followed by a computer Restart (not ShutDown/Restart):

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

The SoftwareDistrubution folder will be regenerated without the previous downloads.
Hopefully this will stop the reappearance of KB5022836.

2 users thanked author for this post.

Ken, Bob99

Ken wrote:

Control Panel\Installed updates indicates it was installed 3/8/23. But it kept showing up as not installed and as installation having failed.

I added the bolding above for emphasis.

@joep517 and @PKCano , since Ken has also had issues trying some of the steps in trying to reset the WU queue (as documented in post 2546499 above) would it be a good idea for him to try the procedure to reset the WU queue that’s outlined very well in AKB2000013, or will that procedure not work at all or not work too well in the Windows 11 environment? After all, it sounds like that resetting the queue will help him get rid of the repeated notices from WU trying to install the update that’s already been (seemingly successfully) installed.

EDIT to add: Given the age of the procedure in AKB2000013, might there be a better, newer procedure to purge the WU queue and the Software Distribution folder for Windows 11 than the older procedure for Windows 10?

Also, instead of resetting the WU queue, would it be a better idea to run dism in order to check for issues with the servicing part of WU and correct any issues it finds, followed by a round of sfc?

1 user thanked author for this post.

Ken

AKB2000016 and AKB2000013 (use @Matador ‘s method described part way down the thread) will give you some insight into the workings of Windows Update.

I’ve been doing well with wushowhide. Have only had to resort to fiddling with the WU service when I’ve forgotten to change the defaults I have in GPEdit for receiving Quality Updates. That’s when I was using some of the instructions that @PKCano initially mentioned in AKB2000013, which is why I’ve had to mess with WU service on occasion.

In the times that I’ve had to mess with it, I’ve never had to dip into the registry to modify anything for WU…I’ve got the Pro version of Win10, so I’ve had the “luxury” of using GPEdit.

I noticed the same thing after installing the December updates…you can’t stop and subsequently disable the Windows Update service and have it stay that way through a reboot. Turns out that there’s a service called “Windows Update Medic Service” that, to me, seems to be in charge of keeping tabs on the WU service. If it detects that WU has been stopped or if its startup type shows as “Disabled” it corrects it during the next system reboot.

I’ve tried setting this service (the WU Medic service) to disabled, but all I get is an “AccessDenied”message when I try to complete the action by clicking the “OK” button at the bottom of the window for it.

I found this out when I suffered some self-inflicted trouble due to trying to install KB5012170 after installing all of this month’s other updates.

That issue forced me to use another method to clear the WU cache besides the one suggested initially by @PKCano in AKB2000013 here on AskWoody. I wound up using, I think, @Matador ‘s method to clear the cache. That method is described further down in the thread that deals with AKB2000013.

To clear things up a bit and to confirm this was true, I tried stopping and disabling the Windows Update service on another computer that I have that had NOT had the December updates applied and then restarting it using the directions in AKB2000013. After rebooting, that computer still had the Windows Update service unstarted and its startup type was still listed as “Disabled”. However, after applying the December updates (and keeping KB5012170 hidden), that computer also will no longer let me stop and subsequently disable the WU service and have it stay that way through a reboot…the service is automatically started and the startup type is changed back to “Manual (Trigger Start)” during the reboot process!

FIXED!!

What did I do? As I mentioned above, I dumped the entire contents of the \SoftwareDistribution\Download folder. That didn’t work on its own. Then I tried rolling back to a known good restore point that I created after successfully installing and rebooting from the normal monthly updates. That was successful, but didn’t change what I was seeing from WU, that it would retry installing the failed update in the future.

Finally, after digging around some more, I found a reference to using the “Pause Updates” feature to sort of reset what you see in Windows Update after getting and hiding an unwanted download that still showed up in WU. Well, I took the plunge, and IT WORKED! WU went from telling me that it had a problem installing an update and that it would keep trying later to telling me that I’m all up to date. The failed update was also showing up in my update history, but after doing the pause updates trick, it no longer shows up there. It’s as if the event simply disappared from WU’s history completely.

In a nutshell, here’s what I wound up doing. All of it is what probably produced the results that worked.

1. After the update failed, I immediately used wushowhide to hide the miscreant update, in this case KB5012170. After hiding it, I followed PK’s long-standing advice and went into the “show hidden updates” side of wushowhide to make sure it was there.
2. I then found the cab file within the \SoftwareDistribution\Download folder and deleted it, along with the other contents of that folder.
3. Tried the steps in AKB2000013 that had worked for me in the past, but didn’t work for me this time. The Windows Update service didn’t stay disabled for me upon rebooting the computer like it’s supposed to, despite repeated efforts.
4. Successfully rolled back to a known good restore point, even though it didn’t change what I was seeing within WU.
5. With the update still showing as hidden in wushowhide, and with WU still griping that it had failed to install an update but would keep trying again, I attempted clicking the “Pause updates” button. This resulted in WU saying that updates had been paused for 7 days. After a couple of moments, I clicked the button that now said “Resume updates” and WU immediately started scanning for updates. After a bit (maybe a minute or so) it finished its check, telling me I was fully up to date.
6. I rebooted and did the same thing again just to make sure, and the same thing happened…WU told me I’m fully up to date.

I hope this helps someone else out of the same potentially sticky situation.

[Bob99]

Well, I tried to install it AFTER all of the other month’s patches were successfully installed and I’d successfully rebooted my machine and cleaned up the drive afterwards. BUT, it didn’t work, throwing the now-infamous error code of 0x800f0322. It also now shows in WU as a failed update attempt and has WU saying that it will retry later. I also now have a “Retry now” button in WU.

I promptly used wushowhide to hide the offending update and attempted the techniques described in AKB2000013 to purge the WU cache. TO NO AVAIL. I’ve been able to stop the wuausvc and set it to “disabled” for the startup type but, upon rebooting, it has automatically started again!

So, I believe that I need to now go into the Software Distribution directory and dump some files and/or folders. Problem is, I can’t remember exactly which ones at this time. I believe that dumping the correct files in that folder will also eliminate the failed installation attempt from WU and render it happy again, saying that I’m all up to date.

@PKCano , @joep517 or other MVPs, can you please refresh my memory on which files/folders in the \Windows\SoftwareDistribution directory I need to delete to get rid of this failed update attempt?

P.S. I’ve already tried just deleting the contents of the SoftwareDistribution\Download folder (after stopping the wuausvc) to no avail.

EDIT: OK, I found the post from Susan on how to reset the software distribution folder, but if the miscreant update doesn’t show at all in the \system32\catroot folder or its files, do I need to delete that folder, or can I keep it? I’m just trying to get WU to not try reinstalling KB5012170.

• This topic was modified 2 years, 4 months ago by Bob99.

When WU scans for updates, the list of available updates is put in a cache. It is the cache you see in the WU queue. That cache remains the same till the next time WU scans on its own. The list is STATIC except immediately after WU scans for updates.

When you run wushowhide, the scan is DYNAMIC (real time). After you hide an update, and rescan with wushow, the update is not listed because the scan is in actual time.

Therefore, you have to CLEAR THE CACHE in WU to make the list (queue) show the real-time pending updates. AKB2000013 discusses this. If you use @Matador ‘s method, found down the thread, it is an easier way to clear the cache (queue).

2 users thanked author for this post.

Fred, rebop2020

When you use wushowhide, click “Advanced” then uncheck “automatically make changes.” Choose “Hide” then check the ones you want to hide and follow the instructions.

Follow the instructions in #2473581. Be sure you have the “2” set in Group Policy. If you have “Pause” already set, start at the top. If “Pause is not set, and there is a list of updates in the Windows Update queue, use wushowhide to hide the ones you don’t want.

The last two steps in those instructions are essentially @Matador’s method to clear the queue. That is much easier than the long instructions in AKB2000013 that I started with. Follow the instructions to clear the queue and after WU subsequently scans for updates, the only ones that will download are the ones you chose not to hied (the ones you want).