Microsoft troubleshooter windows 7

Исправляем ошибки установки обновлений Windows 7

Microsoft troubleshooter windows 7

Windows 7 по-прежнему остается популярной операционной системой в корпоративной среде, несмотря на то, что уже вышли две новые версии клиентских ОС. Расширенная поддержка «семёрки» закончится лишь 14 января 2020 г.

, а это значит, что ближайшие 4 года для нее будут выходить обновления, исправляющие обнаруженные уязвимости. Существует правило – если есть обновления, то есть и проблемы с их установкой.

Давайте разберем, какие основные проблемы возникают при обновлении Windows 7 через Windows Server Update Services (WSUS) и как их исправить с наименьшими затратами.

Ошибка #1. Failed to find updates with error code 80244010

Эту ошибку вы практически гарантированно будете наблюдать на любой системе, впервые обратившейся к серверу WSUS. В WindowsUpdate.log также встретится предупреждение:

WARNING: Exceeded max server round trips

Причина проблемы в том, что список обновлений стал слишком большим, и клиент не может принять его за один заход. Подробности — blogs.technet.microsoft.com/sus/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010
Какое решение предлагает Microsoft? Если после ошибки запустить повторный поиск обновлений, то процесс загрузки метаданных продолжится с момента возникновения ошибки. Терпение господа, терпение. Три, пять попыток wuauclt /detectnow – и все образуется. Не забудьте при повторном поиске дождаться окончания предыдущего цикла поиска, иначе магия не сработает!

Ошибка #2. Не устанавливаются обновления Windows с ошибкой 0x80070308

Встречается эпизодически, и в одном случае из 100 у нее есть единственное и очень специфическое решение — удалить ключ

HKLM\Components\PendingRequired=1

Перезагрузиться. Здесь важно не переусердствовать, не следует удалять никакие другие ключи в этом разделе, даже если они вам очень не нравятся, потому что после этого обновления прекратят ставиться навсегда.

Ошибка #3. Все другие ошибки

Практически 100% других ошибок может решить System Update Readiness Tool (SURT) из статьи support.microsoft.com/en-us/kb/947821
Скачиваете пакет для вашей системы, устанавливаете, читаете лог %windir%\Logs\CBS\CheckSUR.

log и если он заканчивается примерно так:
Summary: Seconds executed: 1164 Found 16 errors Fixed 4 errors то вы наш клиент. Проблема заключается в том, что во время установки обновлений в системе могут появиться битые файлы.

Что является причиной — неисправная сеть, диск, оперативная память, сам Windows Update – выяснить не получится, а исправить ошибки для установки последующих обновлений придется. Как правило, повреждаются *.cat, *.mum, *.manifest файлы. У кого-то повреждаются *.dll, но я на практике не сталкивался.

И вроде бы средство SURT должно само исправить ошибки, поскольку внутри него есть огромный каталог эталонных файлов. Только в последний раз SURT обновлялся в октябре 2014 года, а исправлений на операционную систему с тех пор вышло бесчисленное множество, и многих файлов в каталоге не хватает.

Ниже я опишу последовательность действий, необходимых для исправления ошибок установки обновлений на Windows 7 x64 с использованием SURT. Для редакции x86 просто потребуется другой пакет SURT из KB947821. Последовательность действий будет следующая.

1. Запустить первый проход Windows6.1-KB947821-v34-x64.msu

Пользователя от работы отвлекать не потребуется, все сделаем удаленно. Создаем следующий командный файл и запускаем его:set machine=BUHWKS02xcopy Windows6.1-KB947821-v34-x64.

msu \\%machine%\admin$\temppsexec -s \\%machine% wusa “c:\windows\temp\Windows6.1-KB947821-v34-x64.msu” /quiet /norestartpause где BUHWKS02 – целевая машина.

Когда скрипт отработает и встанет на паузу, проверяем %windir%\Logs\CBS\CheckSUR.log

Если ошибок не найдено – дело не в битых обновлениях. Если он заканчиваетсяSummary: Seconds executed: 1164

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:

winsxs\manifests\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.19091_none_c19fa2719495aca9.manifest winsxs\manifests\amd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.23290_none_5e936c9c5ce2e8e6.manifest winsxs\manifests\wow64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.23290_none_c22840d8adb43043.manifest winsxs\manifests\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.19091_none_b74af81f6034eaae.manifest winsxs\manifests\amd64_microsoft-windows-capi2-weakcrypto_31bf3856ad364e35_6.1.7601.19091_none_5e0ace3543c4654c.manifest winsxs\manifests\amd64_microsoft-windows-gdi32_31bf3856ad364e35_6.1.7601.23290_none_b7d3968679536e48.manifest servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum servicing\packages\Package_2_for_KB3123479~31bf3856ad364e35~amd64~~6.1.1.0.mum

