Hyper-V VM connection issues after running "Standard"

[ghost]

I casually opened hyper-v to test ubuntu server and as hyper-v is the best for bare metal virtualization.That mistake cost me my whole day.Browsing microsoft forums all day couldn't give me an answer.I was about to Rage Install Linux as Host OS until i remembered that i ran an important script which must have caused the malfunction.

I used the reverse privacy-script.bat to undo changes and the VM ran smoothly after that.Like i don't know which part of the script is causing this.But if you use the script in any windows Hyper-V available version you can replicate the process like this:

After using the privacy script,you go right to hyper-v and test any OS to run as a VM.It will show the problems like screenshots given below:

I would like to ask @undergroundwires as if there is any way to fix this issue by not reversing the whole script.Now the thing is i am not gonna sell my privacy just for some virtual machine nor i am wanna keep myself away from using virtual machine and ALSO I SUPPORT THE CONTRIBUTIONS OF THIS PROJECT from my heart.I would have donated if i had cash,too bad for me.

I have also read an old Issue from users that they've experienced windows sandbox getting broken after using the script and the owner documented it very well.

[undergroundwires]

Hi @0xReverse, do you have the script file you executed (you have it if you used the desktop app)? Or did you run any of the presets?

[undergroundwires]

You can generate different combinations. I wonder about your configuration. Or did you just try "Standard", "Strict"?

I'd be happy to take action if you can figure out which script has caused this otherwise.

[undergroundwires]

I could reproduce this on both Windows 11 Pro 23H2 and Windows 10 22H2 using Hyper-V and an Ubuntu VM.

I found that it's Enable strong RSA key requirement causes this, reverting it solves the issue.

This using Standard (binary search tree with bisect) and found out that Enable strong RSA key requirement causes this. Looking to its docs, we really want to keep them on "Standard":

But as it breaks Hyper-V connection, I believe we have to move it to Strict with a document about it breaking Hyper-V machine something like (breaks Hyper-V VMs).

Thank you for the bug report and the context.

[undergroundwires]

Yes reverting only "RSA Key Requirement" will solve the issue.
Please report back if it solves for you or does not work.

The rest of the Standard is OK.
It should not in anyway interfere with Windows Update, or its a critical bug.

We cannot granularity control this config, once it applies, it applies to all system connections.

My further tests show that Docker, wsl, and Windows Sandbox work fine. This impacts only Hyper-V VM connection, connections to other virtualization-based solutions work fine.

[undergroundwires]

0.13.4 is just released 🎉. Actions taken:

• Add documentation to describe potential disruptions caused by stronger RSA key requirements.
• Move RSA key script from 'Standard' to 'Strict' due to its impact on Hyper-V VMs.

Thank you @0xReverse.

Please create new issues for further ideas/problems.