Strange behavior noticed lately Win 10 ver 1909 18363.1139, AND RANT

Ny newest hardware is almost 2 yrs old, my oldest hardware is 10 yrs old, and it is running 2OH2 fine.

- - - Updated - - -

mega10user said:

,


This morning, the 5th time this shows up on win update. Was installed on 11 Nov 2020. Like I said, WTH..... Now an error code, 0x80070002. Guess the next few hours have to figure this out now. The web suggests running the win update troubleshooter so here goes! Yes, sfc already tried. No, nothing else... except the hint that it usually goes away and let some time go by. Times UP doncha think?

BEFORE SOMEONE JUMPS IN TO COMMENT, GIVE YOURSELF THE CHANCE TO READ THE ENTIRE POST BEFORE THIS ONE?

Reminds me of the DOD practice, R&D in the field. Doesn't matter who or what gets screwed up just so ppl see something come out.


.

I had that error recently, and doing like what ths guy did here fixed it.
Your basically removing the failed update files by renaming the folder/
https://answers.microsoft.com/en-us/...c2b9beb?auth=1

Somewhere is a more concise list to follow

Here it is, not all commands were needed for me
3) If that fails try manually resetting Windows Update Service:

Open administrative Command Prompt and type following commands one-by-one followed by Enter key.

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

Close Command Prompt and see if Windows Updates works then

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/error-0x80070002-windows-update/a4729cd0-ef78-49ff-8f74-664b73dc7d10

sdowney717 said:

Ny newest hardware is almost 2 yrs old, my oldest hardware is 10 yrs old, and it is running 2OH2 fine.

- - - Updated - - -



I had that error recently, and doing like what ths guy did here fixed it.
Your basically removing the failed update files by renaming the folder/
https://answers.microsoft.com/en-us/...c2b9beb?auth=1

Somewhere is a more concise list to follow

Here it is, not all commands were needed for me
3) If that fails try manually resetting Windows Update Service:

Open administrative Command Prompt and type following commands one-by-one followed by Enter key.

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

Close Command Prompt and see if Windows Updates works then

https://answers.microsoft.com/en-us/windows/forum/windows_10-update/error-0x80070002-windows-update/a4729cd0-ef78-49ff-8f74-664b73dc7d10

:) Thanks sdowney717 :)


:) Turns out it was crapped win update files! Since it was stuck on that latest 20H2 update from the 11th, I did some research (all those resetting win update help links were years/months/versions old). Tried various links none were what was wrong here. Tried uninstalling that latest security patch, didn't have the ability available. Downloaded that 20H2 file and its associated rqmt (KB4586864 & that 20H2 security update KB4586781) and tried to patch over it but that failed as already installed. Went ahead finally and did the command prompt (admin) and reset the win update files, looked like that didn't work because the 7 files in the 'view installed updates' were still listed (they did not delete the entries in the software installed listing). Went ahead and ran win update as instructed, and it redownloaded that last 20H2 KB4586781, it reinstalled instead of just listing it and error-ing out. So, few hours later, its still working. Who knows what adventure (NOT) will creep up in windows 10 (this laptop) next..... :)


.

mega10user said:

Updated to 2004 20H2 and now there is an automatic windows IE-11 redirect to Edge.

This automatic redirect to Chromium Edge in 20H2 only occurs when you visit a site that tells IE that it is unsupported on this site. This behaviour is new in 20H2. It can be disabled. See:

Automatic redirect of unsupported sites in IE to Edge in 20H2

Bree said:

This automatic redirect to Chromium Edge in 20H2 only occurs when you visit a site that tells IE that it is unsupported on this site. This behaviour is new in 20H2. It can be disabled. See:

Automatic redirect of unsupported sites in IE to Edge in 20H2

Thanks Brink, will try this on future machine upgrades. Already uninstalled IE from the old 10 Pro laptop . Thing was giving me fits!


.