WiFi in Win11 issues in .3915
So i'm going crazy here and don't know where to go next, to Microsoft support or my internet provider... I've happily had Hyper-V on my Windows 11 Insider and some VMs i use for delivering trainings. Few days ago i noticed i no longer can connect to the internet on the VMs. Existing VMs, new VMs, VMs with past snapshots applied, etc.... no internet on the VMs, period. I tried creating new switches several times and nothing helps. However, although i don't need internet to deliver the trainings, when doing so at the university, i always use my host/laptop's internal card with a SIM in it and have no issues whatsoever with the internet in VMs. The SIM i have is from the same provider as my home cable is from. I just turned off my WiFi and connected the cellular network. Boom! VMs instantly have internet access. Turning on WiFi -> no internet again. So at this point i'm kind of stuck and not sure where to go for help. Obviously there is nothing wrong with my Windows OS in general, but there is an issue with the WiFi. On the host, i have no issues with the WiFi, internet is fine and working properly. I'm shutting down my laptop every night, so "restarting" did not fix it. Should i try resetting my router or go to Microsoft Windows support first? I think going to the internet provider has no benefit now, as they will blame the OS. Any thoughts?
Internet Traffic blocked in Edge Sandbox Mode (Windows Defender Application Guard)
I have successfully activated Windows Defender Application Guard but it seems surfing in Edge Sandbox Mode has been impossible. All required gpos and addition requirements as described on here: https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/microsoft-defender-application-guard/configure-md-app-guard https://learn.microsoft.com/en-us/windows/security/application-security/application-isolation/microsoft-defender-application-guard/faq-md-app-guard have been configured accordingly. I had a tip from microsoft support that my firewall could be blocking traffic (NAT)coming from the Host Computer so should allow all IP subnets in the range of 172.x.x.x or 192.x.x.x. I have tested that by allowing this traffic in the Trellix including Remote Ports 49700–65535, as described in Trellix documentation here https://kcm.trellix.com/corporate/index?page=content&id=KB88788 but to no avail. Could there be any other underlying root causes in a typical Enterprise environment where systems have been hardened using Security policies defined by CIS. What rules can be exempted here in order to allow this kind of traffic. Anybody has experience with this kind of environment or issue. Some tips will be welcomed.
17709 domain DNS registration fails, also %LOGONSERVER% var missing.
First I have noticed that the %LOGONSERVER% is no longer present in Server 2019 (at least in the past several builds that I know of). Second, I have tried joinging 17709 Standard and DataCenter installs to both Server 2008R2 domains and now a Server 2019 v17709 domain and they never register with the Domain DNS. They show up in the DHCP (only, not DNS) if their IP is dynamic but when set to static they do not show up in the domain DNS. Even explicitly registering with: ipconfig /registerdns from an elevated cmd does not result in the system showing up in the DNS My current test environment is Server 2019 v17709 DataCenter running the Hypervisor role. A new physical domain controller running Server 2019 v17709 DataCenter with the Active Directory, DNS and DHCP roles. The Domain controller properly shows up in the DNS, however neither the physical hypervisor running DataCenter 17707 or any vm's within its HyperV will properly register with the Domain DNS. However, a Server 2016 vm registers with DNS properly as does a Windows 10 1803 vm.