We earlier talked about the Windows Update problem and the solution to the code 80072ee2 error. Today we shall see the troubleshooting steps and solution to a different kind of error – code 80072f8f which occurs when we do Windows 7 or Vista or XP related updates from Microsoft.
Why does Windows Update Error 80072f8f occur mainly?
So you have bought a new Dell or Samsung laptop. With the hardware you get a brand new Windows 7 Home Premium pre-installed from the OEM manufacturer. Otherwise, you bought Windows 7 Professional or Ultimate from a Best Buy store and you installed on your brand new computer and you are ready to go.
Well, for now, everything is fine. After sometime the Windows giant Microsoft decides to release update to your Windows 7 OS (current update is SP1) or XP (current update is SP3). Now you decide to update to the latest version and fail with an error code of 80072f8f. What’s the reason?
The main reason is this : [Microsoft Article for Vista]
If you receive Windows Update error 80072f8f while checking for updates, your computer’s date and time might not be the same as the date and time for the online Windows Update service.
Ah, you see, you’ve changed the date and time of your system and that’s why your update is not working. Or otherwise, you might have got a hacked or pirated version of Windows and you don’t want your genuine serial number or crack to go blank! Well, in that case you cannot update to the latest release. Either you have to get better hack or crack software to make your Windows genuine and sync your date and time service with that of Microsoft.
The answer is simple. Just change your date & time to the current period. You can follow the following steps from Microsoft Windows article to serve your purpose.
To change your computer’s date and time
- Open Date and Time by clicking the Start button , clicking Control Panel, clicking Clock, Language, and Region, and then clicking Date and Time.
- On the Date and Time tab, make sure that your computer’s date and time are correct. If they’re not, click Change date and time. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
- In the Date and Time Settings dialog box, do the following:
- To change the date, under Date, click the left or right arrows to find the current month in the calendar, and then click the current date.
- To change the time, under Time, double-click the hour, minutes, or seconds that you want to change, and then click the arrows to increase or decrease the value.
- When you have finished changing the time settings, click OK.
Or otherwise, there is a better solution to your Windows Update error 80072f8f problem. Just sync your computer clock with any Internet time server. To do it, just follow the succeeding steps.
- Click the Start button , click Control Panel, click Clock, Language, and Region, and then click Date and Time.
- Click the Internet Time tab, and then click Change settings. If you are prompted for an administrator password or confirmation, type the password or provide confirmation.
- Click Automatically synchronize with an Internet time server, select a time server, and then click OK.
This solution should work on Windows 7, Vista, XP and other Windows OS.
How to Fix 80072f8f Error in Windows 8.1 and 8?
If you observe this video, it’ll be very clear that the above same solution also works for 8 and 8.1. In this video the author has clearly shown why the error is coming up. When is computer date and time are set to 2011, he gets the 80072f8f error. But when he changes the time to the current time (i.e Sep 2014 as per the video), you can see the updates are available.
Before changing the date, even if he tried several times to update, it was a failure. Only after correcting the time and syncing with internet time server, if necessary, then only the issue is resolved.
One article mentioned on “TechSupportForum” gives different solutions to the above problem. One author tried to implement the SFC /SCANNOW command in an elevated command-prompt window. After completing it you can also create a CBS.log file of the result. This can be posted on different forums and analyzed by various Windows experts.
If you get the following result after the scan, “Windows Resource Protection did not find any integrity violations” it means your scan is successful and the file has been repaired.
You can also try the following command.
DISM /Online /Cleanup-Image /RestoreHealth
If you get the following message:
The restore operation completed successfully. The component store corruption was repaired. The operation completed successfully.
Then your computer is without issues regarding the above problem.
But if you still face problem there are several ways to go. You can stop and restart your Windows Time Service. You can do that from Services or apply the following command.
net stop w32time
net start w32time
Then if you still get any issue, you can see the problem in Event Viewer.
A better way to check is the CMOS battery. One of its purposes is maintain proper date and time of your computer hardware. So using F12 and Del key (depending upon your brand), you can go to your boot options and change the firmware or time over there.
If that fails too, than you can follow this link in Internet Explorer 6.0 or above only and update your root certificates. You need to find the OS (there are root certificates even for Windows 8.1 and 8) and click on Add. Download the update, run it on your PC and restart the computer. This should work out.
How to Fix 80072f8f Issue in Windows Phone?
This is the solution from “PCAdvisor”.
Double-check that the date and time are set correctly on your phone. This error occurs when attempting to run Windows Update while your clock is set incorrectly. Simply correcting the date and time usually makes this error go away. The same issue can also occur on desktop PCs when running Windows Update.
This problem was reported by a Nokia Lumia 1020 user, who wanted to update to latest Cyan release of the Windows mobile operating system.
The following article is updated on Nov 16th, 2014.