Parallels 16 messed up Bootcamp

[Susurs]

Hi!

I decided to try Parallels 16 on my Mac Mini 2018 (10.15.7) for the first time.

I had W10 retail with latest updates on my Bootcamp partition as well, and was initially positively surprised when Parallels asked me whether I want to use Bootcamp partition as no other installation of Windows was necessary in this case.

Windows started up fine, and after installation of Paragon tools things were prety smooth.

However that was a short joy and then I started to notice issues.

1) Windows was not activated in Parallels (Ok I can understand that).

2) I booted to Windows and was surprised that I had activation lost there as well. I uninstalled Paragon tools within W10, but that did not help. Activation troubleshooter did not help also. At that point I went back to Catalina 10.15.7 and removed Bootcamp from Parallels app without launching Windows there anymore.

3) When I tried to get back to Windows on Bootcamp I was greeted with an error message “Bless tool was unable to...” and was unable to restart in Bootcamp partition at all...

So in short - I lost activation and access to Bootcamp.

I reinstalled W10 with Bootcamp assistant and to my relief it got activated automatically (I have a retail key). However, this still does not solve the initial problem and I do not know how to avoid same troubles when using Parallels.

Is there a way to revert W10 activation without reinstalling Windows when Bootcamp is used (Without Parallels)?

What is this ‘Bless’ error and how to avoid it?

If I would call MS and try to reactivate W10 in Bootcamp with this ‘Hardware changed’ issue: Would it be activated both, in Bootcamp and Parallels? If I decided to reinstall Bootcamp after that, then I would get activation issues again probably?

In case I would install another W10 within Parallels, and not use Bootcamp with Parallels - Would my activation on Bootcamp as well as ability to boot to that partition would be preserved?

General question: Is there any performance difference for Windows when it is used with Parallels from a) Bootcamp b) Installed within Parallels itself?

Thank you!

 

[Susurs]

Might not be related to the Parallels but after I reinstalled W10 in Bootcamp, I noticed some unrecognised Bluetooth HID device under Device Manager. BT is working Bootcamp software was installed, and previously there was no such issue (Previous installation).

Has anyone encountered something like it?

 

[IowaLynn]

Did Parallels kb article help:

KB Parallels: Activating Windows Virtual Machine installed from Boot Camp

Windows Virtual Machine installed from Boot Camp partition shows that it is not genuine and ask for activation.

kb.parallels.com

 

[Susurs]

Thank you!

That part would be helpful. Ok, then ‘hardware’ is changed, but it would work for both - Bootcamp and Parallels after reactivation.

Still have to figure out if reverting to original state (and reactivation) is possible without reinstalling Bootcamp, and this ‘bless’ issue, as well as whether using W10 within a separate Parallels installation would leave Bootcamp intact.

 

[IowaLynn]

Where is your Windows image? I downloaded from MS and Bootcamp took it, and immediately began installing. Mac Mini 3020. I bought it and was activated.

I thought there were "rules" about whether to activate in the bootcamp install first or wait until Parallels- their kb and forums cover that.

Running natively with Parallels is supported- I've never used Parallels but would read others comments.

 

[Susurs]

I have W10 2004 image from MS on my SDD drive as well as installation USB which came with retail version of Windows. I have no issues reinstalling the system. The issue is ‘bless’ error (I am quite certain it would reappear if I use Parallels again) and some activation questions (reverting activation without reinstalling).

P.S. There seem to be some info on the internet regarding the ‘bless’ issue. I’ll try to find some solution.

 

[Susurs]

I reinstalled W10 within Parallels, and can confirm that it did not break my Bootcamp partition (no activation issues). There are no ‘bless’ issues so far as well.

The performance seem to be the same either on Parallels using Bootcamp which I tried yesterday, or on W10 separate installation within Parallels.

I also reseted NVRAM an reinstalled Bootcamp one more time - currently there are no unidentified devices anymore under the Device Manager.