servicing\packages\Package_for_KB3123479_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum

то будем исправлять.

2. Копируем эталонные файлы на целевую машину

Microsoft предлагает нам длинную, путанную процедуру с извлечением хороших файлов из обновлений и размещением их в определенные каталоги средства SURT. При этом пути в статьях неверные. Где-то и вовсе рекомендуют подкладывать оригинальные msu файлы.

Самый простой и правильный вариант следующий — скопировать эталонные файлы с рабочей системы: *.mum and *.cat из C:\Windows\servicing\Packages складываются в %windir%\Temp\CheckSUR\servicing\packages *.

manifest из C:\Windows\winsxs\Manifests складываются в %windir%\Temp\CheckSUR\winsxs\manifests\ Проблема в том, что битых файлов обычно десятки, и их очень сложно выбрать и скопировать.

Тогда на помощь приходит следующий скрипт PowerShell (эталонной считается машина, с которой вы запускаете скрипт) cls$flag = $false$destPC = “\\BUHWKS02″$log=get-content $($destPC + “\admin$\Logs\CBS\CheckSUR.

log”)$MUMCATSource = “C:\Windows\servicing\Packages\”$MUMCATDest = $destpc + “\admin$\Temp\CheckSUR\servicing\Packages\”$MANIFESTSource = “C:\Windows\winsxs\Manifests\”$MANIFESTDest = $destpc + “\admin$\Temp\CheckSUR\winsxs\Manifests\”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} } Как видите, скрипт прост и может быть легко заточен напильником под вашу инфраструктуру.

3. Запускаем второй проход Windows6.1-KB947821-v34-x64.msu

После копирования файлов мы повторно запускаем SURT, используя командный файл из первого шага. При повторном запуске средство сможет подхватить скопированные нами эталонные файлы из %windir%\Temp\CheckSUR и заменить ими испорченные. Если мы сделали все правильно, то %windir%\Logs\CBS\CheckSUR.

log примет следующий вид:================================= 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

Теперь можно продолжить установку обновлений на целевую машину, например, следующими командными файлами:

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

Ошибка #4. Если SURT отработал нормально, а обновления все равно не ставятся

Попробуйте прибегнуть к старому приему – сбросить службу Windows Update в исходное состояние. Для этого необходимо удалить каталог %windir%\SoftwareDistribution. Создаем файл WU-cleanupCMD.cmd:

net stop wuauserv rmdir /s /q %windir%\SoftwareDistribution net start wuauserv wuauclt /detectnow

Запускаем:

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

После этого возникнет Ошибка #1, но как бороться с ней мы уже знаем.

Ошибка #5

Клиент исчезает из консоли WSUS. Любопытная ошибка, связанная с неправильным клонированием машин и задвоением (затроением и т.д.) идентификаторов клиентов.

Решается так: net stop wuauservREG DELETE “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientId /fREG DELETE “HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate” /v SusClientIdValidation /fnet start wuauservwuauclt /resetauthorization /detectnow /reportnow

Ошибка #6

GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200 SyncUpdates failure, error = 0x80072EE2, soap client error = 5, soap error code = 0, HTTP status code = 200 Windows Update Client failed to detect with error 0x80072ee2

Ошибка связана с нехваткой ресурсов в AppPool WSUS. Решение — снять лимит на потребляемую память. Как это сделать — статья.

Коротко: Открываем IIS, Application Pools, WsusPool, Advanced Settings. Параметр Private Memory Limit устанавливаем в 0.

Продолжение темы настройки WSUS — в моей следующей статье: https://habrahabr.ru/post/329440/

PS: Многие ошибки решены в новом клиенте WSUS:

1. KB3125574 «Windows 7 post SP1 Convenience Rollup Update». Внимательно ознакомьтесь с разделом Known issues!

Предварительно необходимо установить KB3020369 «April 2015 servicing stack update for Windows 7 and Windows Server 2008 R2».

Удачного администрирования!

  • Windows Update
  • Windows 7
  • wsus

Хабы:

  • Системное администрирование
  • Серверное администрирование

Источник: https://habr.com/ru/post/278439/

Windows 7 troubleshooting tools and tips

