Sign in
 

none
Hyper-V Management tool gets uninstalled after a reboot

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am running Windows Server 2012 R2 on a Dell PowerEdge R710 Physical server and we use this as our backup server, running Data Protection Manager.

    We have now decided to upgrade the existing version of the DPM to 2016 and one of the prerequisites is to have 'Hyper-V PowerShell Modules' installed.  

    This gets installed automatically during this installation process and asks for a reboot, after the reboot windows says 92% complete before it says uninstalling and reboots the server again.

    Same thing happens when I install it from GUI or PowerShell CLI.

    Currently not sure why or how to 'fix' this issue and looking for some advice please.

    Many thanks.

    Friday, April 21, 2017 2:35 PM
    |

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sir,

    >>We have now decided to upgrade the existing version of the DPM to 2016 and one of the prerequisites is to have 'Hyper-V PowerShell Modules' installed.  

    Do you mean the following article regarding upgrading DPM to 2016 :

    https://technet.microsoft.com/en-us/system-center-docs/dpm/get-started/upgrade-to-dpm-2016?f=255&MSPPError=-2147217396#new-powershell-cmdlets

    But, it doesn't mentioned 'hyper-v Powershell Module' installation .

     

    Regarding feature installation failed , please check the CBS log on that server .

    Also , please try to use files stored in OS DVD (Assume it is X: drive ) with DISM command:

    dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-Management-Clients /Source:X:\sources\sxs /LimitAccess

    Another feature:

    Microsoft-Hyper-V-Management-PowerShell


    Best Regards,

    Elton

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, April 24, 2017 6:17 AM
    |
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote 
    2017-04-24 10:21:47, Info                  CBS    Attempting to remove poqexec from SetupExecute
2017-04-24 10:21:47, Info                  CBS    Removed poqexec from SetupExecute.
2017-04-24 10:21:47, Info                  CBS    Clearing HangDetect value
2017-04-24 10:21:47, Info                  CBS    Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
2017-04-24 10:21:47, Info                  CBS    WER: Generating failure report for package: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, status: 0x80070057, failure source: AI, start state: Installed, target state: Installed, client id: DISM Package Manager Provider
2017-04-24 10:21:47, Info                  CBS    Not able to query DisableWerReporting flag.  Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170422075700.log to WER report.
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170421152209.log to WER report.
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170421125339.log to WER report.
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170421094012.log to WER report.
2017-04-24 10:21:47, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20170421074900.cab to WER report.
2017-04-24 10:21:47, Info                  CBS    Not able to add %windir%\winsxs\pending.xml to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-04-24 10:21:47, Info                  CBS    Not able to add %windir%\winsxs\pending.xml.bad to WER report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-04-24 10:21:48, Info                  CBS    Clearing original failure status: 0x00000000
2017-04-24 10:21:48, Info                  CBS    Setting ExecuteState key to: ExecuteStateNone
2017-04-24 10:21:48, Info                  CBS    Setting RollbackFailed flag to 0
2017-04-24 10:21:48, Info                  CBS    Clearing HangDetect value
2017-04-24 10:21:48, Info                  CBS    Saved last global progress. Current: 0, Limit: 1, ExecuteState: ExecuteStateNone
2017-04-24 10:21:48, Info                  CBS    Startup: Retrying failed packages.
2017-04-24 10:21:48, Info                  CBS    Startup: Processing complete. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2017-04-24 10:21:48, Info                  CBS    Enabling LKG boot option
2017-04-24 10:21:48, Info                  CBS    Startup processing completed. [HRESULT = 0x800f0922]
2017-04-24 10:21:48, Info                  CBS    Winlogon: Checking to see if CreateSessionNotify has been called at least once.
2017-04-24 10:21:48, Info                  CBS    Winlogon: CreateSessionNotify has been called
2017-04-24 10:21:48, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-04-24 10:21:48, Info                  CBS    Startup: received notification that startup processing completed, allowing user to logon
2017-04-24 10:21:48, Info                  CBS    Winlogon: Stopping notify server
2017-04-24 10:21:48, Info                  CBS    Winlogon: Unloading SysNotify DLL
2017-04-24 10:21:48, Info                  CBS    Failed during startup processing, continuing with Trusted Installer execution [HRESULT = 0x800f0922]
2017-04-24 10:21:48, Info                  CBS    Startup processing thread terminated normally
2017-04-24 10:21:48, Info                  CBS    TiWorker signaled for shutdown, going to exit.
2017-04-24 10:21:48, Info                  CBS    Ending the TiWorker main loop.
2017-04-24 10:21:48, Info                  CBS    Starting TiWorker finalization.
2017-04-24 10:21:48, Info                  CBS    Starting TiWorker initialization.
2017-04-24 10:21:48, Info                  CBS    Ending TiWorker initialization.
2017-04-24 10:21:48, Info                  CBS    Starting the TiWorker main loop.
2017-04-24 10:21:48, Info                  CBS    TiWorker starts successfully.
2017-04-24 10:21:48, Info                  CBS    Universal Time is: 2017-04-24 09:21:48.246
2017-04-24 10:21:48, Info                  CBS    Loaded Servicing Stack v6.3.9600.18384 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.3.9600.18384_none_fa1d93c39b41b41a\cbscore.dll
2017-04-24 10:21:48, Info                  CSI    00000001@2017/4/24:09:21:48.246 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffe56887fa9 @0x7ffe56e14924 @0x7ffe56e1415b @0x7ff609e0d69a @0x7ff609e0df4f @0x7ffe5c6a20f3)
2017-04-24 10:21:48, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
2017-04-24 10:21:48, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2017-04-24 10:21:48, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2017-04-24 10:21:48, Info                  CBS    SQM: Requesting upload of all unsent reports.
2017-04-24 10:21:48, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2017-04-24 10:21:48, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2017-04-24 10:21:48, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2017-04-24 10:21:48, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2017-04-24 10:21:48, Info                  CBS    Session: 30588124_856473250 initialized by client DISM Package Manager Provider.
2017-04-24 10:21:48, Info                  CBS    Enumerating Foundation package: Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~6.3.9600.16384, this could be slow
2017-04-24 10:21:48, Info                  CBS    Ending TiWorker finalization.
2017-04-24 10:21:51, Info                  CSI    00000002 CSI Store 1070157276592 (0x000000f92a5825b0) initialized
2017-04-24 10:21:51, Info                  CSI    00000003@2017/4/24:09:21:51.584 CSI Transaction @0xf92a58de00 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [25]"TI5.30588124_856473250:1/"
2017-04-24 10:21:51, Info                  CSI    00000004@2017/4/24:09:21:51.599 CSI Transaction @0xf92a58de00 destroyed
    Same error. Above is some of the logs I have copied from CBS logs, but I am not sure if this is enough?!
    Monday, April 24, 2017 1:10 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    We have ended up rebuilding the server which fixed the issue.

    • Marked as answer by Latif Yahya Tuesday, April 25, 2017 8:54 AM
    Tuesday, April 25, 2017 8:54 AM
    |