Chi did not go far enough to revise the version of the update. Information portal for security

Today we will look at the devil's pardon when updating Windows 10 - 0x80070020. If we try to guess the history of the Windows OS, then it is clear that, in practice, they blamed the problems with installing the update.

In short, all installation problems can be divided into three groups: no upgrades; The update has loaded, but it cannot be installed; the update was taken and installed, but it was thrown out by the system and it turned to front version. Pardon 0x80070020 when updating Windows 10 is just a bag in one of three groups. It was marked out for two more years that in 2015 it will turn out, right after the exit of the present Windows systems 10.

Behind the claims of Microsoft, the stench is to blame for correcting pardon, Ale, how can you bachiti, the problem is new splinter, moreover, absolutely recently. Unfortunately, the Windows 10 Creators Update turned pardon 0x80070020 to life. The biggest problem is those who are koristuvachi so i could not designate a trigger for її appearance.

Possibly, the problems appeared due to a third-party anti-virus, service to the Center Windows update(Especially with BITS) or with viruses. At once we can see possible ways virishennya tsієї pardon. Unfortunately, it is impossible to propagate anything new in this situation, and the problem lies behind the help of old, but distorted methods.

Ways to clear pardon 0x80070020 when updating Windows 10

Method #1 Enable third-party antiviruses

How already it was said more, possible reason the appearance of an already scheduled pardon when updating Windows 10 could serve as a third-party antivirus software security. All right in the fact that the antivirus can instantly download downloaded update files for threatening your system and successfully block them. After that, the problem was discussed.

What do you have in your system? third-party antivirus, Then try turning on yoga or navit vidaliti, and then try again to update Windows 10. Since everything went smoothly and the system was updated, then you knew the culprit was the antivirus. We recommend that you disable system antivirus - zahisnik Windows. Although wine and є the installed utility, but victorious its functions on the front.

Method #2 Skip BITS service

For Windows experts, the pardon 0x80070020 may sound like a reminder to the background transfer service, or just BITS, as it is just responsible for the delivery and preparation of updates for Windows. As if the process of giving the service a buzz or an error due to recent changes in the system, you can try to drop BITS. For whom you will need to work on your feet:

  • Press on the keyboard Win+R for Wiklik program "Vikonati".
  • Write in an empty row services.msc and press Enter.
  • Find the Background Intelligent Transfer Service (BITS) service in the lists.
  • Click on the service with the left mouse button.
  • Click on the "Startup type" drop-down menu and select the "Automatic" option.
  • It is also your fault to reconsider the fact that the given service is not in a deactivated state. If so, then click on the "Start" button in the next day.
  • Confirm changes and close at the end with Windows services.

Again, you have restarted the BITS service. Try re-installing the update for Windows 10. If everything is visible, then on the right it was crazy in the turned off service.

Method #3 Skip the components of the Windows Update service

For more cost-effective Windows 10, the best way to downgrade the BITS service. However, even though it could not help your situation with a pardon of 0x80070020, then you should try to remove the components of the Windows Update service. It’s necessary to tell you which way you can use to get a trivalent term from you, but just sing along to the problem.

  • click right button click on Start and select "Command row (administrator)".
  • As soon as a row appears in front of you, start typing in it according to the steps of the command, not forgetting when you press Enter after the skin of them:

  • Otzhe, why did we kill you, if you entered these commands:
    • The robot of BITS services, Windows Update services, Windows installer and cryptography.
    • We saw the qmgr * .dat file from the system.
    • We re-registered the components of the BITS services and the Windows Update service.
    • Restarted Winsock.
    • We launched the BITS services, Windows Update, Windows Installer and Cryptography services.
  • After entering all the given commands, restart your computer.

Method #4 Run Windows Update Troubleshooter

