[SOLVED] Windows 11 Update Errors 0x80070490 + 0x80070002

[Saitenschwinger]

Dear Sysnative Windows Update Team,

I'm glad I came across this forum, where there are obviously good experts who can and want to help with this problem.

Windows Update reports: “Error - We could not connect to the update service.” I haven't started this system for over a year, so I don't know when the error occurred.
Last update was 26.12.2023 to 23H2.

I have now tried an inplace update to 24H2 and other manual updates. That didn't help. All the usual fixes suggested by Microsoft have not helped. All the fixes I found on your site were similar but not identical.

Operating system is Windows 11 Home 64bit 24H2 Build 26100.1742.

The log files are attached.

Thank you very much for your support.

Sincerely
Saitenschwinger

 

[Windows Update Bot]

Hi @Saitenschwinger,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[Saitenschwinger]

I read the posting instructions before I posted here. Please let me know if anything is missing.

 

[Saitenschwinger]

No third party security software, only Defender

 

[Saitenschwinger]

Hello dear sysnative team,

I read that you are very busy and that it will take some time for you to respond. I fully understand that. I just saw that entries that are later than mine are already being processed, so I just wanted to make sure that you haven't forgotten about me

Many thanks and best regards

 

[Maxstar]

Hi and welcome to Sysnative,

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

• Note: Your antivirus program may report FRST incorrectly as an infection. If so, disable the real-time protection when downloading and running FRST.
• Right-click to run the tool as administrator. When the tool opens click Yes to disclaimer.
• Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
• Press the Scan button.
• Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
• Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[Saitenschwinger]

Hi Maxstar,

thank You. Here are the two logfiles.

 

[Maxstar]

Windows Update reports: “Error - We could not connect to the update service.” I haven't started this system for over a year, so I don't know when the error occurred.
Last update was 26.12.2023 to 23H2.

Hi,

The FRST log shows you are running Windows 11 Home Version 24H2 26100.3775 which is the latest build (update) from April. So this looks good, so please search again for updates and post the result.

 

[Saitenschwinger]

I have now tried an inplace update to 24H2 and other manual updates. That didn't help. All the usual fixes suggested by Microsoft have not helped. All the fixes I found on your site were similar but not identical.

Operating system is Windows 11 Home 64bit 24H2 Build 26100.1742

Hi Maxstar,

thank you very much. I am still getting this error message:



As you can see here in my thread #1, I have already tried the inplace upgrade. Why this is now already build 3775, I can't see here. Also in the update history it still says Windows 11, 23H2 from 21.11.2023 as the last feature update.

Interesting: I also tried to install the Defender updates manually. That didn't work. With Defender, however, I get the feedback that the latest definition updates are installed daily. However, I cannot see this in the update history.

 

[Maxstar]

Hi,

Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

• Download the attachment fixlist.txt and save it to your desktop.
• Right-click on FRST64.exe and select "Run as administrator".
• Press the Fix button.
• If for some reason the tool needs a restart, please make sure you let the system restart normally.
• When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
• Post the logfile Fixlog.txt as attachment in your next reply.

 

[Saitenschwinger]

Hi Maxstar,

here ist the Fixlog.txt.

(I tried checking for updates again. No changes.)

 

[Maxstar]

Hi,

Export the Windows Update log

• Right-click on the Start button and click Windows PowerShell (Admin).
• Copy and paste the following command into it, press enter afterwards

Get-WindowsUpdateLog

• Wait for the message "WindowsUpdate.log written to C:\Users\<username>\Desktop\WindowsUpdate.log".
• Attach the logfile WindowsUpdate.log to your next reply.

 

[Saitenschwinger]

Hi Maxstar,

here it is.

 

[Maxstar]

Hi,

Please copy and paste the following link into the browser, this should be download a file named environment.cab if it fails the browser will show an error like: "NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED"

HTTPS://slscr.update.microsoft.com/SLS/{9482F4B4-E343-43B6-B170-9A65BC822C77}/x64/10.0.26100.3775/0?CH=336&L=de-DE;en-US&P=&PT=0x65&WUA=1406.2503.20012.0&MK=Gigabyte+Technology+Co.%2C+Ltd.&MD=X299+UD4+Pro

 

[Saitenschwinger]

Yes, that's exactly what happens. Should I skip the error message and download it? What should I do with it afterwards?

 

[Maxstar]

Okay, please do the following first.

Export registry key as hive file.

• Open the Start menu of Windows and type CMD.
• When you see Command Prompt on the list, select the option Run as administrator.
• Copy and paste the following command into the command prompt and press enter.

reg save "HKLM\SOFTWARE\Microsoft\SystemCertificates" "%userprofile%\Desktop\SysCert.hiv"

• Once done, a file will appear on your desktop, called SysCert.hiv.
• ZIP this file and attach it to your next reply.

 

[Saitenschwinger]

Here you go

 

[Maxstar]

Step 1. Download

Acelogix RegBak (Portable) to create a backup of the registry.

• Extract RegBak.zip and right-click regbak64.exe and select "Run as administrator".
• Click on the button New backup and choose the location where you want to save the backup.
• Optional: enter a description for this backup.
• Now click on the option "Click here to view details".
• Ensure the option Select hives not loaded by Windows is checked, to be sure the following items are included in the backup.
  
  
• Click Ok to save these settings and press Start to create the backup.
• When completed you will see the message: Finished succesfully.

Step 2. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

• Save any work you have open, and close all programs.
• Download the attachment SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.

• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Post the logfile (SFCFix.txt) as attachment in your next reply.

Afterwards reboot the system and attempt to update again.

 

[Saitenschwinger]

Hi Maxstar,

I see some good progress. Thank you very much!

1. there is no more error message in Windows Update
2. only 2 definition updates have been installed, nothing else:


3. for the function updates, it still only shows that in the update history, not the inplaced 24H2:


4. I am now being offered a lot of optional driver updates. My processor is an Intel(R) Core(TM) i7-9800X CPU 3.80GHz. Does it make sense to install them?:

 

[Maxstar]

Hi,

Great, for some reason the certificate entry's into the registry became corrupted?

1. OK.
2. This system was already on build 24H2 26100.3775 and now the Defender updates installed as well which where failing in post #9.
3. The Windows update history (screen from Settings) is not always accurate in providing or recen data, so you can ignore it for now.
4. Please avoid installing "Optional driver updates", drivers should only be updated in case of problems or when necessary! And download them always from the hardware manufacturer's website, also because the optional drivers may already be outdated.

I can only suggest to avoid to all the peview updates and all other optional updates when the system is working fine...