Hmm, ok… this can grow in a huge story, anyway…
The Administrator account in Windows has basically the highest privileges and permissions and allows access to all internals of Windows. So for example if some bad guys want to take over your system and get all your data they always try to get access to an account that has these admin permissions.
Windows (as well as OSs like MacOS or Linux) has lots of security issues, detected by various security researchers (like the members of Project Zero at Google) and reported as so called CVEs (Common Vulnerabilities and Exposures). Microsoft and all the other vendors are constantly trying to fix these issues and prepare updates.
However, not all of them can be fixed fast enough and some of them, as an example, allow to take over a system just by reading a website, which is called “drive-by-exploit”. The attacker tries to download some malware code to your system, without you even noticing what happens. The downloaded code then tries to find a vulnerability to get admin permissions. What happens next depends on what the attacker wants, encrypting your disk, downloading private data, etc.
If you are working as an admin the attacker don’t even need to search for the permissions, you are just like an open book, you offer them a “all-you-can-eat” menu.
So you should always work with a standard user account, without admin privileges. If you launch an install package for a software you will see this UAC dialog screen (see below) from Windows asking you for admin permissions. This is ok (as long as the software is from a trusted source), because the software needs to add some information to the Windows registry database and copy the files to the correct directories, like “C:\Program Files” or “C:\ProgramData”. These directories are protected and only writeable by using admin permissions. After finishing the installation the admin privileges are gone again and you can launch the application under your standard user account.
Here is a page from Microsoft explaining what UAC is
On my own machines I work that way. I start the installation as ordinary user, accept the UAC Screen and then work as the standard user. All packages, Cubase, Dorico and SpectraLayers work perfectly fine, including a bunch of Instruments and VSTs.
Windows 11 22H2 contains some new concepts of security, which I haven’t read completely so far, but I guess this is causing a lot of previously not existing problems. So for now I simply stay away from it, until it is more robust and better known.
Long story in brief… stay away from admin accounts for normal daily work.