Page 1 of 1

Problems with Windows 7 Logo Program

Posted: Mon Mar 28, 2011 11:26 am
by rodrigo.onclick
Good afternoon,

Our company is entering some applications for the Microsoft Windows 7 Logo Program and for evaluating the first application, Microsoft Windows Logo Kit Software generated a report with some errors, which include problems with the installation process.

Below is the generated error report:

2. Install to the correct folders by default

Test case: Do not write to the %WINDIR% or %SystemDrive% folders

WARNING: This application wrote the following files to %SystemDrive%, and or %WinDir% folders:
File C:\WINDOWS\LOGS\DPX\SETUPACT.LOG was written to an incorrect location.
File C:\WINDOWS\LOGS\DPX\SETUPERR.LOG was written to an incorrect location.
File C:\WINDOWS\SERVICING\PACKAGES\PACKAGE_FOR_KB958488~31BF3856AD364E35~AMD64~~6.2.7600.16513.CAT was written to an incorrect location.
File C:\WINDOWS\SERVICING\PACKAGES\PACKAGE_FOR_KB958488~31BF3856AD364E35~AMD64~~6.2.7600.16513.MUM was written to an incorrect location.
File C:\WINDOWS\SERVICING\SESSIONS\30141024_2834861396.BACK.XML was written to an incorrect location.
File C:\WINDOWS\SERVICING\SESSIONS\30141024_2834861396.XML was written to an incorrect location.
File C:\WINDOWS\SYSTEM32\MSVCR100_CLR0400.DLL was written to an incorrect location.
File C:\WINDOWS\SYSWOW64\MSVCR100_CLR0400.DLL was written to an incorrect location.

...

9. Support multiuser sessions

Test case: Do not write to the %USERS% folder

WARNING: Application did not pass multiuser session compliance check.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\INSTANCE.DAT was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\MIA.LIB was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\OCSBACKUPSETUP.DAT was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\OCSBACKUPSETUP.EXE was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\OCSBACKUPSETUP.MSI was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\OCSBACKUPSETUP.PAR was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\{30E11F97-1C49-4EF8-BD54-29502284C0A5}\OCSBACKUPSETUP.RES was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\MSS00007.LOG was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\00010007.CI was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\00010007.DIR was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\00010007.WID was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\00010007.WSB was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\CIAD0001.000 was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\CIAD0001.001 was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\SEARCH\DATA\APPLICATIONS\WINDOWS\PROJECTS\SYSTEMINDEX\INDEXER\CIFILES\CIAD0001.002 was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\WINDOWS\WER\REPORTQUEUE\NONCRITICAL_00000000_9F1BD742172D8F3DCB32404FEBC4939090D1A3_CAB_09222A0F\CLIENT_MANIFEST.TXT was written to an incorrect location.
File C:\USERS\TODOS OS USUÁRIOS\MICROSOFT\WINDOWS\WER\REPORTQUEUE\NONCRITICAL_00000000_9F1BD742172D8F3DCB32404FEBC4939090D1A3_CAB_09222A0F\REPORT.WER was written to an incorrect location.


I do not know where to start to change the design of the installer to remedy the problems reported by Microsoft.

I await response.

Thanks,

Rodrigo Duarte
OnClick Sistemas

Re: Problems with Windows 7 Logo Program

Posted: Mon Mar 28, 2011 2:08 pm
by giaviv
Dear Rodrigo,

As far as I know, even though some verification tools fail when ran on InstallAware setups, the actual certification should succeed.

Re: Problems with Windows 7 Logo Program

Posted: Mon Mar 28, 2011 2:19 pm
by rodrigo.onclick
Dear Giaviv,

But the kit as Microsoft pointed writing files in folders that are not allowed recordings, which can occur at runtime error. There is no direct means of burning these files to other folders in Windows?

Thanks,

Rodrigo Duarte
OnClick Sistemas

Re: Problems with Windows 7 Logo Program

Posted: Mon Mar 28, 2011 4:41 pm
by giaviv
Dear Rodrigo,

Have you actually tested your installer to see if these files are being written at runtime?

Re: Problems with Windows 7 Logo Program

Posted: Mon Mar 28, 2011 4:41 pm
by giaviv
Dear Rodrigo,

Have you actually tested your installer to see if these files are being written at runtime?

Re: Problems with Windows 7 Logo Program

Posted: Tue Mar 29, 2011 5:35 am
by rodrigo.onclick
Dear Giaviv,

Yes, the tests were conducted to monitor the tool kit from Microsoft. At the same time there was no other applications running, so the files mentioned were written by InstallAware.

Thanks,

Rodrigo Duarte
OnClick Sistemas

Re: Problems with Windows 7 Logo Program

Posted: Tue Mar 29, 2011 6:12 am
by giaviv
Dear Rodrigo,

When I ran your installer (after building it here) it didn't write to any of the Windows folder entries you mentioned.
How did you physically check for the presence of those files?

Re: Problems with Windows 7 Logo Program

Posted: Tue Mar 29, 2011 12:03 pm
by rodrigo.onclick
Dear Aviv Giladi,

After performing the installation, these files are created in the folder mentioned in the report of errors generated by Microsoft's tool kit, as indicated in the first post. The following attached two images that illustrate the error and also a ZIP folder containing the files.

Why are files are kept in a folder with that name? This breaks with the requirements of Windows 7 Logo Program and OnClick Sistemas need a solution to this problem.

Await solution soon.

Thanks,

Rodrigo Duarte
OnClick Sistemas

Re: Problems with Windows 7 Logo Program

Posted: Tue Mar 29, 2011 12:16 pm
by giaviv
Dear Rodrigo,

What's wrong with writing to ProgramData? That is an excellent, cross-system, user-independent location for files to be written.
Furthermore, you asked on a different post of your how to write to this folder.

Re: Problems with Windows 7 Logo Program

Posted: Wed Mar 30, 2011 1:19 pm
by rodrigo.onclick
Dear Aviv Giladi

I sent this post initially by the error report generated by the Microsoft tools to ensure the application. After searching and reading pages of Microsoft, I found the link http://msdn.microsoft.com/en-us/windows/ff718270 the following snippet of explanations:

[Question] How do I fix the test case 2: Install to correct folders by default failure / warnings?

[Answer]: Applications Should Be installed to the Program Files folder by default. User data or application data must never be stored in this location because of the security permissions configured for this folder. Never write directly to the Windows directory or subdirectories. Use the correct methods for installing files such as fonts or drivers.

The warning shows That the. Config file is stored under C: \. We recommend That All application-specific configuration entries b and stored under the ProgramData directory. Here are default installation directories for your reference:

Native x86 and x64 applications

Program Files -% ProgramFiles%
User's AppData -% APPDATA%
ProgramData -% ALLUSERSPROFILE%
Win32 applications on x64

Program Files -% ProgramFiles (x86)%
AppData -% APPDATA%
ProgramData -% ALLUSERSPROFILE%
All application data That Must Be Shared Among users on the computer Should Be Stored Within ProgramData and all application data exclusive to a specific user and not to Be Shared With Other users of the computer Must Be stored in Users \ <username> \ AppData.


I therefore urge that ignore the initial problem reported in this post.

Thank you for your help.

Rodrigo Duarte
OnClick Sistemas

Re: Problems with Windows 7 Logo Program

Posted: Wed Mar 30, 2011 2:25 pm
by giaviv
Sure, Rodrigo - happy it was resolved!