@AlexanderKamp said in i cant get the websites that are open in opera:
Now it look like all is fine with the disabled Sevice can it be that opera have a bug to write this service on i have no VMs running and dont not know why the service was on after the opera update...
Windows' hypervisor-V is now an on-by-default part of Windows11 and is designed to isolate and run multiple Windows processes and services as if they were in 'sandboxes' or within a virtual machine. That inherently alters how (or even if) they can be accessed by other software running on the system. While this offers isolation and security protection to those processes, it also can impact how software applications interact with them - either individually or collectively. That includes adding possible complications in how other software apps on the system interact with each other, since they may share access to the same Windows services and processes. This is why it can be so complex and frustrating to troubleshoot hypervisor-related problems - and Windows11 has more than its share of difficult hypervisor-related complaints, as even a quick search of websites will quickly show.
In your case, it seems that ALL your web browsers began having hypervisor problems after an Opera update. What is unclear (and possibly unknowable) is whether a Windows update affecting the hypervisor or its controlled processes also may have occurred around the same time. What seems most likely is that something related to generic web browser interfacing with certain Windows' hypervisor-controlled processes is now triggering errors and system crashes. This may be because of changes/updates made to the hypervisor itself, to the controlled processes, to the interfacing protocols, or to the browser installation(s)... and such changes could have been introduced by intentional updating or by unintentional corruption of files or data within files during either an Opera or windows update.
Because of the complexity of identifying exactly where the specific cause rests, it can be quite difficult to resolve hypervisor-related error causes. Some users with the problem simply turn off the hypervisor and accept the modest risk of exposing the related processes to security intrusions from elsewhere on the system. Other users attempt removal and reinstallation of the hyper-V software itself. Still others try uninstalling all related application software before reinstalling each of them (though this probably would also require use of decent registry cleaning software to remove 100% of the related apps' entries from the registry before reinstalling). Other people (out of frustration) have "cleanly" reinstalled Windows on their systems before reinstalling all their application software. Finally, some have been willing to dig deeply into hypervisor operation and the nature of the controlled processes to track down precisely where the triggering code may lie, but this requires a rather thorough understanding of computer programs and operations to achieve. In any case, regarding what to do and the likely success of each approach, your mileage may vary.
At this point, it's my opinion that the problem on your system lies outside of Opera specifically (though the Opera update may, in some weird way, have introduced changes or corruption that surfaced the problem). Given that Opera has apparently not been flooded with reports and complaints of hypervisor-error problems with its software, it seems unique to your system.