Microsoft troubleshooter windows 7

Figuring out the cause of a problem is often the hardest part of troubleshooting, but by itself it doesn't do you much good. When you know the source, you need to parlay that information into a fix for the problem. I discussed a few solutions in the previous section, but here are a few other general fixes you need to keep in mind:

About the book:
This chapter excerpt on Troubleshooting and Recovering from Problems (download PDF) is taken from the book Microsoft Windows 7 Unleashed. This book covers key topics for solutions providers, including customizing Windows 7; monitoring, tuning and optimizing Windows performance; securing Windows 7; and using its power tools. Author Paul McFedries introduces new styles and techniques to troubleshoot Windows 7 and automate administration.
  • Close all programs — You can often fix flaky behavior by shutting down all your open programs and starting again. This is a particularly useful fix for problems caused by low memory or low system resources.
  • Log off Windows 7 — Logging off clears the RAM and so gives you a slightly cleaner slate than merely closing all your programs.
  • Reboot the computer — If there are problems with some system files and devices, logging off won't help because these objects remain loaded. By rebooting the system, you reload the entire system, which is often enough to solve many computer problems.
  • Turn off the computer and restart — You can often solve a hardware problem by first shutting your machine off. Wait for 30 seconds to give all devices time to spin down, and then restart.
  • Check connections, power switches, and so on — Some of the most common (and some of the most embarrassing) causes of hardware problems are the simple physical things. So, make sure that a device is turned on, check that cable connections are secure, and ensure that insertable devices are properly inserted.

More Troubleshooting Tools

Windows 7 comes with diagnostic tools — together, they're called the Windows Diagnostic Infrastructure (WDI) — that not only do a better job of finding the source of many common disk, memory, and network problems, but can detect impending failures and alert you to take corrective or mitigating action (such as backing up your files). The next few sections describe these tools.

Running the Windows 7 Troubleshooters

Windows Vista introduced the idea of the troubleshooter, a Help system component that offered a series of solutions that led you deeper into a problem in an attempt to fix it. In Windows 7, the troubleshooters have been beefed up and given their own home within the Control Panel interface.

To see the Windows 7 troubleshooters, select Start, type trouble, and then choose Troubleshooting in the search results. The Troubleshooting window (see Figure 21.

5) is divided into several categories (Programs, Hardware and Sound, and so on), each of which offers a few links to general troubleshooting tasks.

Note, too, the Get the Most Up-to-Date Troubleshooters check box at the bottom of the window.

If you leave that option activated, and then click a category, Windows 7 queries the Windows Online Troubleshooting service for the latest troubleshooting packs, and then displays the complete list for that category. For example, Figure 21.6 shows the troubleshooters that were available for the Programs category as I wrote this.

TIP 
If you want to see all the available troubleshooters, click the View All link in the Troubleshooting window.

FIGURE 21.5 Windows 7's new Troubleshooting window offers links to various troubleshooting
categories and tasks.

FIGURE 21.6 Click a category to see its available troubleshooters.

Understanding Disk Diagnostics

A hard disk can suddenly bite the dust thanks to a lightning strike, an accidental drop from a decent height, or an electronic component shorting out. However, most of the time hard disks die a slow death. Along the way, hard disks almost always show some signs of decay, such as the following:

  • Spin-up time gradually slows.
  • Drive temperature increases.
  • The seek error rate increases.
  • The read error rate increases.
  • The write error rate increases.
  • The number of reallocated sectors increases.
  • The number of bad sectors increases.
  • The cyclic redundancy check (CRC) produces an increasing number of errors.

Other factors that might indicate a potential failure are the number of times that the hard drive has been powered up, the number of hours in use, and the number of times the drive has started and stopped spinning.

Since about 1996, almost all hard disk manufacturers have built in to their drives a system called Self-Monitoring, Analysis, and Reporting Technology, or SMART.

This system monitors the parameters just listed (and usually quite a few more highly technical hard disk attributes) and uses a sophisticated algorithm to combine these attributes into a value that represents the overall health of the disk.

When that value goes beyond some predetermined threshold, SMART issues an alert that hard disk failure might be imminent.

Although SMART has been around for a while and is now standard, taking advantage of SMART diagnostics has, until now, required third-party programs.

However, Windows 7 comes with a Diagnostic Policy Service (DPS) that includes a Disk Diagnostics component that can monitor SMART. If the SMART system reports an error, Windows 7 displays a message that your hard disk is at risk.

It also guides you through a backup session to ensure that you don't lose any data before you can have the disk replaced.

