Windows App Certification Kit test result warnings under Windows 8

Question

Dear forum members/ MS Support,

First of all many thanks to those who may know how to deal with my issues/ or can waivers be applied.

My system spec is as follows:
Windows 8 Consumer Preview OS
Windows App Certification Kit (bundled with Visual Studio 2011 Beta)

I am testing my desktop app(setup.exe) with Microsoft's "Windows App Certification Kit", and the test results showed the following warnings:


Test Case 1.Remove all non-shared files and folders
File 'C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\0x0409.ini' was not deleted.
File 'C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\1033.MST' was not deleted.
File 'C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\filename.msi' was not deleted.


Test Case 2.Do not write to the %WINDIR% or %SystemDrive% folders
File C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\0x0409.ini was written to an incorrect location.
File C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\1033.MST was written to an incorrect location.
File C:\Windows\Downloaded Installations\{59DBC58B-3547-45E5-941F-9CB2A13588AB}\filename.msi was written to an incorrect location.

Test Case 3.Install signed driver and executable files
Non-driver file C:\Program Files (x86)\InstallShield Installation Information\{EE7927A3-AA32-4B2B-BCB4-D5FDB2CF92BE}\ISSetup.dll does not have a valid signature, either embedded or via a catalog file.

I'm now trying to solve these warnings.
In test case 1 & 2, is there a way to delete the files OR change the file location used by the setup.exe, during the install process?
If not, can we apply waiver for these files(these files are not controlled by our company)?

In test case 3, can we apply waiver for the files created by the installer software company, since they are not our company's files?

Thank you in advance for replying these questions.

Answer 1

Hello Julius,

I am trying to involve someone familiar with this topic to further look at this issue.

Thanks.

---

Vicky Song [MSFT]
MSDN Community Support | Feedback to us

Answer 2

Dear Vicky,

Is there any update from your colleagues regarding this issue?

Thanks.

Answer 3

Hi Julius,

Based on the description, you used the third party InstallShield tool to build you installer. We are not sure if this installer is built as compatibility with Windows 8 Consumer Preview version. I searched the official forum from InstallShield  http://community.flexerasoftware.com/forumdisplay.php?f=133, their information was not seems the InstallShield 2012 Express or other versions support for Windows 8 now.

IF it is possible, could you please try to provide one sample installer with us. It can be one installer with an empty project, and just built by your InstallShield. We could help you to test it.

Sincerely,

---

Bob Bao [MSFT]
MSDN Community Support | Feedback to us

Answer 4

Dear Bob,

Thank you for replying.
Yes I am using InstallShield to build my installer.
Regarding the warnings,they are all generated by the InstallShield installer's internal process, which I have no control of.

1.For test case 1 & 2,
the files found under 'C:\Windows\Downloaded Installations' during install are temporary file used by the InstallShield installer.
below are some examples explaing how InstallShield copies files to that location
   http://forums.cnet.com/7723-10152_102-171218/what-is-in-your-windows-downloaded-installations-folder/
   http://www.pcreview.co.uk/forums/c-windows-downloaded-installations-t2378268.html
It is apparent that the InstallShield installer will copy files to 'C:\Windows\Downloaded Installations' during the installation process.
Since I have no control of its internal  file-copying process,   can I apply waiver for these files?

2.As for test case 3, can I apply waiver for InstallShield's files that are not signed?

BRs
Julius

Answer 5

Dear MS team,

Is there any update from your team regarding this issue?

Thanks.

Answer 6

Hi Julius,

what version of InstallShield are you using to create your installer e.g. "InstallShield 2012 Spring"?  In parallel, we are also checking with the product group. 

thanks for the patience,

mike

Answer 7

Hello Mike,

I am using InstallShield 2010 Primier.

Answer 8

Dear Mike,

I would like to know if your team still looking into this issue?

BRs

Answer 9

Julius,

The pathing you see in TC's 1 and 2 is considered a secured location (%system% and its subfolders). "C:\Windows\Downloaded Installations\" was an old location that installers used when downloading files off the Internet (not local installation) usually through Explorer. This is the reason the forum links you posted are out-dated (2006).

You or another internal developer need to query your Setup.rul for that path and change it to a non-restrictive location, such as %temp% or find the location in your Project files and change it. IShield has its own scripting language so you must may have to use the CMDLINE variable properly detect the environmental variable.

If you truly are using a 3rd-party application that is required with your application then you CAN extract the MSI file manually (use Setup.exe extract parameter) and write your own custom installer for the MSI file. I would contact that company first (I'm sure you know why). Also I would get on the horn with that company and ask them to fix their installer project files to logo compatible. You should be able to apply for a logo waiver for all 3rd-party/optional components. Example, certain Microsoft MsXml and VC8 versions recieved warnings during the logo certification, however, those warnings don't count against your applications submission.


If it is an optional component (i.e. not a part of the default installation or REQUIRED to make your product run successfully) then re-do the logo certification test without the optional component installed.

Based on your previous responses, it sounds as if you have access to the project files for that particular runtime file. Changing the extraction path should resolve your issue.