- Remove From My Forums
-
Вопрос
-
Доброго времени суток!
При попытке установить обновление на Windows Server 2008 R2 ничего не происходит… точнее сказать так беспрерывно бегает полосочка и написано что происходит поиск обновлений последний раз он искал почти сутки потом я его отключил.
На сервере установлен MS Exchange 2007, если эта информация чем-то поможет.
Подскажите с чем может быть связана данная проблема?
Ответы
-
В общем, проблема решилась страндартным «всё выключить и включить назад»: отключаем обновление exchange antispam сигнатур; останавливаем Windows Update; очищаем папку Software Distribution; запускаем
Windows Update, и убеждаемся, что он нормально теперь работает; включаем обновление antispam; убеждаемся, что тоже работает.-
Предложено в качестве ответа
5 декабря 2011 г. 9:46
-
Изменено
AlexVD
5 декабря 2011 г. 9:46 -
Помечено в качестве ответа
Vinokurov Yuriy
9 декабря 2011 г. 12:41
-
Предложено в качестве ответа
The Windows Update screen comes up and I click on Download Updates. I then get the bar scrolling across the screen and it says Downloading Updates but the counts never increase (0 KB total, 0% complete). I’ve tried several things found via Google to resolve this but so far nothing has worked.
Quoted from https://serverfault.com/questions/166318/windows-update-not-working-on-windows-2008-r2-standard-x64, except I don’t have an unlicensed SQL Server 2008 running. I have also tried several things from Google, including WUInstall and setting up a separate WSUS server and nothing has worked so far.
I’ve re-registered and sfc’d about every DLL I can think of that might be at all related (a little over 150), I’m not using any proxy servers.
I’ve downloaded the updates manually, but Windows stalls with a «Searching for updates» that never finishes searching.
Only errors I can find in my log are as follows:
2012-01-30 05:00:10:014 980 f40 AU WARNING: Failed to change download properties of call, error = 0x80070057 2012-01-30 07:43:06:441 980 fc0 AU WARNING: Returning due to error from GetDownloadProgressUx, error = 0x8024000C 2012-01-30 07:43:06:443 980 fc0 AU WARNING: GetInteractiveInstallProgress failed, error = 0x8024000C
Upon googling the first error, I came across some resolution steps:
Click on Start and type services.msc into the search box, then click on services as it appears above. Scroll down the list to Windows Update, right click on it and select stop.
Type this into the search box %windir%\SoftwareDistribution click on «Software Distribution» in the box above and delete the entire contents of the «Download» folder.
Go back and turn the Windows Update service back on.
Which, I’ve already tried, and no luck.
Later on, it says to download Microsoft’s MicrosoftFixit.wu.Run.exe
and try that, which I have and no luck. I’ve also tried Microsoft patch Windows6.1-KB947821-v14-x64.msu
which stalls with the ever so annoying «Searching for updates on this computer» forever.
I’ve tried downloading the third-party FixWU and nothing.
I’ve tried forcing a reinstall of the Windows Update agent using WindowsUpdateAgent30-x64.exe /wuforce
I’ve checked the PC for anti-viruses, rootkits, mal-ware, nothing of that sort. I reset all the VPN connections, and turned off the firewall temporarily, still nothing.
I’ve checked access permissions on C: and it’s sub-folders, both built-in Users and Administrators have read/write privileges.
Also tried everything in http://support.microsoft.com/kb/949358, and manually rebuilding/reinstalling the Windows Update agent.
I’m at my wit’s end here, not sure what else to do/try, any suggestions???
-
#1
Привет, не могу установить обновления через центр обновлений Windows Update — вроде бы винда пытается что то ставить а потом выдает аж 2 ошибки с кодами
Код 8024402С
Код 80246007
Пробовал перезагружаться, и перезапускал службу — бестолку. Подскажите решение…
-
#2
Попробуйте следующие варианты:
1. Временно удалите установленный антивирус (может потребоваться перезагрузка). Проверьте.
2. Выполните шаги по восстановлению исходного состояния компонентов Центра обновления Windows, предложенные в статье по адресу http://support.microsoft.com/kb/971058/ru. Опять же, проверьте.
3. Поскольку ошибка связана с подключением к серверу обновлений, попробуйте использовать другое подключение через другого провайдера, если есть такая возможность. Также установите Internet Explorer в качестве обозревателя по умолчанию и выполните рекомендации из этой статьи.
Перезапуск службы BITS (restart-service bits) + повторная установка обновлений
-
#3
0x80246007 — происходит по многим причинам, среди которых самые распространенные
- База данных Центра обновления Windows повреждена.
- Когда другой процесс конфликтует с компонентом Центра обновления Windows.
- Даже когда есть проблема с услугами BITS.
-
#4
частично победил перезапуском сервера. Теперь осталось понять почему обновления ставятся не все сразу..
Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Service Pack 1 Windows Server 2012 Standard Еще…Меньше
Проблемы
При обновлении Windows Server 2008 до Windows Server 2008 R2 появляется следующее сообщение об ошибке:
После обновления эти функции Windows могут работать неправильно. Перед обновлением рекомендуется отключить функции. Отмените обновление, откройте панель управления и выполните поиск по запросу «Включение и отключение компонентов Windows». Windows SharePoint Services 3.0
При обновлении Windows Server 2008 до Windows Server 2012 появляется следующее сообщение об ошибке:
Windows не будет устанавливаться, пока не будет пройден каждый из этих моментов. Закройте программу установки Windows, проследите за каждым из них, а затем перезапустите программу установки Windows, чтобы продолжить. Для продолжения необходимо перезапустить Windows, чтобы изменения в системных файлах можно было выполнить. Внесите эти изменения. Отключите эти функции Windows. Windows SharePoint Services 3,0 – ознакомьтесь со статьей Microsoft Knowledge Base: 962216
Причина
Эта проблема возникает из-за того, что выпущенные версии Microsoft Windows SharePoint Services 3,0 и Microsoft Windows SharePoint Services 3,0 с пакетом обновления 1 (SP1) не поддерживаются в Windows Server 2008 R2 или Windows Server 2012.
Решение
Windows SharePoint Services 3,0 необходимо обновить до пакета обновления 2 (SP2), прежде чем можно будет обновить Windows Server 2008 до Windows Server 2008 R2 или Windows Server 2012. Начиная с пакета обновления 2 (SP2), Windows SharePoint Services 3,0 поддерживается в Windows Server 2008 R2 и Windows Server 2012. Чтобы установить Windows SharePoint Services 3,0 с пакетом обновления 2 (SP2) на компьютер под управлением Windows Server 2008 R2 или Windows Server 2012, посетите один из указанных ниже веб-сайтов центра загрузки Майкрософт.
Windows SharePoint Services 3,0 с пакетом обновления 2 (SP2)
Нужна дополнительная помощь?
Table of Contents
- Background
- Error message
- Log file location
- Downlevel Phase
- Dump analysis
- References
- Solution
Background
We decided to move our domain controller from Windows Server 2008 R2 to Windows Server 2012/R2 (physical machine-Dell), as it was a domain controller so we had to meet some prerequisites before we could proceed with the upgrade. We met all the prerequisites.
A disk of Windows Server 2012 R2 was inserted into the system and upgrade was initiated, compatibility report came OK and upgrade process started but it didn’t complete and rollback to Windows Server 2008 R2 (thank god the rollback didn’t fail) after the first
reboot.
Error message
We saw below message after the machine came up:
---------------------------
Install Windows
---------------------------
This version of Windows could not be installed.
Your previous version of Windows has been restored, and you can continue to use it. Before trying to install this version of Windows again, check online to see if it is compatible with your computer.
---------------------------
OK
---------------------------
Log file location
Before we proceed further here’s the location of the log files which can be checked while working on OS upgrade issue.
Below logs can be checked in case of an error while downlevel phase process (downlevel phase means, the in-place upgrade process before the first reboot):
- C:WINDOWSPANTHERsetupact.log (Contains information about setup actions during the installation).
- C:WINDOWSPANTHERsetuperr.log (Contains information about setup errors during the installation).
You can check below logs in case of rollback after the reboot:
- C:$WINDOWS.~BTSourcesPanthersetupact.log (Contains information about setup actions during the installation).
Please check below link for more information about different log files:
Windows Vista, Windows 7, Windows Server 2008 R2, Windows 8.1, and Windows 10 setup log file
locations
Interestingly, in our scenario, we didn’t find any errors in the downlevel phase and post reboot, log files are mentioned below:
Downlevel Phase
2017-02-09 03:12:14, Info [0x0640d2] IBSLIB [Setup Disk Usage] ------ Drive C: ------
2017-02-09 03:12:14, Info [0x0640d3] IBSLIB [Setup Disk Usage] Total bytes on drive: xxxx.xx MB (xxxxxxxxxx.xx bytes)
2017-02-09 03:12:14, Info [0x0640d4] IBSLIB [Setup Disk Usage] Free bytes available to user: xxxxx.x MB (xxxxxxxx xxbytes)
2017-02-09 03:12:14, Info [0x0640d6] IBSLIB [Setup Disk Usage] Found Setup folder/file [LS Folder ].
2017-02-09 03:12:14, Info [0x0601dc] IBS Setup has completed phase 1 at 2017-02-09 03:12:14
2017-02-09 03:12:14, Info [0x0601ef] IBS RestartMachine:Successfully enabled the shut down privilege
2017-02-09 03:12:14, Info [0x0601f0] IBS RestartMachine:Trying to reboot machine from downlevel OS.
2017-02-09 03:12:14, Info [0x0601f1] IBS RestartMachine:Call to InitiateShutdownEx() succeeded. Shutdown should occur soon.
Logs of the server after the reboot (it was server 2008 R2 at this time):
2017-02-09 03:18:50, Info [0x0e00cf] TOOL Starting OS Rollback... (launched with command line ["/Upgrade"])
2017-02-09 03:18:51, Info TOOL OS Rollback: Rolling back upgrade...
2017-02-09 03:18:52, Info [0x090009] PANTHR CBlackboard::Close: x:$windows.~btsourcesrollbacksetupinfo.
2017-02-09 03:18:52, Info [0x064149] IBSLIB RollbackExecuteSequence in progress...
Because we didn’t have any error in the above logs means that something went wrong while the machine was rebooting.
We tried to check if machine generated any dump file and we got the clue. We actually found a minidump at the location e:$Windows.BT~windowsminidump
Point to be noted here is that the minidump was not in C drive rather we found it in E drive so please check all the drives for the logs/dumps, in case if you are dealing with OS upgrade issues.
Dump analysis
We analyzed the dump and found that the issue caused by a graphics driver g200ewm.sys (Matrox Graphics), analysis is mentioned below:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000005, 0, ffffd00020d21b98, ffffd00020d213a0}
!analyze -v
Probably caused by : g200ewm.sys ( g200ewm+1925e )
References
You may check below article about analyzing a dump file:
How to Debug Kernel Mode Blue Screen Crashes (for beginners)
Solution
The issue was resolved after we uninstalled this graphics driver and initiated the upgrade with the basic VGA driver.
- Remove From My Forums
-
Question
-
Hi All,
I’m having a trouble with one VM and I forgot to make a snapshot
I already try to use Windows 2008 setup disk iso to create bootrec on Windows.oldwindows to boot to Windows 2008 r2
It’s successful but when I logon either on the console or RDP what I see is just a black blank screen.
Any solution to fix this ?
I’m running the chkdsk now…
All replies
-
Please try to update your server.
Mark it as answer if your question has solved. MCT Regional Lead. x2 MCSE-MCSA Exchange Server & Windows Server
-
I would create a new VM. I would then install a clean copy of windows server 2012 R2. Then I would use the old VM’s virtual disk and copy the desired data from it to the new system. In place upgrades leave the possibilities of upgrade artifacts.
Better to start with a clean OS image.Better yet, I would create the new VM as either 2016 or 2019 instead of ‘upgrading’ to such an old version. If performing an upgrade, it is better to upgrade to the most current version possible.
tim
-
Edited by
Tuesday, March 19, 2019 11:49 AM
-
Edited by
-
Hi,
Thanks for posting in our forum!
I am agree with Tim’s last words, if it were me, I will recreate a new 2016 VM, and then copy all the data I needed from the old VHD. Inplace upgrade
is not my choiceBest Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Proposed as answer by
Danie1zhouMicrosoft contingent staff
Monday, March 25, 2019 6:04 AM
-
Proposed as answer by
-
Well… There’s the decision from my team to do the inplace upgrade for this VM.
I’m able to roll it back to 2008 R2 then upgrade it to 2012 R2 one more time and it’s success this time.
However it seem like the Windows update is broken and has 8024200D error all the time.
I try to fix it with many solution and not success yet. Running dism with installation disk as source now.
Anyone have any other idea ?
update… after repair the image the Windows Update still failed.
-
Edited by
Archdragoon
Thursday, March 21, 2019 9:23 AM
-
Edited by
-
Hi,
According to your description, the issue seems a little strange, we are trying to involve someone more professional to look into this issue, if there’s any useful information or suggestions, we’ll feedback as soon as possible.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Thanks Daniel but it’s fine now.
All the problem come from the broken… or should I say bad ISO file ?
First attempt I upgrade this VM from 2008 R2 with x18-27588 which is actually 2012 not 2012 R2.
But I never think that it’s related to Windows update failure.
This time I use x19-82891 to upgrade my VM and it’s working very well.
Funny!!
-
Proposed as answer by
Danie1zhouMicrosoft contingent staff
Monday, March 25, 2019 6:04 AM
-
Proposed as answer by
-
Hi,
I am glad to hear that!
Thanks for your sharing!
if you have any other concerns, please feel free to let me know.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
- Remove From My Forums
-
Question
-
Hi All,
I’m having a trouble with one VM and I forgot to make a snapshot
I already try to use Windows 2008 setup disk iso to create bootrec on Windows.oldwindows to boot to Windows 2008 r2
It’s successful but when I logon either on the console or RDP what I see is just a black blank screen.
Any solution to fix this ?
I’m running the chkdsk now…
All replies
-
Please try to update your server.
Mark it as answer if your question has solved. MCT Regional Lead. x2 MCSE-MCSA Exchange Server & Windows Server
-
I would create a new VM. I would then install a clean copy of windows server 2012 R2. Then I would use the old VM’s virtual disk and copy the desired data from it to the new system. In place upgrades leave the possibilities of upgrade artifacts.
Better to start with a clean OS image.Better yet, I would create the new VM as either 2016 or 2019 instead of ‘upgrading’ to such an old version. If performing an upgrade, it is better to upgrade to the most current version possible.
tim
-
Edited by
Tuesday, March 19, 2019 11:49 AM
-
Edited by
-
Hi,
Thanks for posting in our forum!
I am agree with Tim’s last words, if it were me, I will recreate a new 2016 VM, and then copy all the data I needed from the old VHD. Inplace upgrade
is not my choiceBest Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.-
Proposed as answer by
Danie1zhouMicrosoft contingent staff
Monday, March 25, 2019 6:04 AM
-
Proposed as answer by
-
Well… There’s the decision from my team to do the inplace upgrade for this VM.
I’m able to roll it back to 2008 R2 then upgrade it to 2012 R2 one more time and it’s success this time.
However it seem like the Windows update is broken and has 8024200D error all the time.
I try to fix it with many solution and not success yet. Running dism with installation disk as source now.
Anyone have any other idea ?
update… after repair the image the Windows Update still failed.
-
Edited by
Archdragoon
Thursday, March 21, 2019 9:23 AM
-
Edited by
-
Hi,
According to your description, the issue seems a little strange, we are trying to involve someone more professional to look into this issue, if there’s any useful information or suggestions, we’ll feedback as soon as possible.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Thanks Daniel but it’s fine now.
All the problem come from the broken… or should I say bad ISO file ?
First attempt I upgrade this VM from 2008 R2 with x18-27588 which is actually 2012 not 2012 R2.
But I never think that it’s related to Windows update failure.
This time I use x19-82891 to upgrade my VM and it’s working very well.
Funny!!
-
Proposed as answer by
Danie1zhouMicrosoft contingent staff
Monday, March 25, 2019 6:04 AM
-
Proposed as answer by
-
Hi,
I am glad to hear that!
Thanks for your sharing!
if you have any other concerns, please feel free to let me know.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
Hi all,
finally I managed to upgrade to windows 2012R2.
First I used gptgen-1.1 to convert the disk to GPT, and then I started the upgrade but there was again a problem after the convert to GPT I had to fix a lot of things.
Fist step was to create an EFI volume and I used this steps from
http://triplescomputers.com/blog/casestudies/repair-a-corrupted-efiuefi-boot-sector-and-bcd/ Opens a new window
:
X:windowssystem32>diskpart
Microsoft DiskPart version 10.0.10240
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: MININT-3A416N9
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
——– ————- ——- ——- — —
Disk 0 Online 489 GB 0 B *
DISKPART> sel disk 0
Disk 0 is now the selected disk.
DISKPART> list part
Partition ### Type Size Offset
————- —————- ——- ——-
Partition 1 Primary 489 GB 1024 KB
DISKPART> sel part 1
Partition 1 is now the selected partition.
DISKPART> shrink desired=1024
DiskPart successfully shrunk the volume by: 1024 MB
DISKPART> create partition efi size=260
DiskPart succeeded in creating the specified partition.
DISKPART> format quick fs=fat32
100 percent completed
DiskPart successfully formatted the volume.
DISKPART> exit
Leaving DiskPart…
X:windowssystem32>bcdboot c:windows — and this step here fails.
To fix this one I had to change the BIOS to EFI from VMWare. After the change I had to use again the windows disk to open a cmd and assign letter to my EFI volume then to execute cd /d m:EFIMicrosoftBoot and bootrec /fixboot.
Finally I had to rename the BCD and again a problem I could not rename it because it was in use. Then I try to exit the cmd and I got the option to use again Windows 2008R2.
This was the good news, after I started windows 2008R2 I check everything and I found that the EFI volume is used correctly and the disk is now GPT format.
After everything I gave windows one last try to upgrade to Windows 2012R2 and I could not believe it after the restart I got a screen with text Upgrading Windows instead of an error.
Now my machine which was with Windows 2003 is running Windows 2012R2.
Was this post helpful?
thumb_up
thumb_down
- Remove From My Forums
-
Question
-
Hi Everyone,
I currently have Windows Server 2008. As this is near end of life, we are looking to upgrade this to windows server 2012.
Would there ben any recommendations on how to go about this?
Any roles and features that I should be aware of that I need to migrate? Or even programs and software that I might need to do the same with?
Thanks
D
All replies
-
-
Edited by
Friday, October 25, 2019 12:44 PM
-
Edited by
-
Hi Leon,
Thanks for your response.
The upgrade will be 2008 R2 to 2012 R2, for some reason it was downgraded to 2008 R2, prior to me starting. We are moving it back before end of support.
We currently do not have a new server on the side to set up. We would be using the same server.
In the scenario where we use the same server and if that is currently on 2008 R2, are there any considerations I need to take into place?
It is currently used for AD, DNS, DHCP, FileServer, VSS.
It is the Domain Controller.
Thanks
D
-
Hello,
Thank you for posting in our forum.
If we want to upgrade the domain control to win2012R2, we can refer to the article:Step-By-Step:
Active Directory Migration from Windows Server 2008 R2 to Windows Server 2012 R2Tip: This answer contains the content of a third-party website. Microsoft makes no representations about the content of these websites. We provide this content only for your convenience.
Hope the information can be helpful and if there is anything else we can do for you, please feel free to post in the forum.
Best regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Hi Leon,
I’ve just learnt that we will be completing a clean install of windows server 2012.
We currently have a second server set up which runs Windows 2016 and is a replication server of Windows 2008 (server due for an upgrade).
What considerations need to be taken when completing a clean install?
Thanks
D
-
Edited by
Dwayne10
Thursday, October 31, 2019 12:39 PM
-
Edited by
-
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
- Remove From My Forums
-
Question
-
Hi Everyone,
I currently have Windows Server 2008. As this is near end of life, we are looking to upgrade this to windows server 2012.
Would there ben any recommendations on how to go about this?
Any roles and features that I should be aware of that I need to migrate? Or even programs and software that I might need to do the same with?
Thanks
D
All replies
-
-
Edited by
Friday, October 25, 2019 12:44 PM
-
Edited by
-
Hi Leon,
Thanks for your response.
The upgrade will be 2008 R2 to 2012 R2, for some reason it was downgraded to 2008 R2, prior to me starting. We are moving it back before end of support.
We currently do not have a new server on the side to set up. We would be using the same server.
In the scenario where we use the same server and if that is currently on 2008 R2, are there any considerations I need to take into place?
It is currently used for AD, DNS, DHCP, FileServer, VSS.
It is the Domain Controller.
Thanks
D
-
Hello,
Thank you for posting in our forum.
If we want to upgrade the domain control to win2012R2, we can refer to the article:Step-By-Step:
Active Directory Migration from Windows Server 2008 R2 to Windows Server 2012 R2Tip: This answer contains the content of a third-party website. Microsoft makes no representations about the content of these websites. We provide this content only for your convenience.
Hope the information can be helpful and if there is anything else we can do for you, please feel free to post in the forum.
Best regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com. -
Hi Leon,
I’ve just learnt that we will be completing a clean install of windows server 2012.
We currently have a second server set up which runs Windows 2016 and is a replication server of Windows 2008 (server due for an upgrade).
What considerations need to be taken when completing a clean install?
Thanks
D
-
Edited by
Dwayne10
Thursday, October 31, 2019 12:39 PM
-
Edited by
-
Hi,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Cynthia
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
This tutorial contains several methods to fix Windows Update Problems in Windows 7/8/8.1 & Server 2008/2012 OS. In many cases, even in fresh Windows installations, the Windows Update is not working as expected, or it stuck when checking for updates or it displays several errors whenever you try to search for the available updates.
In such cases your system may become slow or unresponsive, because the Windows Update service (svchost.exe) causes high CPU usage. The Windows Update service is an essential feature in all Windows versions, because it is needed to provide all the available important and optional updates needed for the proper Windows operation and security.
The Windows Update problems often occur on Windows 7 or Vista based computers and in most cases, the errors are caused without any obvious reason and without a permanent solution to fix them from Microsoft. For all these reasons, I decided to write this troubleshooting guide, with the most efficient methods to resolve Windows Update problems on Windows 8.1, 8, 7 & Server 2008 or Server 2012.
Problems-Symptoms that are solved with this guide:
Windows Update is checking for updates forever.
Windows Update stuck/freezes.
Windows Update cannot find new updates.
Windows Update cannot currently check for updates because the service is not running.
Windows Update occurred an Unknown error: Code 8007000E
How to Solve Windows Update Issues on Windows 7/8/8.1 & Server 2008/2012
Important:
1. Before proceeding to apply the methods below, in order to troubleshoot Window Update problems, make sure that the Date and Time settings are correct on your system.
2. Try the following trick: Change the Windows Update settings from «Install updates automatically» to «Never check for updates (not recommended)» & restart your system, After restart set the update settings back to «Install updates automatically« and then check for updates. If this trick fails then set the Windows Update Settings to «Check for updates but let me choose whether to download and install them» and then check for updates again.
3. If you have performed a fresh Windows 7 or Server 2008 installation, install Service Pack 1 for Windows 7 or Windows Server 2008 R2, before you continue.
4. Make sure that your computer is clean from viruses and malware. To accomplish this task you can use this Malware Scan and Removal Guide to check and remove viruses or/and malicious programs that may be running on your computer.
Method 1. Force Windows to re-create the Windows Update Store folder.
Method 2. Install the KB3102810 security Update.
Method 3. Install the latest Update Rollup.
Method 4. Run the Windows Update Troubleshooter.
Method 5. FIX Corrupted System Files and Services (SFC).
Method 6: FIX Windows corruption errors with the System Update Readiness tool (DISM).
Method 7: Update Windows by using the WSUS Offline Update tool.
Method 1. Force Windows to re-create the Windows Update Store folder
The Windows Update Store folder (commonly known as «SoftwareDistribution» folder), is the location where Windows stores the downloaded updates.
-If the SoftwareDistribution folder becomes corrupted then it causes problems with Windows Update. So, one of the most efficient solutions to resolve problems with Windows Update, is to recreate the SoftwareDistribution folder. To do that:
1. Simultaneously press the Windows + R keys to open run command box.
2. In run command box, type: services.msc and press Enter.
3. Right click on Windows Update service and select Stop.
4. Open Windows Explorer and navigate to C:\Windows folder.
5. Select and Delete the “SoftwareDistribution” folder.*
(Click Continue at «Folder Access Denied» window).
* Note: The next time that the Windows Update will run, a new empty SoftwareDistribution folder will be automatically created by Windows to store updates.
6. Restart your computer and then try to check for updates.
Method 2. Install the KB3102810 (KB3102812) security Update.
I have seen many times, that Windows Update is checking for updates forever (stuck) without finding updates, even in fresh Windows 8, 7 or Vista installations. Thankfully, Microsoft has released a security update to resolve the «Installing and searching for updates is slow and CPU utilization is high» issue. To apply the fix:
Step 1. Install Internet Explorer 11. *
* Note: This step is applied only to a fresh Windows 7 or Windows 2008 installation. If Internet Explorer 11 is already installed on your system, then skip this step and continue to step 2 below.
1. Download and install Internet Explorer 11 according to your OS version.
2. Restart your computer.
Step 2. Install the KB3102810 Update.
1. Download – but do not install it yet – the following security update according to your OS version, to your computer:
- Windows 7 & Server 2008: KB3102810
- Windows 8.1 & Server 2012: KB31028102
2. After the download, restart your computer.
3. After the restart, immediately install the security update, otherwise the installation hangs.
4. After the installation, restart your computer.
Step 3. Delete the SoftwareDistribution folder.
1. Follow the steps in Method-1 and delete the «SoftwareDistribution» folder.
2. Restart your computer.
2. Navigate to Windows Update and check for updates. Then, let it run at-least half to one hour. If you ‘re lucky, Windows will find all available updates.
Method 3. Install the latest Update Rollup to fix Windows Update issues.
The Windows Update Rollups, in most cases can fix issues with Windows Update. But before installing the latest Windows update rollup, first change the way that Windows install updates to «Never check for updates (not recommended«. To do that:
1. Simultaneously press the Windows + R keys to open run command box.
2. In run command box, type: wuapp.exe and press Enter.
3. Select Change settings on the left.
4. Set Never check for updates (not recommended).
6. Proceed and download the latest Windows Update rollup for your system, but don’t install it (yet).
July 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2
September 2016 update rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1
September 2016 update rollup for Windows 8.1 and Windows Server 2012 R2
7. After the download, restart your computer.
8. After restart, then proceed and install the downloaded rollup.
9. Check for updates.
Method 4. Run the Windows Update Troubleshooter.
Microsoft offered the Windows Update Troubleshooter tool, in order to fix problems with Windows Update.
1. Navigate to Control Panel > All Control Panel Items > Troubleshooting > Fix Problems with Windows Update.
2. Click Next and let Windows to try to fix the update problems.
3. When the repair is completed, restart you PC and check for updates again.
Method 5. FIX Corrupted System Files and Services (SFC).
The next method to solve Windows Update problems is to run the System File Checker (SFC) tool in order to fix Windows’ corrupted files and services. To do that:
1. Open an elevated command prompt:
- Right click at Windows start button and select Command Prompt (Admin)
2. In the command window, type the following command and press Enter.
- SFC /SCANNOW
3. Wait and do not use your computer until SFC tool checks and fixes the corrupted system files or services.
4. When SFC tool finishes, reboot your computer and check for Updates.
Method 6: FIX Windows corruption errors with the System Update Readiness tool (DISM).
The System Update Readiness tool is a Microsoft tool that can fix Windows corruption errors.
Windows 7, Vista & Server 2008:
1. Download and save to your desktop the System Update Readiness tool according to your Windows version.
2. Double click to install the downloaded file (e.g. Windows6.1-KB947821-v34-x86.msu).
3. When the installation is completed, restart your computer and try to install Windows Updates.
Windows 8, 8.1 & Server 2012:
1. Right click at Windows start button and select Command Prompt (Admin).
2. At the command prompt window, type the following command & press Enter:
- Dism.exe /Online /Cleanup-Image /Restorehealth
3. Be patient until DISM repairs component store.
4. When the operation is completed, you should be informed that the component store corruption was repaired.
5. Close command prompt window and restart your computer.
6. Check for updates.
Method 7: Update Windows by using the WSUS Offline Update tool. (Windows 10, 8.1, 8 or 7)
1. Download the latest version of WSUS Offline Update utility.
2. After the download, extract the «wsusoffline.zip» file.
3. From the «wususoffline» folder, double click at UpdateGenerator.exe application.
4. At Windows tab, select the Windows Edition, that you are using.
5. Press the Start button.
6. Be patient until the WSUS Offline Update utility downloads all the available updates.
7. When the download is completed, open the client folder (wsusoffline\client) and double click at «UpdateInstaller.exe» application.
8. Place a check at «Automatic reboot and recall» checkbox.
9. Finally press the Start button and be patient until the WSUS Offline Update installer, installs the downloaded updates to your system.
That’s it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.