none
SSMS 2016 - A pending restart is blocking setup from completing

    Question

  • I have already updated the database engine from RC to the June RTM. But when I try to update SSMS 2016 I get the following error:

    This is the log file:

    https://onedrive.live.com/redir?resid=782E71E9B77FB492!8699&authkey=!AODRqiAkOPAotcs&ithint=file%2clog

    I have restarted many times the PC (at least 3 times) and I always get the same result.
    Friday, June 3, 2016 10:50 PM

Answers

  • Well, problem solved.

    Apparently my VS 2015 installation was corrupted.

    I solved the issue by downloading and running the VS installer "vs_community_ENU.exe" from download-visual-studio.

    The installer didn't recognize my current VS 2015 installation (even though my VS worked). It installed all over again, or at least the missing packages or something.

    Then the SSMS 2016 installation was able to complete.

    Thursday, June 9, 2016 8:22 PM

All replies

  • I know this might sound silly but is there a reason not to do restart. 

    Do you still get the error after restart?

    you probably can install SSMS using command prompt and skip the restart process. there is a switch you can use to skip restart.

    but is there a reason, you would not want to restart, in first place.


    Hope it Helps!!

    Friday, June 3, 2016 11:46 PM
  • Sorry, I forgot to tell that I have restarted many times the PC (at least 3 times) and I always get the same result.

    Can you give me more details about that switch?

    Thanks in advance

    Saturday, June 4, 2016 1:41 AM
  • Sorry, I forgot to tell that I have restarted many times the PC (at least 3 times) and I always get the same result.

    Can you give me more details about that switch?

    Thanks in advance

    try this and see if  it fixes:

    navigate to folder, the installer is and try

    SSMS-Setup.exe /install  /norestart  /log C:\Temp\log.txt

    refer this https://msdn.microsoft.com/en-us/library/bb500441.aspx


    Hope it Helps!!

    Saturday, June 4, 2016 3:15 AM
  • @Stan210 Thanks for your response!

    Sadly, it didn't work. Here is the log file: log.txt

    I also tried running SSMS-Setup-ENU.exe /uninstall /quiet but it didn't do anything. Maybe I should do that with the Release Candidate installer.

    This is the screen that SSMS shows when checks for updates:


    Monday, June 6, 2016 12:17 AM
  • Have a look in HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\PendingFileRenameOperations

    You have to clean up some things there.

    Monday, June 6, 2016 9:24 PM
  • @Erland It appears to be something related to that. I tried clearing that registry entry, running the setup again, restart the PC, run the setup, shut-down, turn on, run the setup, but I get the same result.

    The installer generates the following entries on that registry entry:

    \??\C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\%localappdata%\temp\SsmsSetup\VS2015KB3095681Update

    \??\C:\Users\titob\AppData\Local\Temp\DEL300B.tmp

    \??\C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\

    \??\C:\Users\titob\AppData\Local\Temp\DEL300C.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301A.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301B.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301C.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301D.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301E.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL301F.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL3020.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL3021.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL3022.tmp

    \??\C:\Users\titob\AppData\Local\Temp\DEL5557.tmp


    Wednesday, June 8, 2016 1:11 AM
  • So you are saying that the SSMS installer generates entries in PendingFileRenameOperations and then later it thinks it can proceed because of them?

    I'm afraid that I don't have a single idea of what is going on. I mean, it worked on the machines I tried it on.

    Do you have any security/AV software running? While I hate to give that as an advice, you could try turning it off (and maybe pull the network cable first).

    Wednesday, June 8, 2016 9:15 PM
  • Yes, SSMS installer generates the entries in PendingFileRenameOperations.

    I'm using windows defender on this PC. I just tried installing SSMS 2016 in my laptop (not an upgrade from RC) and it worked ok. I suppose there is something wrong with this PC.

    I really appreciate your help anyway. I will keep using the RC version of SSMS while I can.

    Wednesday, June 8, 2016 9:29 PM
  • Maybe this is the most relevant part from the log:

    [3220:259C][2016-06-07T22:04:54]i000: MainViewModel.OnPackageAction: Install Started for package Update for Microsoft Visual Studio 2015 (KB3095681)
    [3220:259C][2016-06-07T22:04:54]i000: MainViewModel.OnPackageActionProgress: Percent completed: 0, Overall progress: 26
    [3154:1E68][2016-06-07T22:04:54]i301: Applying execute package: VS2015KB3095681Update, action: Install, path: C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\redist\VS14-KB3095681.exe, arguments: '"C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\redist\VS14-KB3095681.exe" /q /norestart /log %localappdata%\temp\SsmsSetup\VS2015KB3095681Update'
    [3220:259C][2016-06-07T22:04:54]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:55]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:56]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:56]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:57]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:57]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:58]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3220:259C][2016-06-07T22:04:58]i000: MainViewModel.OnPackageActionProgress: Percent completed: 50, Overall progress: 30
    [3154:1E68][2016-06-07T22:04:59]e000: Error 0x80044000: Process returned error: 0x80044000
    [3154:1E68][2016-06-07T22:04:59]e000: Error 0x80044000: Failed to execute EXE package.
    [3220:259C][2016-06-07T22:04:59]e000: Error 0x80044000: Failed to configure per-machine EXE package.
    [3220:259C][2016-06-07T22:04:59]i000: MainViewModel.OnPackageAction: Install Completed for package Update for Microsoft Visual Studio 2015 (KB3095681)
    [3220:259C][2016-06-07T22:04:59]i319: Applied execute package: VS2015KB3095681Update, result: 0x80044000, restart: None
    [3220:259C][2016-06-07T22:04:59]e000: Error 0x80044000: Failed to execute EXE package.
    [3154:1E68][2016-06-07T22:04:59]i351: Removing cached package: VS2015KB3095681Update, from path: C:\ProgramData\Package Cache\02A26E554FBB4232ACD36E70D09F2C7893D399CD\

    Wednesday, June 8, 2016 9:31 PM
  • Well, problem solved.

    Apparently my VS 2015 installation was corrupted.

    I solved the issue by downloading and running the VS installer "vs_community_ENU.exe" from download-visual-studio.

    The installer didn't recognize my current VS 2015 installation (even though my VS worked). It installed all over again, or at least the missing packages or something.

    Then the SSMS 2016 installation was able to complete.

    Thursday, June 9, 2016 8:22 PM
  • Glad to hear that you were able to resolve the issue!

    Those sort of problems are certainly not fun at all. Often you just sit there and say to yourself "what?" There are logs, but the logs are verbose, and far from always crystal clear.

    To be fair, it is also very difficult for someone who is writing an installer to foresee what may be wacko on a computer.

    Thursday, June 9, 2016 9:18 PM
  • Same error here. No amount of restarting helps, nor does an install of VS community.

    Anyone?

    Saturday, July 9, 2016 3:34 AM
  • Yes I just have to agree that these problems take up too much time and just wanted to add that when all is not going according to plan, look to any applications that co-exist and may be corrupted that can be affecting the failures... in this case, visual studio was the culprit, and it looks like op was able to solve this in days rather than weeks which is always good.  Good post here for anyone facing similar issues with other software.

    Thanks Erlang for this quote "To be fair, it is also very difficult for someone who is writing an installer to foresee what may be wacko on a computer."

    Erlang Sommarskog

    Wednesday, November 30, 2016 1:19 AM
  • Did anyone get a solution...

    I am totally stuck with the same issue.

    My computer got restated half way through a SSMS install.

    Now i get the same error as above.

    I have tried everything mentioned but nothing helps.

    Please help

    Saturday, September 30, 2017 9:34 AM
  • Recommended repair of possible failures in Windows File System, openning cmd with administrator privileges:

    C:\>sfc /scannow

    Reference: https://technet.microsoft.com/en-us/library/bb491008.aspx

    Friday, February 9, 2018 5:59 AM