If everything described above did not help you, then you can help and encourage you to try the services of system diagnostics of problems with the Windows Update service. The chance of correcting the pardon 0x80070020 is small, but why not try it.

  • Right-click the mouse on Start and go to the "Control Panel".
  • Go to the item "Search for troubleshooting" (through other icons).
  • Click on the message "Search for troubleshooting for the help of the Windows Update service."
  • Before you z'appear at the end of "Diagnosis and prevention of problems on the computer." Press "Dodatkovo" and check the box next to the option "Automatically stop the correction", which will help you.
  • Press the "Dal" button.

From i all. If it is not possible for system diagnostics to detect problems with the Windows Update service, then it is necessary to fix them in automatic mode, so you have checked the box.

Method No. 5 Rechecking the PC for the presence of viruses

If nothing has helped you up to this point, then, perhaps, the reason lies in some shkіdniki, like blocking the installation of the update, or navigating the downloaded files to install the update. For the help of your Anti-Virus system, turn it over for the presence of viruses. As soon as it appears, then remove the infected elements and again try to update Windows 10 to check the visibility of the pardon 0x80070020.


Did you know a friend's pardon? View text and press Ctrl + Enter

Since the release of the first update of windows 10, microsoft has already intensively begun to improve operating system. We are releasing two patches to update. One patch for security, the other for system maintenance (fixing bugs, lags, improving the interface, design, etc.). Prote, a rich coristuvach, had to solve a lot of problems when installing windows 10 updates. A few hours later, after a scarg coristuvachiv, Microsoft released a tool that could help you get a lot of pardons when installing updates in Windows 10, 8. We can do more methods below with one tool Mike.

How to fix the windows update pardon

Rozberemo for the cob vbudovaniya variant for the correction of pardons when renewed. For whom you wish Settings > Security Update > Troubleshooting > Windows Update and press Run Troubleshooter.

Fix Pardons for Windows Update

If there is no such decision point, there are more descriptions, then we will analyze help Windows update. Deyakі koristuvachі can turn on the update, and then through the new year they want to change. The feature is described more recently introduced in the Creators Update and this item will not be available, including Windows 8. Microsoft has released a tool for using pardons when updating Windows 10, Windows 8.1, Windows 7.

  • go to microsoft website and download the diagnostic program.
  • Select system version and download Troubleshooting in Windows Update Center.
  • For others Windows versions 8.1, Windows 7, check the items on the site, mark the items and then solve a lot of problems related to firmware updates.



Fix pardon when installing Windows 10

We will correct for the help of the command line i parameter DSIM. Vіdkryte command line in the name of the administrator.

In order to enter or copy in order the next code:

  • 1.DISM.exe /Online/Cleanup-image/Restorehealth
  • 2. DISM.exe /Online/Cleanup-Image/RestoreHealth/Source: C:\RepairSource\Windows/LimitAccess
  • 3.sfc /scannow

Note: Dock after the skin command, 100% result and do not use the Internet and computer in the media.



Fixing pardons for updating Windows Zupinka and starting services

For one of the most common reasons that Windows may not be able to update or install an update, services may be blocked by other software processes. You can try to reset the computer and change the process. If it didn’t help, then we’ll figure out how to help the team bits, zupinimo and restart the services connected with the windows update center. Vіdkryte command row in the name of the administrator and enter the next code in order:

Note:I recommend putting the rest version Windows Update Agent Center. Yogo update on the official microsoft sites.

Zupinka services:

  • net stop bits
  • net stop wuauserver
  • net stop appidsvc
  • net stop cryptsvc

Starting services:

  • net start bits
  • net start wuauserver
  • net start appidsvc
  • net start cryptsvc



How to clean up the SoftwareDistribution folder to use Windows 10 updates

The problem of others is in papacy Software Distribution, de save the windows update files themselves. If the system is being updated, then the stench is saved by itself in your papacy. After the installation of an update, WUAgent see all the folders are old, but other times the processes get mixed up and the folder is left behind different files. Mi purify hand folder Software Distribution, so that there were no failures and pardons when installing windows updates. Open the command line in the name of the administrator and enter the following commands:

Windows 7, as before, is the most popular operating system in the corporate environment, regardless of those that have already released two new versions of client operating systems. Expanded "Simka" line will end less than 14 September 2020, but it means that the next 4 dates for her are to be updated, to correct the inconsistencies.

The first rule is that if it is updated, then there are problems with its installation. Let's take a look at what the main problems are when updating Windows 7 through Windows Server Update Services (WSUS) and how to fix it with the least amount of effort.

Pardon #1. Failed to find updates with error code 80244010
Qiu pardon you are practically guaranteed to be posterіgati on any system, before going back to the WSUS server. WindowsUpdate.log also has a warning:
WARNING: Exceeded max server round trips

The reason for the problem is that the list of updates has become too large, and the client cannot accept it in one go. details -
What is the solution to promote Microsoft? If you start a second update search after the pardon, then the process of capturing metadata will continue from the moment the pardon was made. Patience panova, patience. Three, five samples wuauclt / detectnow - and everything is in control. Do not forget to repeat the search to finish the previous cycle of the search, otherwise the magic will not work!

Pardon #2. Chi do not install Windows updates with a pardon 0x80070308
Zustrichaetsya sporadically, and in one step out of 100 she has one and even more specific solution - find the key
HKLMComponentsPendingRequired = 1

Re-engage. Here it’s important not to overdo it, not to see any other keys in your division, to see if the stench doesn’t suit you anymore, to that after the new renewal it’s put back.

Pardon #3. All other pardons
Almost 100% of other pardons can be eliminated by the System Update Readiness Tool (SURT) s stat
Get the package for your system, install it, read the log% windir% LogsCBSCheckSUR.log and it will end up like this:

Summary:
Seconds executed: thousand one hundred and sixty chotiri
Found 16 errors
Fixed 4 errors


then you are our client.

The problem lies in the fact that during the installation of an update, some files may appear in the system. What is the reason - the mesh, the disk is wrong, operational memory, Windows Update itself - z'yasuvati not viide, but correct pardons for installing upcoming updates.

As a rule, * .cat, * .mum, * .manifest files are supported. Some people get * .dll, but I didn’t stick in practice. І nachebto zasіb SURT can correct pardons, shards in the middle of the new є majestic catalog of reference files. For the last time, SURT was upgraded in the year 2014, but the transfer to the operating system was still silent, and there were no more files in the catalog.


Below I will describe the sequence of actions necessary for the correction of the pardons of installing updates on Windows 7 x64 with SURT guidelines. For the x86 edition, you just need the other SURT package with KB947821.

The aftermath will come.

1. Run the first pass Windows6.1-KB947821-v34-x64.msu
There will be no need for a coristuvacha in the form of a robot, everything is removed. Create an upcoming batch file and run yoga:
set machine=BUHWKS02 xcopy Windows6.1-KB947821-v34-x64.msu %machine%admin $temp psexec -s %machine%wusa "c:windowstempWindows6.1-KB947821-v34-x64.msu" /quiet/norestart pause
de BUHWKS02 - target machine.
If the script is executed and paused, it will be checked% windir% LogsCBSCheckSUR.log
No pardons have been found - on the right, not in beaten updates.
How wine will end

Summary:
Seconds executed: thousand one hundred and sixty chotiri
Found 16 errors
Fixed 4 errors
CSI Manifest All Zeros Total count: 6
CSI Catalog Corrupt Total count: 3
Fixed: CSI Catalog Corrupt. Total count: 3
CBS MUM Corrupt Total count: 3
CBS Catalog Corrupt Total count: 3
CSI Catalog Thumbprint Invalid Total count: 1
Fixed: CSI Catalog Thumbprint Invalid. Total count: 1
Unavailable repair files:
winsxsmanifestswow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.19091_none_c19fa2719495aca9.manifest
winsxsmanifestsamd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.23290_none_5e936c9c5ce2e8e6.manifest
winsxsmanifestswow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.23290_none_c22840d8adb43043.manifest
winsxsmanifestsamd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.19091_none_b74af81f6034eaae.manifest
winsxsmanifestsamd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.19091_none_5e0ace3543c4654c.manifest
winsxsmanifestsamd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.23290_none_b7d3968679536e48.manifest
servicingpackagesPackage_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicingpackagesPackage_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum


