SOLVED

Microsoft Policy Analyzer not working

%3CLINGO-SUB%20id%3D%22lingo-sub-882223%22%20slang%3D%22de-DE%22%3EMicrosoft%20Policy%20Analyzer%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-882223%22%20slang%3D%22de-DE%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvery%20time%20I%20try%20to%20run%20the%20Policy%20Analyzer%20v.3.2.1803.28001%20on%20my%20Win%2010%201809%20the%20tool%20fails%20to%20read%20the%20local%20registry%20or%20the%20local%20policy%20despite%20having%20local%20admin%20rights.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%20message%3A%20An%20error%20occursed%20while%20parsing%20EntityName.%20Line%20156%2C%20position%2082.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnybody%20else%20getting%20that%20message%20or%20any%20idea%20how%20to%20overcome%3F%20Even%20if%20I%20log%20on%20with%20my%20admin%20account%20I%20get%20the%20same%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThx%20%26amp%3B%3CBR%20%2F%3EBR%20Dan%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-886616%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Policy%20Analyzer%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-886616%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F417319%22%20target%3D%22_blank%22%3E%40Daniel_Schmitz_FNC%3C%2FA%3E%20-%20can%20you%20run%20Process%20Monitor%20and%20identify%20which%20keys%20it%20can't%20read%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFWIW%2C%20the%20next%20version%20of%20Policy%20Analyzer%20will%20drop%20%22Compare%20local%20registry%22%20and%20%22Local%20policy%22%20and%20replace%20them%20with%20a%20%22Compare%20to%20Effective%20State%22%20feature.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-900105%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Policy%20Analyzer%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-900105%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F171536%22%20target%3D%22_blank%22%3E%40Aaron%20Margosis%3C%2FA%3ERan%20into%20an%20issue%20with%20that%20functionality%20as%20well%2C%20and%20it%20turned%20out%20that%20the%20Policy%20Analyzer%20isn't%20code%20signed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20that%20next%20version%2C%20can%20we%20get%20the%20app%20and%20components%20digitally%20signed%20by%20Microsoft%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-901088%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Policy%20Analyzer%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-901088%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F314857%22%20target%3D%22_blank%22%3E%40TheOtherJosh%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20versions%20of%20Policy%20Analyzer%20that%20have%20been%20published%20with%20the%20Security%20Compliance%20Toolkit%20have%20%3CEM%3Ealways%3C%2FEM%3E%20been%20digitally%20signed%20by%20Microsoft.%20You%20might%20have%20a%26nbsp%3B%3CEM%3Every%3C%2FEM%3E%20old%20version.%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Fid%3D55319%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3E%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fdownload%2Fdetails.aspx%3Fid%3D55319%3C%2FFONT%3E%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1015330%22%20slang%3D%22en-US%22%3ERe%3A%20Microsoft%20Policy%20Analyzer%20not%20working%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1015330%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F171536%22%20target%3D%22_blank%22%3E%40Aaron%20Margosis%3C%2FA%3EAhh%20...%20there's%20nothing%20like%20being%20an%20early%20adopter%20of%20a%20tool%20...%20(%20it%20was%20file%20version%203.1.6139.4918%20)%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fcool_40x40.gif%22%20alt%3D%22%3Acool%3A%22%20title%3D%22%3Acool%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi all,

 

every time I try to run the Policy Analyzer v.3.2.1803.28001 on my Win 10 1809 the tool fails to read the local registry or the local policy despite having local admin rights.

 

Error message: An error occured while parsing EntityName. Line 156, position 82.

 

Anybody else getting that message or any idea how to overcome? Even if I log on with my admin account I get the same message.

 

Thx & BR
Dan

4 Replies

@Daniel_Schmitz_FNC - can you run Process Monitor and identify which keys it can't read?

 

FWIW, the next version of Policy Analyzer will drop "Compare local registry" and "Local policy" and replace them with a "Compare to Effective State" feature.

@Aaron MargosisRan into an issue with that functionality as well, and it turned out that the Policy Analyzer isn't code signed.

 

For that next version, can we get the app and components digitally signed by Microsoft?

Best Response confirmed by TheOtherJosh (Occasional Contributor)
Solution

@TheOtherJosh 

The versions of Policy Analyzer that have been published with the Security Compliance Toolkit have always been digitally signed by Microsoft. You might have a very old version.

https://www.microsoft.com/download/details.aspx?id=55319

@Aaron MargosisAhh ... there's nothing like being an early adopter of a tool ... ( it was file version 3.1.6139.4918 ) :cool: