[BUG] Files Extension Fails on Server 2012 R2 systems with Failed Exception Error

%3CLINGO-SUB%20id%3D%22lingo-sub-400880%22%20slang%3D%22en-US%22%3E%5BBUG%5D%20Files%20Extension%20Fails%20on%20Server%202012%20R2%20systems%20with%20Failed%20Exception%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-400880%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20Build%201903%20Preview%2C%20when%20connected%20to%20a%20Server%202012%20R2%20system%2C%20navigating%20to%20the%20Files%20extension%20generates%20the%20following%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENotification%20details%3CBR%20%2F%3EError%3CBR%20%2F%3EFailed%20to%20load%20This%20PC.%20Error%3A%20RemoteException%3A%20The%20term%20'try'%20is%20not%20recognized%20as%20the%20name%20of%20a%20cmdlet%2C%20function%2C%20script%20file%2C%20or%20operable%20program.%20Check%20the%20spelling%20of%20the%20name%2C%20or%20if%20a%20path%20was%20included%2C%20verify%20that%20the%20path%20is%20correct%20and%20try%20again.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20this%20point%2C%20the%20circles%20spin%20and%20never%20load%20the%20files%20tree.%20This%20issue%20does%20NOT%20occur%20when%20connected%20to%20Server%202016%20servers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401127%22%20slang%3D%22en-US%22%3ERe%3A%20%5BBUG%5D%20Files%20Extension%20Fails%20on%20Server%202012%20R2%20systems%20with%20Failed%20Exception%20Error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401127%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F213604%22%20target%3D%22_blank%22%3E%40Aaron%20Hall%3C%2FA%3E!%20I%20confirmed%20that%20we%20can%20repro%20this%20on%201903%2C%20but%20it's%20been%20fixed%20already%20in%20our%20internal%20daily%20builds.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

On Build 1903 Preview, when connected to a Server 2012 R2 system, navigating to the Files extension generates the following error:

 

Notification details
Error
Failed to load This PC. Error: RemoteException: The term 'try' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

 

From this point, the circles spin and never load the files tree. This issue does NOT occur when connected to Server 2016 servers.

3 Replies
Highlighted

Thanks @Aaron Hall! I confirmed that we can repro this on 1903, but it's been fixed already in our internal daily builds.

Highlighted
That's awesome to hear, thank you!
Confirmed this is working on 1904 release. Thanks!