Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 264
  • Last Modified:

"Error Found: The attack surface analyzer test detected the following errors"

I am trying to certify apps on a clean Windows 8.1 virtual machine.   It's pretty much an out of the box setup with a couple of apps on it and Windows App Certification Kit 3.4.  Well, I am FAILING all of my installers on the error below, but if you notice the error is actually error-less.   There are no errors produced.  

I've reinstalled WACK and submitted my installer projects to the developer of our installer software. They were able to successfully pass the step.   I simply have no idea how to deal with this at this point.

It's a standard EXE and MSI project.  No click to run.

Windows security best practices test
FAILED
Attack surface analyzer
•Error Found: The attack surface analyzer test detected the following errors:
•Impact if not fixed: During installation or runtime, the app changed an ACL on a registry key or directory. Changing the default Windows security protections can increase the vulnerability of customer's computer to malware.
•How to fix:  During installation and at runtime, your app must read and write data to the areas prescribed by the Windows App Certification without modifying an existing access control list. See link below for more information:
 Fixing Attack Surface Analyzer Errors
0
TechBento
Asked:
TechBento
  • 2
1 Solution
 
McKnifeCommented:
Hi.

"There are no errors produced" - what do you mean? The message claims, that your apps modifies default ACLs which it shouldn't. Or aint't that true?
0
 
TechBentoAuthor Commented:
See the "...error:"
That's supposed to have file names/paths in it.   Yeah, produced nothing.

Good news is I got around the problem.  This was a clean VM from a MSDN ISO for 8.1 Pro "N".  I scuttled it and rebuilt it using a Windows 8.1 Pro - not the N version - and ... guess what?!  It passed.  I don't know what wacky thing WACK 3.4 was doing, but it seems that my prior Windows installation was too special for it.

So yeah, this is all done for.  I got my app certified and now onto other thing.s
0
 
TechBentoAuthor Commented:
I solved the issue in the last 24 hours.  The solution sucks: rebuild the VM.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now