Understanding Resource Exhaustion Detection

Your system can become unstable if it runs low on virtual memory, and there's a pretty good chance it will hang if it runs virtual memory. Older versions of Windows displayed one warning when they detected low virtual memory and another warning when the system ran virtual memory.

However, in both cases, users were simply told to shut down some or all of their running programs. That often solved the problem, but shutting everything down is usually overkill because it's often the case that just one running program or process is causing the virtual memory shortage.

Windows 7 takes this more subtle point of view into account with its Windows Resource Exhaustion Detection and Resolution tool (RADAR), which is part of the Diagnostic Policy Service. This tool also monitors virtual memory and issues a warning when resources run low.

However, RADAR also identifies which programs or processes are using the most virtual memory, and it includes a list of these resource hogs as part of the warning.

This enables you to shut down just one or more of these offending processes to get your system in a more stable state.

Microsoft is also providing developers with programmatic access to the RADAR tool, thus
enabling vendors to build resource exhaustion detection into their applications. When such a program detects that it is using excessive resources, or if it detects that the system as a whole is low on virtual memory, the program can free resources to improve overall system stability.

NOTE 
The Resource Exhaustion Detection and Recovery tool divides the current amount of committed virtual memory by the commit limit, the maximum size of the virtual memory paging file. If this percentage approaches 100, RADAR issues its warning.

If you want to track this yourself, run the Performance Monitor (see Chapter 6), and add the % Committed Bytes in Use counter in the Memory object.

If you want to see the exact commit numbers, add the Committed Bytes and Commit Limit counters (also in the Memory object).

  • See “Using the Performance Monitor,” p. 119.

Running the Memory Diagnostics Tool

Few computer problems are as maddening as those related to physical memory defects because they tend to be intermittent and they tend to cause problems in secondary systems, forcing you to waste time on wild goose chases all over your system.

Therefore, it is welcome news that Windows 7 ships with a Windows Memory Diagnostics tool that works with Microsoft Online Crash Analysis to determine whether defective physical memory is the cause of program crashes.

If so, Windows Memory Diagnostics lets you know about the problem and schedules a memory test for the next time you start your computer.

If it detects actual problems, the system also marks the affected memory area as unusable to avoid future crashes.

Windows 7 also comes with a Memory Leak Diagnosis tool that's part of the Diagnostic Policy Service. If a program is leaking memory (using up increasing amounts of memory over time), this tool will diagnose the problem and take steps to fix it.

To run the Memory Diagnostics tool yourself, follow these steps:

1. Select Start, type memory, and then click Windows Memory Diagnostic in the search results. The Windows Memory Diagnostics Tool window appears, as shown in Figure 21.7.
2. Click one of the following options:

  • Restart Now and Check for Problems — Click this option to force an immediate restart and schedule a memory test during startup. Be sure to save your work before clicking this option.
  • Check for Problems the Next Time I Start My Computer — Click this option to schedule a memory test to run the next time you boot.

After the test runs (it takes 10 or 15 minutes, depending on how much RAM is in your system), Windows 7 restarts and you see (for a short time) the Windows Memory Diagnostic Tool icon in the taskbar's notification area. This icon displays the results of the memory text.

FIGURE 21.7 Use the Windows Memory Diagnostic tool to check for memory problems.

TIP 
If you're having trouble starting Windows 7 and you suspect memory errors might be the culprit, boot your machine to the Windows Boot Manager menu (refer to Chapter 4).

When the menu appears, press Tab to select the Windows Memory Diagnostic item, and then press Enter. If you can't get to the Windows Boot Manager, you can also run the Memory Diagnostic tool using Windows 7's System Recovery Options.

See “Recovering Using the System Recovery Options” in Chapter 23, “Troubleshooting Startup.”

Checking for Solutions to Problems

Microsoft constantly collects information about Windows 7 from users. When a problem occurs, Windows 7 usually asks whether you want to send information about the problem to Microsoft and, if you do, it stores these tidbits in a massive database. Engineers then tackle the “issues” (as they euphemistically call them) and hopefully come up with solutions.

About the
Paul McFedries is the president of Logophilia Limited, a technical writing company, and has been writing computer books since 1991. McFedries is the author or coauthor of more than 60 books that have sold more than 3 million copies worldwide. He is also the proprietor of Wordspy.com, a website described as “the word lover's guide to new words,” which tracks new words that become part of the English language.