then we'll fix it.
2. Copy the reference files to the target machine
Microsoft proponuє to us dovgu, swindle the procedure and place them in the same SURT catalogs. With any path in the articles is unvirnі. We hereby recommend that you submit original msu files.

The simplest and correct option is to copy the reference files from the working system:

* .Mum and * .cat from C:WindowsservicingPackages are folded into %windir%TempCheckSURservicingpackages
*.Manifest from C:WindowswinsxsManifests is folded into %windir%TempCheckSURwinsxsmanifests

The problem is that there are dozens of beaten files, and it’s even easier to select and copy them. Then the offensive script comes to the rescue (the reference machine is entered, so you run the script)

cls $flag=$false $destPC="BUHWKS02" $log=get-content $($destPC+"admin $LogsCBSCheckSUR.log") $MUMCATSource="C:WindowsservicingPackages" $MUMCATDest=$destpc+"admin$TempCheckSURservicingPackages" $MANIFESTSource = "C:WindowswinsxsManifests" $MANIFESTDest = $destpc + "admin $TempCheckSURwinsxsManifests" If ((Test-Path -Path $MUMCATDest -PathType Container) -eq $false) (New-Item -Path $MUMCATDest -ItemType directory) If ((Test-Path -Path $MANIFESTDest -PathType Container) -eq $false) (New-Item -Path $MANIFESTDest -ItemType directory) foreach ($line in $log) (if ($flag -eq $True) ( if ($line.trim().length -ne 0)($fileArray = $($line.Split("")) $file = $FileArray[$FileArray.Length-1] $extArray = $file.split( ".") $ext = $extArray[$extArray.length-1] if ($ext -eq "manifest")(Write-Warning $("Copying" + $($MANIFESTSource + $file) + "to" + $MANIFESTDest) Copy-Item $($MANIFESTSource + $file) $($MANIFESTDest + $file)) if (($ext -eq "mum") -or ($ext -eq "cat")) (Write-Warning $("Copying" + $($MUMCATSource + $file) + "to" + $MUMCATDest) Copy-Item $($MUMCATSource + $file) $($MUMCATDest + $file)))) if ($line -eq "Unavailable repair files: ") ($flag = $true))
Like a bachite, the script is simple and can be easily imprisoned with a file for your infrastructure.

3. Run another pass Windows6.1-KB947821-v34-x64.msu
After copying the files, we restart SURT, copying the batch file from the first step. When you restart the zasib, you can copy the reference files we have copied from% windir% TempCheckSUR and replace the zips with them.
If we have broken everything correctly, then % windir% LogsCBSCheckSUR.log will take the next look:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-03-03 09:15
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
Summary:
Seconds executed: +1435
No errors detected

Now you can continue installing the update on the target machine, for example, with the following command files:
set machine = BUHWKS02
psexec -i -s %machine% wuauclt /detectnow
pause

set machine = BUHWKS02
psexec -i -s %machine%wuauclt/updatenow
pause

Pardon #4. Yakshcho SURT vіdpratsyuvav normally, but the update is still not installed
Try to go to the old priyoma - throw off Windows service Update to the cob mill. For which you need to see the %windir% SoftwareDistribution directory.

We create the WU-cleanupCMD.cmd file:
net stop wuauserver
rmdir /s/q%windir%SoftwareDistribution
net start wuauserver
wuauclt / detectnow

run:
set machine = BUHWKS02
psexec -c -s %machine%WU-cleanupCMD.cmd
pause

After that winkne Pardon # 1, but we already know how to fight it.

Far from the administration!

© 2021 Mobile and computer gadgets