Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
That's very strange. A clean install (just did one) creates an empty sub-tree hierarchy for AuthRoot.That key doesn't exist on this machine
Windows does not handle upgrades well, usually a second upgrade or a repair upgrade fixes that.The only common denominator I can find is it looks like all of these were upgraded from windows 10 to windows 11.
The pulse completed successfully, The last sync time still shows a date of 3/21/2024, I waited about 10 minutes to give it a chance to and did the sync time again and it still didn't change.Can you try to manual trigger the cert update to see if that works?
terminal with adminrights.
certutil -pulse
afterwards check with (can take a few seconds after pulse before output shows:
certutil -verifyctl AuthRoot | findstr /i "lastsynctime"
I still haven't found the cause, but the fix appears to be working, I'm going to have cybersecurity push a GPO to all 652 remaining computers with the issue, then I will spot check 50 or so to make sure they are doing updates.certutil also has a -syncWithWU switch that, well, syncs with WU. :)
we use lansweeper to monitor all of our network devices, I cant find a single computer on our domain with that keyThat's very strange. A clean install (just did one) creates an empty sub-tree hierarchy for AuthRoot.
Wonder if a domain-wide "extinction event" clobbered this key (or another setting) at the same time. And it doesn't show up for machines created since then.
Question, we applied a new Authroot cert to most of the affected machines, now it looks like it only does updates for a few days on that certificate then it's back to not doing updates again. Any ideas?No need to reset any folders. OP has already found that it’s a certificate issue. The only remaining item is figuring out what caused the cert issue.
Unfortunately, those logs are foreign language to me, I'm no expert in reading logs and figuring out what the issue is.Head back to the logs (post 4). They really are your friend here.
I too had some machines do this as well at my station, and was unsure why. I never thought to look at the certificates. Luckily it was only around 3 machines in our building that were doing that, so it was fixed with a reimage.I desperately need help! We have 3200+/- total domain computers all on windows 11, mostly Enterprise and some on Pro, 600+ of them haven't done updates since either November of 2024 or August of 2023. They get an error when trying to do updates that says, "We couldn't connect to the update service". I have tried many things, verified all the Registry setting were correct, update troubleshooter fails, I can ping the update serves successfully from a CMD prompt, restarted services, deleted software distribution and other folders, I can manually push updates, but it won't auto pull them. Any help would be greatly appreciated.
yea, I have so many of them, reimaging is not an option, they are spread all over the state of Arkansas. The list I pulled this morning was 414 devices.I too had some machines do this as well at my station, and was unsure why. I never thought to look at the certificates. Luckily it was only around 3 machines in our org that were doing that, so it was fixed with a reimage.
Still odd though. I will keep an eye on this thread should I come across any more.
Get-AppxPackage -AllUsers| Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Can you tell me the full syncwithWU command?
Correct, that's what I'm trying to fix. While this computer is doing updates, the Auth root cert hasn't synced since the 17th of this month. I am assuming that should be syncing every day. If I can fix this issue it will in turn resolve the update issue.I should add that, as you mentioned, your cert sync time is a little old. Until you track down what's keeping that from working, you're going to keep having this problem.