One of Windows 7's most promising features is called Problem Reporting (it was called Problem Reports and Solutions in Vista), and it's designed to make solutions available to anyone who goes looking for them.

Windows 7 keeps a list of problems your computer is having, so you can tell it to go online and see whether a solution is available.

If there's a solution waiting, Windows 7 will download it, install it, and fix your system.

Here are the steps to follow to check for solutions to problems:

1. Select Start, type action, and then click Action Center in the results. (You can also click the Action Center icon in the taskbar's notification area, and then click Open Action Center.) The Action Center window appears. 2. Click Maintenance to view the maintenance-related tools and messages. 3. Click the Check for Solutions link. Windows 7 begins checking for solutions.

4. If you see a dialog box asking whether you want to send more information about your problems, you can click View Problem Details to see information about the problems, as shown in Figure 21.8. When you're ready to move on, click Send Information.

Источник: https://searchitchannel.techtarget.com/feature/Windows-7-troubleshooting-tools-and-tips

[FIX] Windows Updates Troubleshooting In Windows 7, 8

Microsoft troubleshooter windows 7

Everyone wants to keep his system updated, the way is the have automatic installation of Windows Updates. But there may be certain scenarios when you can’t install all updates fully. The reason behind this could be wast, may be you need to repair your computer in order to fix the issues concerning unsuccessful installation of updates.

Today in this article, we’ll see the some troubleshooting steps which you can follow to fix up the issues with Windows Updates.

Many times you face error of similar kind as the one shown in image above, due to this there is installation of Windows Updates is not complete so far.

The thing noticeable here is that “Try again” button doesn’t seems working and won’t solve the issue. In such scenarios, you can try this solutions:

Method 1: Windows Updates Troubleshooting Using Troubleshooter

To fix it out initially, you can try the Windows Update Automated Troubleshooter, a specially designed tool to found out and fixes concerning Windows Update. You can download it using following link:

Download Windows Update Automated Troubleshooter

If the troubleshooter was not able to fix your issue, then you can try the following manual fix and we’re pretty sure it will work. Make sure you follow the exact procedure. We recommend you to create a System Restore point before making any changes to system. Here is the fix:

Method 2: Windows Updates Troubleshooting By Resetting Components

Following steps will illustrate you how to reset Windows Update components in Windows:

1. Open the Command Prompt with administrative privileges.

2. Now stop the Background Intelligent Transfer Service (BITS) and Windows Update services using following commands:

net stop bitsnet stop wuauserv

3. Moving on, type following command:

Del “%ALLUSERSPROFILE%\Application Data\Microsoftetwork\Downloader\qmgr*.dat”

After applying above stated command, check whether the issue still persists or not. If it is fixed, then skip the step 4 and directly go to the step 5.

4. This is the aggressive step in order to fix the issue. You need to rename following folders using Command Prompt:

%systemroot%\SoftwareDistribution\DataStore%systemroot%\SoftwareDistribution\Download%systemroot%\system32\catroot2

To rename the folders, use following commands respectively:

Ren %systemroot%\SoftwareDistributionData\Store *.bakRen %systemroot%\SoftwareDistribution\Download *.bakRen %systemroot%\system32\catroot2 *.bak

5. Now we, reset the BITS service and the Windows Update service to the default security descriptor. To do this enter following commands (copy the commands and right click paste it Command Prompt) :

sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

Now type the following command:

cd /d %windir%\system32

6. Next, re-register the BITS files and the Windows Update files. This requires the following bunch of commands to be executed:

  • regsvr32.exe browseui.dll
  • regsvr32.exe vbscript.dll
  • regsvr32.exe actxprxy.dll
  • regsvr32.exe wintrust.dll
  • regsvr32.exe cryptdlg.dll
  • regsvr32.exe oleaut32.dll
  • regsvr32.exe wuaueng1.dll
  • regsvr32.exe qmgrprxy.dll

7. After running and registering all components using above commands, run following command:

netsh winsock reset

In case you’re running Windows XP, then additionally execute following command to set proxy settings:

proxycfg.exe -d

8. We’re almost done now! Just restart the BITS & Windows Update services again using following commands:

net start bitsnet start wuauserv

In this way your issue should be fixed now. Try reinstalling the updates which were not completely installed previously. It should work fine now. If you’re still facing the issues, then please let us know via comment box!

Источник: https://www.kapilarya.com/windows-updates-troubleshooting

Поделиться:
Нет комментариев

    Добавить комментарий

    Ваш e-mail не будет опубликован. Все поля обязательны для заполнения.