Hi All, It worked for me after trying various sizes and OS what I used is mentioned below VM SIZE - E4sV4, post installation I changed it to E8sV4 as extra compute was required for my test lab OS - windows10 enterprise 21h2 Security Type of VM should be standard to enable nested virtualization (Trusted Virtual machine will not work)
Great vid. Thanks. Quick question, did you have to do NAT or does bridging work? Not a big deal for workstations, but we have some old Linux VM's that won't run in Azure, so we are trying nested virtualizations, but the network seems to be the tricky part.
Sir i used windows server 2016 azure(GEN2), didnt work,, windows server 2019(GEN@), also didnt work, i used hyper V , the internet connection too didnt work..
@Chris, were you able to find any solution to it as Windows 10 2004 is not available in Azure, please provide some workaround with the latest versions. Thanks in advance🙏
thanks! i have tried lots of windows version and different service plans. At last i make it work! Specs : windows 10 pro 21h2 and Standard E4s v4 - Gen1. Also note that i didnt reboot after 2nd script, dunno if it matters
@Chris Martel Hi can you help with where you found the Windows 10 2004 Enterprise Gen1? Because I don't seem to find it or alternatively which other OS can work with this?
Hi Wincy, I haven't worked on this in awhile. You dont see the Windows 10 2004 Enterprise Gen1 available in the images section? I think other OS will work fine but the main concern is to use the specific Standard E4s_v4 size.
Hello grate video but dir me it is not working with v4 windows 10 enterprise imagr ;( still the same error and next error after closing first is Transport (VMDB) error -14 pipe connection has been brokrn ;(
I will test now! Edit: Just got this error after done everything on video "VMware Workstation and Device/Credential Guard are not compatible" any ideas for how to fix that?
I have diligently experimented with various Azure server types, investing 4 hours of my time. Regrettably, I must inform you that this method is no longer effective.
Hi All,
It worked for me after trying various sizes and OS
what I used is mentioned below
VM SIZE - E4sV4, post installation I changed it to E8sV4 as extra compute was required for my test lab
OS - windows10 enterprise 21h2
Security Type of VM should be standard to enable nested virtualization (Trusted Virtual machine will not work)
You are a life saver, a super hero ♥
This is great, gonna try this asap.
You are a life saver buddy❤️❤️❤️❤️
Chris you are a good man buddy, I dont care what they say about you - 😂😂
Transport (VMDB) error -14: Pipe connection has been broken.?
Great video, going to try this out today!
Thanks! Let me know how it goes!
Great vid. Thanks. Quick question, did you have to do NAT or does bridging work? Not a big deal for workstations, but we have some old Linux VM's that won't run in Azure, so we are trying nested virtualizations, but the network seems to be the tricky part.
Thanks Jason! I used NAT for the VM in the video, I actually haven't tried bridging so that would be a good test. Good luck!
@@chrismartel10 thanks chris!
Sir i used windows server 2016 azure(GEN2), didnt work,, windows server 2019(GEN@), also didnt work, i used hyper V , the internet connection too didnt work..
@Chris, were you able to find any solution to it as Windows 10 2004 is not available in Azure, please provide some workaround with the latest versions. Thanks in advance🙏
thanks! i have tried lots of windows version and different service plans. At last i make it work! Specs : windows 10 pro 21h2 and Standard E4s v4 - Gen1. Also note that i didnt reboot after 2nd script, dunno if it matters
is it working
perfect chris
Windows 2016 don't have. When press right click is don't have program windows power sell. So I can't access to folder
Hello, I tied with these sizes: Standard_E8as_v4 and Standard_E8s_v3 and it does not work
Thanks for the information, seems like its limited to only a few specific sizes for some strange reason.
@Chris Martel Hi can you help with where you found the Windows 10 2004 Enterprise Gen1? Because I don't seem to find it or alternatively which other OS can work with this?
Hi Wincy, I haven't worked on this in awhile. You dont see the Windows 10 2004 Enterprise Gen1 available in the images section? I think other OS will work fine but the main concern is to use the specific Standard E4s_v4 size.
Thank you so much!!
Tried this and the HyperV error isn't there but now I'm getting an error saying Device Guard / Credential Guard needs to be disabled.
Hi Nabil, you used the specific VM series mentioned in the details?
@@chrismartel10 Hi Chris,
I used a Standard_E2s_v3 image, 2vCPU, 16GB of RAM and I've tried OS Win10Pro 1909, 20H1/H2 and 21H1
Same for me. Did you ever find the solution?
It does work with Windows 10 2004 Enterprise Gen1 like in the video. But not with 21H1 or Windows 11
@@lvmeijer Where did you find 2004 image its not there for me
That works perfect with NAT. Did anyone had a chance to make bridging work?
I tried that with linux kali I wonder if it possible to install Mac also
Hello grate video but dir me it is not working with v4 windows 10 enterprise imagr ;( still the same error and next error after closing first is Transport (VMDB) error -14 pipe connection has been brokrn ;(
Sir my vm inside that vmware is not loading it is giving black screen any suggestion
I will test now!
Edit: Just got this error after done everything on video "VMware Workstation and Device/Credential Guard are not compatible" any ideas for how to fix that?
It does work with Windows 10 2004 Enterprise Gen1 like in the video. But not with 21H1 or Windows 11
I have diligently experimented with various Azure server types, investing 4 hours of my time. Regrettably, I must inform you that this method is no longer effective.