To make a long story short I have a 32 bit Win 10 pro VM which I am using to run a bunch of old but VERY VALID educational programs that are CD/DVD based. These programs were originally designed to work in Win 98 or XP all 32 bit.
I have created .ISO versions of the CDs and I mount them and run the old programs in a VM.
The way I want to have this work, and the way it DID WORK under the Win 7 "XP Mode" feature is as follows...
A user does a normal log in to the system, was Win 7 ENT, now Win 10 Ent, X64. On the 2nd screen was an Icon which win clicked would start the XP Mode VM, open it up in full screen and log in to the "guest OS" which only had Icons to run the learning
software, which was the only software, other than basic "Windows stuff" and the software to mount the .ISOs of the learning programs installed . The user then would click on one of the Icons, the program would run, they would use it then close it
and either start a new program or close the VM out. At no time would they have to log in to the VM.
The old XP Mode from Win 7 was an excellent tool for doing this and enabled the college I work at to continue to use the many perfectly valid learning/teaching/studying programs that they have with out needing to buy in to the new "pay for the rest
of your life" greed based subscription based/ cloud based learning programs these products have mostly morphed in to.
If Win 10 had a similar XP Mode that would pass sound to the hosting system and could autologin like the XP Mode does on my Win 7 system I would not need to be here asking this question, but alas MS crippled the XP Mode, yes I can run the original XP Mode
VM in Hyper-V and get the old programs running, EXCEPT for sound/resolution which MS has INTENTIONALLY disabled.
Fast forward....
I have a Win 10 Pro x86 VM that is doing everything I need it to except autologin. I can get the VM to autologin, but NOT with ENHANCED MODE active which I MUST HAVE in order to get full resolution to match my monitors etc and even more important sound.
Access to the host systems "sound" etc can only be done, for some, I am sure, VERY STUPID SHORT SIGHTED REASON, with enhanced mode active.
When enhanced mode is active the system, from what my research tells me, has the "base" VM running, somewhere in the background, and then uses RDP to open up a session in to it through which it then gains access to the host systems sound etc. What
a stupid short sighted design. AT ALL TIMES A VM SHOULD ALWAYS BE ABLE TO ACCESS THE SOUND and FULL RESOLUTION of the host system, at the least, at ALL TIMES EVEN IN BASIC MODE....DUH. Think audible "problem" alerts as an example of why this is important.
In general I could live with that IF RDP would support autologin, which for obvious security reasons it at least should not do without a lot of warnings of the dangers.
I have noticed that whenever I RDP in to one of my real PCs there is an option to save my "log in" I do not get this option when Hyper-V is doing the RDP session via Enhanced Mode. (I have read that this saved "log in" can also be manually
done via a settings type of file) I have actually, for security reasons, never used that option so I don't know whether it saves both username and password or just username.
My question for today is can anyone out there figure out a way to get some method of autologin to work for a VM running under Hyper-V AND also keep access to the full resolution of the system and the host systems sound?
Is there a "settings file" I could edit that could help me?
Any "thinking outside the box" solutions for this problem would also be greatly appreciated.
A VERY BIG THANK YOU to any who try to help,
Ralph