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

Hi Roeland,

I had the same issue a while ago (Hyper-V vs. VMware clash).
Ended up reverting to an earlier system state with the use of System Restore.

Regards,

Matthijs

• Proposed as answer by M. ter Horst Tuesday, July 28, 2015 4:06 PM
• Marked as answer by MeipoXuMicrosoft contingent staff, Moderator 22 hours 27 minutes ago
• Unmarked as answer by Deason WuMicrosoft contingent staff, Moderator 6 hours 22 minutes ago

Hi Roeland,

I had the same issue a while ago (Hyper-V vs. VMware clash).
Ended up reverting to an earlier system state with the use of System Restore.

Regards,

Matthijs

• Proposed as answer by M. ter Horst Tuesday, July 28, 2015 4:06 PM
• Marked as answer by MeipoXuMicrosoft contingent staff, Moderator Monday, August 10, 2015 8:57 AM
• Unmarked as answer by Deason WuMicrosoft contingent staff, Moderator Tuesday, August 11, 2015 1:02 AM

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

all,


the intermediate solution to disable hyper-v in the BCD worked OK but still, the BCD itself was not found as windows has forgotten.
where it resides -- even though it was the default path.

I tried oldest available snapshot; roll back any patch that could be removed. removed all s/w that was not needed. still no dice.
I gave up as windows 10 also failed to install due to an error that was documented without any way to resolve..

I dumped the linux environment  to a second disk and reinstalled windows 8.1 on the same existing partitions. Obviously, windows itself is not
capable of finding out that there are native operating systems, unlike grub2. SO I had to fix the bootloader afterwards.

I double checked before linux bootloader was fixed, that the BCD was there. It was. I also updated and reinstalled all software again..
Updated to windows 10 and then I reinstalled grub2 -- the BCD is still there and all works  and linux can be started as well.

This leads to believe that it's not the installment of grub2 but a problem within windows.


So basically a windows reinstall causing a major part of a  day.

thnx for the help.