all,

some time ago I experimented a bit with hyper-v -- so added the feature to 8.1 pro x86_64.

All fine and dandy. However I want to remove it again, in order to be able to use VMware workstation.

Obviously, this can't work with the hyper-v role installed. So I decided to uncheck and remove hyper-v.

What happens is that Hyper-V removal is scheduled but after the necessary reboots and all it ends up with "cannot complete your request' and rolls back whatever was performed ....

Now, I know that refreshing windows could work. Reinstall could work as well. But those wreck the installed software.

Same for reverting tol an older snapshot (or whatever it's called in windows).

Initiating changes to turn off update Microsoft-Hyper-V of package Microsoft-Hyper-V-ClientEdition-Package. Client id: DISM Package Manager Provider.

A reboot is necessary before the selectable update Microsoft-Hyper-V of package Microsoft-Hyper-V-ClientEdition-Package can be turned off.

Update Microsoft-Hyper-V of package Microsoft-Hyper-V-ClientEdition-Package failed to be turned off. Status: 0x800f0922.

I I did a scanhealth, restorehealth and even dism.exe /online /cleanup-image /StartComponentCleanup /ResetBase.

I reverted to the last known snapshot that works -- also no way to remove hyper-v.

Is there anyone who could give a hint / help to remove the role? Google itself comes up with several ways and all

fail the same way. 

• Moved by BrianEhMVP Thursday, July 23, 2015 3:08 PM

Umesh,

I have _all_ patches installed for both the OS and the added software. That's quite a list. 
(268 currently)
I did a sysrestore on a copy halfway june and that didn't help either.

You probably can't tell me what particular "well tested" patch causes this?

• Edited by Roeland Jansen Thursday, July 23, 2015 5:17 PM added details

nope smjain.

I installed windows; installed linux (and therefore grub2) and after a month or so, started playing with hyper-v.

Note that bcdedit needs the /store option to find it so somewhere some setting is lost that  tells bcdedit where the store is. If the nontransparent removal process indeed cannot find the BCD, it may be the cause.

But now... how can I make the system know that the BCD path the (afaik) default c:\boot\BCD...?