Skip to main content

Windows update keep installing on shutdown




Ever have an issue that windows update keep installing on shutdown all over again.

It keeps installing on shutdown but updates never get installed, the next time you shutdown still the same update is applied.

There are quite a few solutions on the web on how to get rid of this issue.

But whatever solution or suggestion on the web that you can find, don't and don't install third party software claiming to solve the issue.

Below is the link which I found to be helpful to solve this kind of issue:


The link is answers.microsoft.com, so I guess it can be trusted.

But don't just follow or believe any instruction from a public forum. I know you are asking for help.

What I mean is try to evaluate whether the instruction or solution given by other people is reliable and not causing any further harm or issue.

Below is the solution from the link above:

(Text below is copied from link posted above)

First, use FixIt for Windows update and try delete or rename %windir%/SoftwareDistribution

If rename SoftwareDistribution not solve the problem, try this:

1. Open Regedit

2. Go to HKLM\Components

3. Delete or rename REG_DWORD "pendingrequired=1"

4. Profit!

So basically, if you find yourself on a situation that Windows update keep installing on shutdown like a cycle, every time you shutdown same update is being applied.

Before doing anything, open registry editor and browse to this path: HKLM\Components (HKEY_LOCAL_MACHINE\Components)

Then look for this key: pendingrequired=1

If the said key is found, delete the key and restart the computer.

If everything goes well the problem should be solved.

But if the key is not found or the problem persist after deleting the key then it could be some other issue.

Deleting or modifying the registry may corrupt the whole system so if you are not sure what you are doing then ask help from an IT person.

Cheers..hope it helps..

Linux Android App cheat sheet:
https://play.google.com/store/apps/details?id=com.LinuxMobileKit

Comments

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...