Run W11 in Hyper-V with only TPM 1.2 in the W10 host - AND RESULTING ISSUES !!!


All here - now that I've successfully created a Win 11 Pro VM on my Win 10 Pro host, how do I get the Win 11 Pro VM to "see" the folders and additional hard drives on the Win n10 Pro host?
Following a different thread, I originally turned on all of a new External network connection, a new Internal network connection and a new Private network connection, but these alone don't make my new Win 11 VM "see" the drives or folders on the Win 10 host.
 

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM
All here - now that I've successfully created a Win 11 Pro VM on my Win 10 Pro host, how do I get the Win 11 Pro VM to "see" the folders and additional hard drives on the Win n10 Pro host?
Following a different thread, I originally turned on all of a new External network connection, a new Internal network connection and a new Private network connection, but these alone don't make my new Win 11 VM "see" the drives or folders on the Win 10 host.
in file explorer, go to \\nameofhostcomputer\sharename

replace that with the actual computer name and share name, it'll ask you for a user name and password, use

computername\username
password

for computername, use the name of the host computer, and username, a local user on that computer with access to the shared folders.

you could just go to \\nameofhostcomputer and it should connect, and show you all of the available shared folders on that system

I'd get rid of the internal and private connections, and make sure the network is set as private - internal is for VMs and Host to communicate, private is for just VMs to communicate. External should give you access to everything on your network, as well as the host's internet connection

make sure you have a password protected account on the VM host, things get wonky if you don't - it doesn't have to be an account you actually use, as long as you give it access to shared folders

maybe

username: sharingacct
password: LetMeShareFiles!
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Lenovo Thinkstation P500
    CPU
    Intel Xeon E5-1630v3
    Motherboard
    Lenovo Std
    Memory
    32GB DDR4
    Graphics Card(s)
    Nvidia GTX 760
    Sound Card
    Lenovo Std
    Monitor(s) Displays
    2 24" 75hz, 1 27" 144hz
    Screen Resolution
    1080p x3
    Hard Drives
    1x 500GB WD Black NVMe Gen 3 SSD
    1x 750gb WD Black 2.5" 7500rpm
    PSU
    Lenovo Std 650w
    Case
    Lenovo Std
    Cooling
    Lenovo Std
    Keyboard
    Aorus K9 USI Red
    Mouse
    Logitech G502 Hero
    Internet Speed
    1.5Gbps Cable
    Browser
    Firefox
    Antivirus
    Trend Micro WFHBS
pgallagher - thanks - very thorough.
And I was about to post that on my Win 10 "host", Task Manager shows my External New Switch, which is active even when the VM is off, my Internal New Switch and my Default Switch, but not my Private New Switch. I wonder why.
But I might delete or remove the Internal and Private per your recommendation, and then try your suggestions.
One problem is that I do NOT have logon passwords on my Win 10 "host" or my new Win 11 VM. This PC is sitting at home, and I don't want them. But let's see.
 

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM
pgallagher - thanks - very thorough.
And I was about to post that on my Win 10 "host", Task Manager shows my External New Switch, which is active even when the VM is off, my Internal New Switch and my Default Switch, but not my Private New Switch. I wonder why.
But I might delete or remove the Internal and Private per your recommendation, and then try your suggestions.
One problem is that I do NOT have logon passwords on my Win 10 "host" or my new Win 11 VM. This PC is sitting at home, and I don't want them. But let's see.
it's a necessity for networking - but like I said, you don't need it to be a user account that you use.

right click the start button on the Windows 10 host, choose computer management

go to users and groups, click users, right click, create user

