Export (0) Print
Expand All
Expand Minimize

The computer needs to be restarted before Setup can continue

 

Applies to: Exchange Server

Topic Last Modified: 2014-07-17

Microsoft Exchange Server 2013 Setup can’t continue because it detected that the local computer needs to be restarted to complete the installation of other programs or updates.

When programs or updates are installed, they sometimes need to make changes to files or other resources on the computer that can only be made during Windows startup. To tell Windows that it needs to make changes during startup, a program or update makes a change to one or both of the following Windows registry keys:

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile

  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

This table shows all of the values that you might see in these keys.

 

Value of UpdateExeVolatile Value of PendingFileRenameOperations Results

Greater than 3

Not applicable

An invalid value was returned.

3

Not applicable

An update that's been installed and another update that's been removed are waiting for the computer to be restarted. If it's a security update, the computer might be at risk until it's restarted.

2

Not applicable

An update that's been installed is waiting for the computer to be restarted. If it's a security update, the computer might be at risk until it's restarted.

1

Not applicable

An update removal is waiting for the computer to be restarted.

0 or missing

Exists and contains value

The installation of an update didn't finish. The system needs to be restarted to finish the installation. If it's a security update, the computer might be at risk until it's restarted.

0 or missing

Empty

The computer doesn’t need to be restarted.

Exchange Setup won't continue and it'll show this error if the UpdateExeVolatile registry key exists and has as value other than 0, or if the PendingFileRenameOperations registry key isn't empty. If you see this error, it usually just means that the computer hasn't been restarted since the last time a program or update was installed. However, sometimes the installation of a program or update doesn't complete properly and the values in these keys aren't reset. The values in these keys are considered to be orphaned. When this happens, Setup will keep telling you that the computer needs to be restarted even if you already have.

There are a couple things you can do to fix this error.

Restart the computer

Restart the computer, and then run Exchange 2013 Setup again. The most common reason for why you'll see this error is because the computer hasn't been restarted since the last time a program or update was installed. Restarting the computer will often fix this error and let Setup continue. If it does, you’re all set and you can get back to installing Exchange.

Remove the orphaned values from the registry

If restarting the computer doesn't fix this error, another program or update probably didn't finish installing properly. When this happens, you'll need to use these steps to remove the orphaned values from the UpdateExeVolatile and PendingFileRenameOperations registry keys before Setup can continue.

Before you go any further, a note about making changes to the Windows registry (or just "registry"). Making incorrect changes to the registry could cause serious problems, and could even force you to reinstall Windows. Before you make any changes to the registry, make sure you have a working backup of your computer.

  1. Press the Windows key + 'R' to open the Run window.

  2. In Open, type regedit.exe, and press Enter to open Registry Editor.

  3. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\.

  4. If the UpdateExeVolatile key exists and contains anything other than 0, do the following:

    1. In the right navigation pane, double-click the UpdateExeVolatile key.

    2. Replace the value in the key with 0, and then click OK.

  5. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\.

  6. If the PendingFileRenameOperations key contains any value, right-click PendingFileRenameOperations in the navigation pane, and then click Delete.

  7. Close Registry Editor.

After you've finished these steps, this error should no longer appear when you run Exchange Setup.

Having problems? Ask for help in the Exchange forums. Visit the forums at: Exchange Server, Exchange Online, or Exchange Online Protection.

Did you find what you’re looking for? Please take a minute to send us feedback about the information you were hoping to find.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft