Windows Server 2022 Preview Bug Discovered

%3CLINGO-SUB%20id%3D%22lingo-sub-2491853%22%20slang%3D%22en-US%22%3EWindows%20Server%202022%20Preview%20Bug%20Discovered%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2491853%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20running%20Windows%20Server%202022%20Preview%20Standard%20and%20have%20discovered%20a%20bug.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20not%20really%20sure%20where%20to%20report%20it%2C%20so%20I'll%20report%20it%20here.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurrently%20running%20Build%2020348.75.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20run%20secpol.msc%2C%20and%20change%20Network%20List%20Manager%20Policies%2FNetwork%2FNetwork%20Location%20and%20change%20the%20server%20to%20Location%20Type%20-%20Private%2C%20when%20you%20reboot%2C%20the%20server%20is%20unresponsive%20in%20terms%20of%20for%20example%20clicking%20control%20panel%2FWindows%20Defender.%20Cant%20launch%20Edge%20etc.....something%20fundamentally%20wrong.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThankfully%20I%20have%20a%20snapshot%20to%20rollback%20to%2C%20but%20this%20is%20a%20pretty%20big%20issue%20for%20my%20servers%20that%20are%20not%20domain%20joined%2C%20but%20are%20in%20fact%20on%20a%20private%20network%2C%20not%20a%20public%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2491853%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%202022%20Bug%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2491908%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Server%202022%20Preview%20Bug%20Discovered%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2491908%22%20slang%3D%22en-US%22%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1089740%22%20target%3D%22_blank%22%3E%40alanplum241276%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3ECheck%20out%20this%20article%20with%20further%20information%20how%20to%20report%20bugs%3A%3CBR%20%2F%3E%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.howtogeek.com%2F368667%2Fhow-to-report-a-problem-or-send-feedback-about-windows-10%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.howtogeek.com%2F368667%2Fhow-to-report-a-problem-or-send-feedback-about-windows-10%2F%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3EBest%20regards%2C%3CBR%20%2F%3ESchnittlauch%3CBR%20%2F%3E%3CBR%20%2F%3E%22First%2C%20No%20system%20is%20safe.%20Second%2C%20Aim%20for%20the%20impossible.%20Third%2C%20no%20Backup%2C%20no%20Mercy%22%20-%20Schnittlauch%3CBR%20%2F%3E%3CBR%20%2F%3EMy%20answer%20helped%20you%3F%20Don't%20forget%20to%20leave%20a%20like.%20Also%20mark%20the%20answer%20as%20solved%20when%20your%20problem%20is%20solved.%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2491910%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Server%202022%20Preview%20Bug%20Discovered%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2491910%22%20slang%3D%22en-US%22%3EWith%20respect%2C%20I%20am%20reporting%20a%20bug%20with%20server%202022%2C%20not%20windows%2010.%20Server%202022%20does%20not%20have%20the%20feedback%20hub.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2492433%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%20Server%202022%20Preview%20Bug%20Discovered%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2492433%22%20slang%3D%22en-US%22%3EI%20have%20forwarded%20your%20issue%20to%20the%20appropriate%20team%20for%20investigation.%20They%20may%20contact%20you%20directly%20if%20they%20need%20more%20information.%20You%20can%20use%20Feedback%20Hub%20on%20a%20Windows%2010%20box%20to%20report%20a%20bug%20on%20server%2C%20but%20what%20you've%20done%20here%20is%20just%20as%20good.%20Thank%20you%20for%20letting%20us%20know.%3C%2FLINGO-BODY%3E
New Contributor

Hi,

 

I am running Windows Server 2022 Preview Standard and have discovered a bug.

 

I'm not really sure where to report it, so I'll report it here.

 

Currently running Build 20348.75.

 

If you run secpol.msc, and change Network List Manager Policies/Network/Network Location and change the server to Location Type - Private, when you reboot, the server is unresponsive in terms of for example clicking control panel/Windows Defender. Cant launch Edge etc.....something fundamentally wrong.

 

Thankfully I have a snapshot to rollback to, but this is a pretty big issue for my servers that are not domain joined, but are in fact on a private network, not a public one.

5 Replies
Hi @alanplum241276

Check out this article with further information how to report bugs:

https://www.howtogeek.com/368667/how-to-report-a-problem-or-send-feedback-about-windows-10/

Best regards,
Schnittlauch

"First, No system is safe. Second, Aim for the impossible. Third, no Backup, no Mercy" - Schnittlauch

My answer helped you? Don't forget to leave a like. Also mark the answer as solved when your problem is solved. :)
With respect, I am reporting a bug with server 2022, not windows 10. Server 2022 does not have the feedback hub.
I have forwarded your issue to the appropriate team for investigation. They may contact you directly if they need more information. You can use Feedback Hub on a Windows 10 box to report a bug on server, but what you've done here is just as good. Thank you for letting us know.

@alanplum241276, I am investigating your reported issue.  In order to best serve you I will need more information.  With your settings stabilized (network set as Private), from an elevated command prompt, please run the following
NetSh.exe WFP Capture Start
   Attempt to Launch Edge ( "%ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe" --profile-directory=Default )
   Attempt to open the Windows Defender Firewall control panel ( %WinDir%\System32\Firewall.cpl )

   Attempt to open the Windows Defender Firewall Snap-In ( %WinDir%\System32\WF.msc )

NetSh.exe WFP Capture Stop

You can send the resultant WFPDiag.cab to DHarper@Microsoft.com

Thanks
Dusty Harper


@Dusty Harper, I have sent you an email but I have been unable to do what you have asked as the system hangs on NetSh.exe WFP Capture Start when network set to private.