Windows 7 Logo Requirements for InstallShield Developers

If you haven't looked at the Windows 7 Software Logo Program requirements and are curious, then read on.  I've looked and will report.

The good news is that there does not appear to be much different from the Vista Logo Program requirements.  Yes, x64 support is expected with your installations, but you are surprised about that, are you?

If you bit the bullet and got your installation house in order for Vista, then you don't have much to worry about in Windows 7.  If you have been putting off making your applications UAC compliant, then you will be unhappy to learn that UAC is still around.  It's apparently here to stay.  You are still going to have to deal with UAC and manifests in Windows 7.  So, you might as well do it.

Here are the highlights from the Windows 7 Logo requirements doc.  I'm sorry if it's boring.

Policies

1. Comply with AntiSpyware Coalition Guidelines.
   • This means that Microsoft does allow its logo to appear on malware or spyware.  Sorry, hackers.  You won't be able to get the logo on your apps.
2. Do not modify WRP protected resources.
   • Applications must not attempt to install files or modify registry keys protected by WRP (Windows Resource Protection).
3. Ensure ongoing quality.
   • Vendors must not hide unhandled exceptions from Windows error reporting (WER).
   • Use Application Verifier (AppVerifier) within your software development lifecycle.
   • ISVs must conduct application specific testing on both x86 and x64 versions of Windows 7.
   • ISVs must submit test results obtained from an x64 Windows 7 (they left a word out on this first part and I haven't figured out what it is), and execute logo testing on x64 versions of Windows.
   • If there is an issue with an application carrying the Windows 7 logo, and it turns out to be a violation of the logo requirements, MS will confirm the issue and contact the partner for resolution.  ISVs must address the issue with 30-90 days.
   • Microsoft may request a licensed copy of the logo-carrying application in certain cases.

Technical Requirements

1. Clean, reversible installation.
   • An application installation should never force a reboot.
   • An installation should not be dependent on 8.3 short file names (SFN).
   • An installation should not block silent installs/uninstalls.
   • Application installers must create the correct registry entries to allow successful detection and uninstalls.
2. Install to correct folders by default.
   • Applications should be installed to the Program Files folder by default.
   • User data or application data should never be stored under the Program Files folder.
   • All application data that must be shared among users should be stored within ProgramData.
   • All application data exclusive to a specific user and not to be shared with other users of the computer must be store in Users\<username>\AppData.
   • You should never write to the Windows folder or subfolders.  Use the correct methods for installing fonts or drivers.
   • In a per-machine installation, user data must be written at first run, and not during the initial installation.
   • A waiver is required for applications writing to the GAC.
3. Digitally sign files and drivers.
4. Support x64 versions of Windows.
   • Appliations must natively support 64-bit or at a minimum, 32-bit applications must run seamlessly on 64-bit systems.
5. Do not block installation or application launch based on OS version check.
   • Applications must not perform version checks for equality (== 5.1).  Use a greater than or equal check (>= 5.1).
6. Follow User Account Control (UAC) Guidelines.
   • Most applications do not require administrator privileges at run-time, and should be just fine running under a standard user account.
   • Windows applications must have a manifest that defines the execution levels and tells the OS what privileges the application requires.
7. Adhere to Restart Manager Messages.
   • Applications must not block the shutdown process.
8. Do not load Services and Drivers in Safe Mode.
9. Support Multiuser Sessions.
   • Windows users should be able to run concurrent sessions without conflict or disruption.

If you want to read the Windows 7 Software Logo Program requirements document, you can download from here.  I uploaded a copy to my server, because to download it from Microsoft, you have to install some file transfer software.  I thought it would just be easier to offer it to you here:

http://www.installationdeveloper.com/docs/windows-7-client-software-logo.pdf

Here is a link to the Windows 7 Software Logo Program page: 

http://msdn.microsoft.com/en-us/windows/dd203105.aspx

My installation development philosophy is this.  Develop your applications and installations like you were going to submit them for Logo Certification.  Even if you aren't.

Develop applications and installations to run in a Standard User account, unless you positively, absolutely have to run under an Administrator account.  Follow the requirements, run and pass the validation checks, do a lot of testing, and you will have many happy customers for the companies you work for.

If you do these things…

…you'll likely get a raise, the kids can go to college, and all will be right with the Windows world.

How to Add a License File to Your InstallShield Project