make your dummy account for file sharing, set a password on that (you'll never need to use this account for anything else)

now, right click on any folder you want to share, and create a share, give that account read/write/edit access to the share - repeat as necessary

now go to your windows 11 VM, and in file explorer, enter the \\computername for the host

it will ask you for username and password - enter that, tell it to remember the password, and map the shares that show up (right click, map network drive)

it should give you access to the folders you need, and you won't need to use the password again, other than setting up the shares.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Lenovo Thinkstation P500
    CPU
    Intel Xeon E5-1630v3
    Motherboard
    Lenovo Std
    Memory
    32GB DDR4
    Graphics Card(s)
    Nvidia GTX 760
    Sound Card
    Lenovo Std
    Monitor(s) Displays
    2 24" 75hz, 1 27" 144hz
    Screen Resolution
    1080p x3
    Hard Drives
    1x 500GB WD Black NVMe Gen 3 SSD
    1x 750gb WD Black 2.5" 7500rpm
    PSU
    Lenovo Std 650w
    Case
    Lenovo Std
    Cooling
    Lenovo Std
    Keyboard
    Aorus K9 USI Red
    Mouse
    Logitech G502 Hero
    Internet Speed
    1.5Gbps Cable
    Browser
    Firefox
    Antivirus
    Trend Micro WFHBS
how do I get the Win 11 Pro VM to "see" the folders and additional hard drives on the Win n10 Pro host?
If you use the Default Switch then your VM should be able to see the Internet and your host only.

If you use an External Switch then your VM should be able to see and connect to any PC on your network.

Almost everything I know about Hyper-V I have learned from Kari's excellent series of tutorials, I strongly recommend you read them.

 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
It is much easier to turn on rdp in vm and then you can use enhanced mode to access other drives. See tutorials.
 

My Computer

System One

  • OS
    Windows 10 Pro + others in VHDs
    Computer type
    Laptop
    Manufacturer/Model
    ASUS Vivobook 14
    CPU
    I7
    Motherboard
    Yep, Laptop has one.
    Memory
    16 GB
    Graphics Card(s)
    Integrated Intel Iris XE
    Sound Card
    Realtek built in
    Monitor(s) Displays
    N/A
    Screen Resolution
    1920x1080
    Hard Drives
    1 TB Optane NVME SSD, 1 TB NVME SSD
    PSU
    Yep, got one
    Case
    Yep, got one
    Cooling
    Stella Artois
    Keyboard
    Built in
    Mouse
    Bluetooth , wired
    Internet Speed
    72 Mb/s :-(
    Browser
    Edge mostly
    Antivirus
    Defender
    Other Info
    TPM 2.0
pgallagher, bree and cereberus - thanks again for your attention and tips.

As it turned out, late last night, on a reboot, my Win 11 VM started seeing all the shared Network folders on my Win 10 host. I hadn't changed anything, I still have three ethernets (naming three of the four virtual switches) showing in the host's Task Manager, and both OSes still do NOT require a password for logon.. The Shared folders just started showing up in Network on the Win 11 VM, and the 11 VM was able to open what was inside them. (I haven't checked it in the other direction because I don't have any apps in the VM yet.) EDIT - this is only the Shared folders on my Win 10 host, not all the hard drives in the host.

One different or maybe related problem I am noticing is this: When I start the VM, I sometimes get an error message that the VM is already running. But then, if I hit the fix or continue button, it usually starts working. That's a bit concerning.
And the opening process in the VM is to show me a nice photo -- an aerial shot of what looks like across-the-Sound suburbs of Seattle with rivers or bay arms -- with my VM 11 User Name and a button to sign in. I hit that button (no password) and soon the screen goes black and shows the Hyper-V legend in white. Then I either get that error message or I'm in the VM. That's clunky.

Thoughts? Cheers for a holiday Monday!
 

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM
When I start the VM, I sometimes get an error message that the VM is already running.
How do you 'close' the VM when you're done with it? Just closing the connection window is not enough, the VM is still running even if you can't see it. It's a machine like any other, you have to shut it down properly. Do that from within the VM, or from the connection Window's Action menu or Shutdown button. There is a Stop option there as well. Use Stop as a last resort, this is a the equivalent of killing the power for a PC while Windows is running.

Shutting down the Host doesn't necessarily shut down a running VM. In the VM's Settings under Management the default Automatic Stop Action when the Host shuts down is to save the VM state, and the default action when the Host starts up is to to start the VM if it was previously running. You can change these settings.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 4GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
EDITS AT BOTTOM

Bree - This time I Shut Down from inside the Win 11 VM. Then, the window goes black and shrinks and shows me the smaller window for the Virtual Machine Connection but with this popup message:
"The sessions was disconnected. If you want to continue, try to connect again. If the problem persists, contact your system administrator. Would you like to try to reconnect? [Reconnect] [Exit}."
Note that I had not disconnected myself, only Shut Down the VM.
This time, I waited while I'm typing this, and eventually hit [Reconnect]. The white popup disappears, and I see the small black Virtual Machine Connection window with these white letters:
"The virtual machine '[Name]' is turned off. To start the virtual machine, select 'Start' from the Actin Menu. [Start button]."
So, now, I hit Start.
My VM starts up, I get the beautiful blue folded paper, but after maybe five seconds that disappears, the screen shrinks to the black Virtual Machine Connection window with the error message
"The connection was lost because another user connected to the virtual machine. Try to connect again. If the problem persists, contact your system administrator. Would you like to try to reconnect? [Reconnect] [Exit}."
So I hit Reconnect. Now I see the aerial shot of Seattle suburb across the Sound. I hit Sign In. I am connected now to the blue folded paper but with Task Manager running as I had left it earlier !!! The previous instance did not fully shut down !!! I can tell because I had Task Manager running earlier in the VM.
From inside the VM, I Shut Down.
Then I get the same small black window and the first popup message noted at the top here. This time I hit Exit. In the Hyper-V Manager, there is no picture in the bottom pane, and the State of my VM is Off.

Could this be caused by my having all four Virtual Switches? Should I try to Remove the Internal and Private Virtual switches, leaving the External and maybe the Default?

One other thought: Earlier last night, in the VM, I ran one of my favorite personal utilities - this bat file:

Code:
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow
timeout /t 5 /nobreak
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >> "C:\Users\[MyUserName]\Desktop\sfcdetails.txt"
notepad c:\windows\logs\cbs\cbs.log
notepad "C:\Users\[MyUserName]\Desktop\sfcdetails.txt"
pause
rem exit

It ran well and showed me the good results I expected. In fact, it might be this bat that fixed the VM's Network to show me the Shared folders on my Host.
And one other good thing - before I started this post and tried my Shut Downs, in the VM, in Documents, I created a new Folder and set it to be shared Read/Write by Everyone. Then, from the host, I copied a jpg and a pdf into it, and I was able to see and open them in the VM. So that is working nicely.

Anyway, what do you think about my Shut Down saga?

EDITS - Bree - Thanks for the link (four above) to USE LOCAL DEVICES, etc. It's working like a charm. Not only do I see all the hard drives on my Host PC, but when I plugged in a USB stick, it eventually showed up (with a nudge). This Hyper-V is really good!
(Question - is there a converse of this - on my Host Win 10 PC, is there a setting that similarly sees all of my Win 11 VM as an additional drive?)
ONE MORE DETAIL that (who knows) might be relevant to my Shut Down saga - In the Win 11 VM, in Networks, at the top level, three computers are listed: my Win 10 Host, my Win 11VM and "tsclient", which is a stranger.. Before I turned on the "USE LOCAL DEVICES", a doubleclick on tsclient showed nothing. Now it shows all the hard drives on my PC !!! Do you have "tsclient" in your VM's "Networks"? (And what does "ts" stand for?)
But still would appreciate everyone's suggestions about my Shut Down saga.
 
Last edited:

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM
Well - my weekend experiment has succeeded, and I now have an Activated copy of Win 11 Pro in my Hyper-V.

The odd startup saga has died down mostly, all on its own.

Thanks to all here.

To see how I activated with an old Win 7 Pro 64-bit OEM key sticker, go to To activate Win 11, what types of older license are good?
 

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM
Update - A few issues:
  1. Booting and rebooting sometimes have issues. Sometimes it seems to start well, but then the screen will jump back to the Hyper-V Manager with an error message that another user is using the Win 11, and do I want to reconnect? If I hit "Reconnect", i usually get back to the VM.
  2. In my Win 11 VM, Turn Windows Features On and Off says that "Microsoft Defender Application Guard cannot be installed. The processor does not have required virtualization capabilities."
    Now, the processor in the VM seems to be the same as the processor on my Host, so why is there an issue?
    Name Intel CoreCode Name Ivy Bridge
    Technology 22nm
    Specification Intel Core i5-3470 CPU @ 3.20GHz
  3. Question - can VMs in Hyper-V Restart while the Hyper-V Manager maintains a connection? If I ask my Win 11 V< to Restart, I am left with the Hyper-V Manager and it does not go back to the Win 11 VM.
Thoughts? Thanks.
 

My Computer

System One

  • OS
    A Hyper-V Virtual Machine of Win 11 Pro 64-bit v 21H2 running on Win 10 Pro 64-bit v 21H1 host
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell Optiplex 7010
    CPU
    Intel Core i5-3470 CPU with four cores
    Memory
    16GB RAM, of which 8GB is assigned to the Win 11 VM

Latest Support Threads

Back
Top Bottom