Windows 10: Problem with instalation Hyper-V

Discus and support Problem with instalation Hyper-V in Windows 10 BSOD Crashes and Debugging to solve the problem; Hi, I tried instal docker, so i need install Hyper-V, but: PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by Aleksander Dyb, Jun 3, 2019.

  1. Problem with instalation Hyper-V


    Hi,

    I tried instal docker, so i need install Hyper-V, but:

    PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All

    >>

    Enable-WindowsOptionalFeature : Enable-WindowsOptionalFeature failed. Error code = 0x800f0831

    At line:1 char:1

    + Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V ...

    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    + CategoryInfo : NotSpecified: Problem with instalation Hyper-V :)) [Enable-WindowsOptionalFeature], COMException

    + FullyQualifiedErrorId : Microsoft.Dism.Commands.EnableWindowsOptionalFeatureCommand


    or:

    PS C:\WINDOWS\system32> DISM /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

    >>

    Deployment Image Servicing and Management tool

    Version: 10.0.17134.1

    Image Version: 10.0.17134.765

    Enabling feature(s)

    [==========================100.0%==========================]


    Error: 0x800f0831


    DISM failed. No operation was performed.

    For more information, review the log file.


    The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

    dism.log:

    2019-06-03 23:52:57, Info DISM PID=8224 TID=8824 Scratch directory set to 'C:\Users\aleks\AppData\Local\Temp\'. - CDISMManager:Problem with instalation Hyper-V :put_ScratchDir

    2019-06-03 23:52:57, Info DISM PID=8224 TID=8824 DismCore.dll version: 10.0.17134.1 - CDISMManager::FinalConstruct

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM PID=8224 TID=8824 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=8224 TID=8824 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=8224 TID=8824 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=8224 TID=8824 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession

    2019-06-03 23:52:57, Info DISM DISM.EXE:

    2019-06-03 23:52:57, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->

    2019-06-03 23:52:57, Info DISM DISM.EXE:

    2019-06-03 23:52:57, Info DISM DISM.EXE: Host machine information: OS Version=10.0.17134, Running architecture=amd64, Number of processors=4

    2019-06-03 23:52:57, Info DISM DISM.EXE: Dism.exe version: 10.0.17134.1

    2019-06-03 23:52:57, Info DISM DISM.EXE: Executing command line: "C:\WINDOWS\system32\Dism.exe" /Online /Enable-Feature /All /FeatureName:Microsoft-Hyper-V

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=8224 TID=8824 Connecting to the provider located at C:\WINDOWS\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 physical location path: C:\ - CDISMManager::CreateImageSession

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Event name for current DISM session is Global\{052A5017-1465-4792-BC36-5E275A2234D1} - CDISMManager::CheckSessionAndLock

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Create session event 0x1b0 for current DISM session and event name is Global\{052A5017-1465-4792-BC36-5E275A2234D1} - CDISMManager::CheckSessionAndLock

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Copying DISM from "C:\WINDOWS\System32\Dism" - CDISMManager::CreateImageSessionFromLocation

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Successfully loaded the ImageSession at "C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21" - CDISMManager::LoadRemoteImageSession

    2019-06-03 23:52:57, Info DISM DISM Image Session: PID=6420 TID=4024 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Initializing a provider store for the IMAGE session type. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\OSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM OS Provider: PID=6420 TID=4024 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM OS Provider: PID=6420 TID=4024 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM OS Provider: PID=6420 TID=4024 Host OS verion is 10.0 - CDISMOSServiceManager::SetDllSearchPath

    2019-06-03 23:52:57, Warning DISM DISM OS Provider: PID=6420 TID=4024 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\LogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger

    2019-06-03 23:52:57, Warning DISM DISM Provider Store: PID=6420 TID=4024 Failed to load the provider: C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log

    2019-06-03 23:52:57, Info DISM DISM Manager: PID=8224 TID=8824 Image session successfully loaded from the temporary location: C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21 - CDISMManager::CreateImageSession

    2019-06-03 23:52:57, Info DISM DISM.EXE: Target image information: OS Version=10.0.17134.765, Image architecture=amd64

    2019-06-03 23:52:57, Info DISM DISM.EXE: Image session version: 10.0.17134.1

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Getting the collection of providers from an image provider store type. - CDISMProviderStore::GetProviderCollection

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\CbsProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2019-06-03 23:52:57, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_SUCCESS

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize

    2019-06-03 23:52:57, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2019-06-03 23:52:57, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_SUCCESS

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\MsiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\IntlProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\IBSProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\DmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info CSI 00000001 Shim considered [l:125]'\??\C:\WINDOWS\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND

    2019-06-03 23:52:57, Info CSI 00000002 Shim considered [l:122]'\??\C:\WINDOWS\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.760_none_eaef1a361d71e348\wcp.dll' : got STATUS_SUCCESS

    2019-06-03 23:52:57, Info DISM DISM Driver Manager: PID=6420 TID=4024 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\UnattendProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\SmiProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Warning DISM DISM Provider Store: PID=6420 TID=4024 Failed to load the provider: C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\AppxProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\ProvProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\AssocProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\GenericProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\OfflineSetupProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\SysprepProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\TransmogProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Transmog Provider: PID=6420 TID=4024 Current image session is [ONLINE] - CTransmogManager::GetMode

    2019-06-03 23:52:57, Info DISM DISM Transmog Provider: PID=6420 TID=4024 Audit Mode: [No] - CTransmogManager::Initialize

    2019-06-03 23:52:57, Info DISM DISM Transmog Provider: PID=6420 TID=4024 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType

    2019-06-03 23:52:57, Info DISM DISM Transmog Provider: PID=6420 TID=4024 Product Type: [WinNT] - CTransmogManager::Initialize

    2019-06-03 23:52:57, Info DISM DISM Transmog Provider: PID=6420 TID=4024 Product Type ServerNT : [No] - CTransmogManager::Initialize

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Connecting to the provider located at C:\Users\aleks\AppData\Local\Temp\47B817B2-E67C-482A-9B96-A5C80A366F21\SetupPlatformProvider.dll. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM Provider Store: PID=6420 TID=4024 Encountered a servicing provider, performing additional servicing initializations. - CDISMProviderStore::Internal_LoadProvider

    2019-06-03 23:52:57, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: OSServices

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Package Manager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Package Manager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: MsiManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: MsiManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: IntlManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: IntlManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: IBSManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DriverManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DriverManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Unattend Manager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: AppxManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: AppxManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: ProvManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: ProvManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: AssocManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: AssocManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: OfflineSetupManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: OfflineSetupManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SysprepManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: SysprepManager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.

    2019-06-03 23:52:57, Info DISM DISM.EXE: Attempting to add the commands from provider: SetupPlatformManager

    2019-06-03 23:52:57, Info DISM DISM.EXE: Succesfully registered commands for the provider: SetupPlatformManager.

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Processing the top level command token(enable-feature). - CPackageManagerCLIHandler:Problem with instalation Hyper-V :private_ValidateCmdLine

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Encountered the option "featurename" with value "Microsoft-Hyper-V" - CPackageManagerCLIHandler:Problem with instalation Hyper-V :private_GetPackagesFromCommandLine

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Encountered an unknown option "featurename" with value "Microsoft-Hyper-V" - CPackageManagerCLIHandler:Problem with instalation Hyper-V :private_GetPackagesFromCommandLine

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Feature Microsoft-Hyper-V-All with CBS state 4(CbsInstallStateStaged) being mapped to dism state 4(DISM_INSTALL_STATE_STAGED) - CDISMPackageFeature::LogInstallStateMapping

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 Initiating Changes on Package with values: 5, 7 - CDISMPackage::Internal_ChangePackageState

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=4024 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize

    2019-06-03 23:52:57, Info DISM DISM Package Manager: PID=6420 TID=6996 Error in operation: (null) (CBS HRESULT=0x800f0831) - CCbsConUIHandler::Error

    2019-06-03 23:52:58, Error DISM DISM Package Manager: PID=6420 TID=4024 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0831)

    2019-06-03 23:52:58, Error DISM DISM Package Manager: PID=6420 TID=4024 Failed processing package changes with session options - CDISMPackageManager:Problem with instalation Hyper-V :processChangesWithOptions(hr:0x800f0831)

    2019-06-03 23:52:58, Error DISM DISM Package Manager: PID=6420 TID=4024 Failed ProcessChanges. - CPackageManagerCLIHandler:Problem with instalation Hyper-V :private_ProcessFeatureChange(hr:0x800f0831)

    2019-06-03 23:52:58, Error DISM DISM Package Manager: PID=6420 TID=4024 Failed while processing command enable-feature. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0831)

    2019-06-03 23:52:58, Info DISM DISM Package Manager: PID=6420 TID=4024 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

    2019-06-03 23:52:58, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0831

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Found the PE Provider. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Package Manager: PID=6420 TID=4024 Finalizing CBS core. - CDISMPackageManager::Finalize

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(SysprepManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: SysprepManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Finalizing the servicing provider(SetupPlatformManager) - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: SetupPlatformManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=6420 TID=4024 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Manager: PID=8224 TID=8824 Closing session event handle 0x1b0 - CDISMManager::CleanupImageSessionEntry

    2019-06-03 23:52:58, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.

    2019-06-03 23:52:58, Info DISM DISM.EXE:

    2019-06-03 23:52:58, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->

    2019-06-03 23:52:58, Info DISM DISM.EXE:

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=8224 TID=8824 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=8224 TID=8824 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider

    2019-06-03 23:52:58, Info DISM DISM Provider Store: PID=8224 TID=8824 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider


    thanks for help, i haven't experience with dism yet.

    :)
     
    Aleksander Dyb, Jun 3, 2019
    #1

  2. Hyper V deativication

    Hi Geoffrey,

    Hyper-V lets you run an operating system or computer system as a virtual machine on Windows. Before proceeding in disabling
    Hyper-V, please create a backup of your files for security purposes.

    To disable Hyper-V, please follow the steps below:

    • On the Cortana search box, type Turn Windows Features on or off and press
      Enter.
    • Look for the Hyper-V folder.
    • Uncheck the tick-box next to the main Hyper-V folder and click
      OK.
    • Restart your PC.

    Should you have further questions, please let us know.
     
    Jefferson Ore, Jun 3, 2019
    #2
  3. Rex99ny Win User
    Where is the Hyper V Manager, How to I start it ?

    I am trying to setup an XP virtual Machine on Windows 10 Pro.

    I followed the steps in Neil Peterson article of 5/9/2016.

    System Requirements - done - ok

    Install Hyper-V - done - ok

    Create a Virtual Switch - skip

    Create a Virtual Machine

    Create a Virtual Machine with Hyper-V Manager

    These steps walk through how to manually create a virtual machine and deploy an operating system to this virtual machine.


    • In Hyper-V Manager, click Action > New >
      Virtual Machine
      to bring up the New

    Uhhhhhhhhh - this step obviously implies one knows

    1) Where the Hyper-V Manager is

    2) How to start the Hyper-V Manager

    Isn't that odd ?
     
    Rex99ny, Jun 3, 2019
    #3
  4. Problem with instalation Hyper-V

    Hyper-V

    That's the problem that I cannot find Hyper-V in Windows Features list, hence I am not able to turn it on or off.
     
    NarekGrigoryan, Jun 3, 2019
    #4
Thema:

Problem with instalation Hyper-V

Loading...
  1. Problem with instalation Hyper-V - Similar Threads - Problem instalation Hyper

  2. A problem with Hyper-V

    in Windows 10 Gaming
    A problem with Hyper-V: Hello,I have a Windows 11 Pro PC and decided to try out Hyper-V. I've made a new virtual machine in Windows 10 yes I downloaded an ISO file from Microsoft. I've already went through the whole Windows installation process. However, whenever I connect to the VM I must close the...
  3. A problem with Hyper-V

    in Windows 10 Software and Apps
    A problem with Hyper-V: Hello,I have a Windows 11 Pro PC and decided to try out Hyper-V. I've made a new virtual machine in Windows 10 yes I downloaded an ISO file from Microsoft. I've already went through the whole Windows installation process. However, whenever I connect to the VM I must close the...
  4. Hyper-V problem

    in Windows 10 BSOD Crashes and Debugging
    Hyper-V problem: I am getting an error generic failure message when trying to open Hyper-V Quick Create. https://answers.microsoft.com/en-us/windows/forum/all/hyper-v-problem/bd928ba4-fe6f-411f-b921-c87d987e5b4e
  5. Hyper-V problem

    in Windows 10 Gaming
    Hyper-V problem: I am getting an error generic failure message when trying to open Hyper-V Quick Create. https://answers.microsoft.com/en-us/windows/forum/all/hyper-v-problem/bd928ba4-fe6f-411f-b921-c87d987e5b4e
  6. Hyper-V problem

    in Windows 10 Software and Apps
    Hyper-V problem: I am getting an error generic failure message when trying to open Hyper-V Quick Create. https://answers.microsoft.com/en-us/windows/forum/all/hyper-v-problem/bd928ba4-fe6f-411f-b921-c87d987e5b4e
  7. Problems Installing Hyper-V

    in Windows 10 Gaming
    Problems Installing Hyper-V: I can't enable Hyper-V on Windows 11. The error I get is "0x00001AB1 [6833] An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log."I've tried through the Control Panel, cmd prompt, and a .bat file....
  8. Problems Installing Hyper-V

    in Windows 10 Software and Apps
    Problems Installing Hyper-V: I can't enable Hyper-V on Windows 11. The error I get is "0x00001AB1 [6833] An attempt to create space in the transactional resource manager's log failed. The failure status has been recorded in the event log."I've tried through the Control Panel, cmd prompt, and a .bat file....
  9. Hyper-V installation

    in Windows 10 Installation and Upgrade
    Hyper-V installation: I have Windows 10 PRO and just turned on Hyper-V to set up a virtual machine. Everything went well until I tried to install the operating system. I bought a version of windows 10 home for this purpose but its on a USB drive and the installation setup doesn't accept this...
  10. Clean install 15014 in hyper-v

    in Windows 10 Virtualization
    Clean install 15014 in hyper-v: I have created an iso using the uup to iso tutorial and it works fine to upgrade existing VMs, setting iso as a dvd. I am trying to clean install it in hyper-v overwriting an existing vm (do not want to change existing vm id) and have set it as a dvd, and changed boot...