WARNING: ERROR: Applications are expected to create these registry entries DisplayName, InstallLocation, Publisher, UninstallString, VersionMajor*, and VersionMinor*.
This application did not create the following registry entries:

IMPACT IF NOT FIXED: A user might remove an application not only to free up disk space, but also to return the computer to its state prior to the application being installed. Failure to restore the machine to its original state is a poor user experience. Also applications that do not create the above registry entries will not be found by enterprise inventory tools, and may experience issues in OS migrations and or upgrades scenarios. Windows telemetry tools may not accurately report information about your application.

HOW TO FIX: You can supply all of the information needed to configure Add/Remove Programs in Control Panel by setting the values of certain installer properties in your application's Windows Installer package. Setting these properties automatically writes the corresponding values into the registry. The latest information and best practices that illustrate how to do this can be found at these links 1 and 2.

WARNING: ERROR: This application’s install has forced an immediate reboot without providing the user with an option to restart the computer at a later time.

IMPACT IF NOT FIXED: Forcing an immediate reboot during install can impact users in a variety of negative ways, and could cause data loss.

HOW TO FIX: A reboot should never be the only option at the end of an install or update. Users should have the opportunity to restart later. Guidance on how to handle the need for a reboot is available HERE.

WARNING: ERROR: This application’s uninstall has forced an immediate reboot without providing the user with an option to restart the computer at a later time.

IMPACT IF NOT FIXED: Forcing an immediate reboot during uninstall can impact users in a variety of negative ways, and could cause data loss.

HOW TO FIX: A reboot should never be the only option when uninstalling an application. Users should have the opportunity to restart later. Guidance on how to handle the need for a reboot is available HERE.

WARNING: ERROR: WSLK didn't detect any changes to the file inventory collected during the "Pre-Install" phase. This could be due to a unsuccessful or incomplete uninstall. Please uninstall your application and run this step once you are done. This application failed to remove the following files during uninstall:

IMPACT IF NOT FIXED: Leaving unnecessary files behind wastes disk space and might cause application conflicts later.

HOW TO FIX: Ensure that all files and Add/Remove Program entries are properly removed.

WARNING: ERROR: This application wrote the following files to %SystemDrive%, and or %WinDir% folders:

IMPACT IF NOT FIXED: Avoid storing application’s data to %SystemDrive%, and or %WinDir% folders. The ACLs on certain Windows directories have been changed to enable data sharing and collaboration in data directories and outside of a user's protected directories. File virtualization addresses the situation where an application relies on the ability to store a file, such as a configuration file, in a system location typically writeable only by administrators. Running programs as a standard user in this situation might result in program failures due to insufficient levels of access. Also there are privacy and system integrity concerns when applications do not store files in the correct folders. Using the Known Folder APIs ensures that you are always able to get to your data. Please note: “Virtualization is implemented to improve application compatibility problems for applications running as a standard user on Windows 7. Developers must not rely on virtualization being present in subsequent versions of Windows”

HOW TO FIX: Guidelines and API calls have been provided to help the application to know where to install and store system and data files. More information and guidance can be found at these links 1, 2, and 3.

WARNING: ERROR: This application wrote the following files to a location other than %ProgramFiles%:

IMPACT IF NOT FIXED: Install applications to %ProgramFiles% for native 32-bit and 64-bit applications, and %ProgramFiles(x86)% for 32-bit applications running on x64. The ACLs on certain Windows directories have been changed to enable data sharing and collaboration in data directories and outside of a user's protected directories. File virtualization addresses the situation where an application relies on the ability to store a file, such as a configuration file, in a system location typically writeable only by administrators. Running programs as a standard user in this situation might result in program failures due to insufficient levels of access. Also there are privacy and system integrity concerns when applications do not store files in the correct folders. Using the Known Folder APIs ensures that you are always able to get to your data. Please note: “Virtualization is implemented to improve application compatibility problems for applications running as a standard user on Windows 7. Developers must not rely on virtualization being present in subsequent versions of Windows”

HOW TO FIX: Guidelines and API calls have been provided to help the application to know where to install and store system and data files. More information and guidance can be found at these links 1, 2, and 3.

WARNING: ERROR: The application installed the following unsigned files:

If any of the above files are DLLs, OCX, SCR, CPL or EXEs that are not one of the application’s main executables (has a shortcut on start menu or desktop), they can safely be ignored. All others need to be signed to meet the Windows 7 Software Logo requirements.

IMPACT IF NOT FIXED: Having digitally signed files allows users to know that software is genuine. It also allows detection if a file has been tampered with, by a virus or Trojan for example. Windows 7 will have the ability to prevent any unsigned application from launching with a full administrator access token. If you want your application to operate correctly in locked-down environments, while displaying a more user friendly user interface, it should be signed with an Authenticode signature.

“The elevation prompt displays contextual information about the executable requesting elevation and the context is different depending on whether the application is Authenticode signed. The elevation prompt is seen in two variations: the consent prompt and the credential prompt.”

HOW TO FIX: To sign the application, you can either generate a certificate from makecert.exe or obtain a code-signing key from one of the commercial certification authorities (CAs), such as VeriSign, Thawte, or a Microsoft CA. information and guidance on how to sign your drivers and files is available HERE.

WARNING: ERROR: When this test was started a switch was set indicating that either a 32bit or 64bit application is being tested. The application installed the following files that do not match the specified platform architecture:

If any of the above files are drivers, or 16-bit your application FAILED this test, otherwise you can safely ignore.

IMPACT IF NOT FIXED: 32-bit processes cannot load 64-bit DLLs, and 64-bit processes cannot load 32-bit DLLs. 64-bit Windows does not support running 16-bit Windows-based applications. The primary reason is that handles have 32 significant bits on 64-bit Windows. Therefore, handles cannot be truncated and passed to 16-bit applications without loss of data. Attempts to launch 16-bit applications fail. 32-bit drivers cannot run on 64-bit Windows and must be ported. For user-mode applications, 64-bit Windows includes WOW64, which enables 32-bit Windows applications to execute (with some loss of performance) on systems running 64-bit Windows. No equivalent translation layer exists for drivers.

HOW TO FIX: Install only files and drivers for the corresponding processor architecture. More information and guidance on programming for compatibility with 64bit operating systems is available HERE.

WARNING: ERROR: Application failed to install under a higher Windows version.

IMPACT IF NOT FIXED: Customers are artificially blocked from installing their applications when there are no technical limitations.

HOW TO FIX: Applications must not perform version checks for equality (== 5.1). If you need a specific feature, check whether the feature itself is available. If you need Windows XP, check for Windows XP or later (>= 5.1), this way, your detection code will continue to work on future versions of Windows. Driver installers and uninstall modules should never check the OS version.

WARNING: ERROR: Application failed to run under a higher Windows version.

IMPACT IF NOT FIXED: Customers are artificially blocked from running their applications when there are no technical limitations.

HOW TO FIX: Application installations must not perform version checks for equality (== 5.1). If you need a specific feature, check whether the feature itself is available. If you need Windows XP, check for Windows XP or later (>= 5.1), this way, your detection code will continue to work on future versions of Windows. Driver installers and uninstall modules should never check the OS version.

WARNING: ERROR: following files have requested an elevated run level, or are not manifested:

The toolkit reports all files with a shortcut (desktop or start menu) that request a run level higher than “asInvoker”.

• If any of the above files are used for install or uninstall, they can be ignored.
• If any of the above files are not an application’s main executable, they can be ignored.
• If any of the above files are requesting uiAccess, a waiver with business justification explaining the needed permission is required to pass this requirement.

IMPACT IF NOT FIXED: If an application only operates or installs when the user is an administrator, users are being forced to run applications with unnecessary elevated access. The fundamental problem is that, when users are always forced to run applications using elevated access tokens, deceptive or malicious code can easily modify the operating system, or worse, affect other users. It is nearly impossible to control a user that has a full administrator access token. Administrators can install applications and run any application or script that they wish. IT managers are always seeking ways to create "standard desktops" where users log on as standard users. Standard desktops greatly reduce help desk costs and reduce IT overhead. The difficulty and experience depends on how the file is manifested, and the permission level requested. The user experience is best for applications that follow UAC guidelines.

HOW TO FIX: Manifest files with the proper permissions needed. Adhere to the following UAC guidelines and best practices which are located HERE. A checklist for following UAC can be found HERE.

WARNING: ERROR: The application did not install any shortcuts. The following files did not respond to system restart requests:

Some applications as part of their first launch display EULAs or auto update prompts, registration forms, etc. If your application performs in this way, it could be falsely reported as non-compliant with the restart requirement.

• If any of the above files are reported for this reason, you should restart testing from a clean state (clean OS). This time around, before running the /postinstall phase, execute any run-once functionality in the application PRIOR to running the /postinstall phase of the toolkit.

IMPACT IF NOT FIXED: By failing to shutdown gracefully, customers could lose data when the OS finally forces a shutdown. It also slows the shutdown/reboot process, impacting performance perceptions.

HOW TO FIX: In a critical shutdown, applications that return FALSE to WM_QUERYENDSESSION will be sent WM_ENDSESSION and closed, while those that time out in response to WM_QUERYENDSESSION, will be terminated. By following these guidelines, you can ensure that your application will handle critical shutdowns gracefully:

• WM_QUERYENDSESSION with LPARAM = ENDSESSION_CLOSEAPP(0x1): GUI 19 applications must respond (TRUE) immediately in preparation for a restart
• WM_ENDSESSION with LPARAM = ENDSESSION_CLOSEAPP(0x1): Applications must return a 0 value within 30 seconds and shut down. At a minimum, applications should prepare by saving any user data and state information that is needed after a restart
• Console applications that receive CTRL_C_EVENT notification should shut down immediately. Drivers must not veto a system shutdown event

More information and guidance on requesting and responding to system shutdowns and the RestartManager is available HERE.

WARNING: ERROR: The following files have been scheduled to start with the OS when it is started in Safe Mode:

IMPACT IF NOT FIXED: Safe mode allows users to diagnose and troubleshoot Windows. Unless needed for basic operations of the system (for example, storage device drivers) or for diagnostic and recovery purposes (for example, anti-virus scanners), drivers and services must not be set to load in safe mode. They could make it more difficult to troubleshoot the OS.

HOW TO FIX: Remove your entries from the following registry keys:

• HKLM/System/CurrentControlSet/Control/SafeBoot/Minimal
• HKLM/System/CurrentControlSet/Control/SafeBoot/Network

Any application writing to these keys will require a waiver with business justification to pass this requirement.

WARNING: ERROR: Application did not pass multiuser session compliance check.

IMPACT IF NOT FIXED: The application’s installation might not be accessible or usable by multiple users.

HOW TO FIX: : Application installation should not store data files or settings to user specific data stores (User Profile, HKCU etc.). This would result in those settings and files being available only for the installing user. Installation should take care of machine-wide configuration and data files. Per-user files and settings should be created post-installation (either at user-login or first-run of the application) to ensure that files as well as settings are available to all users.

WARNING: ERROR: Application did not pass multiuser session compliance check.

IMPACT IF NOT FIXED: The application’s installation might not be accessible or usable by multiple users.

HOW TO FIX: : Application installation should not store data files or settings to user specific data stores (User Profile, HKCU etc.). This would result in those settings and files being available only for the installing user. Installation should take care of machine-wide configuration and data files. Per-user files and settings should be created post-installation (either at user-login or first-run of the application) to ensure that files as well as settings are available to all users.

WARNING: ERROR: The application did not install any shortcuts. Application invocation in multiple sessions did not pass.

IMPACT IF NOT FIXED: Multiple windows users might not be able to launch the application seamlessly in concurrent sessions.

HOW TO FIX: : The application must not block launching multiple instances of the application across concurrent sessions both locally or remotely. Applications must not depend on global mutexes or other named-objects to check or block multiple instances. If multiple instances per user need to be blocked, then per-user or per-session namespaces must be used for mutexes or other named-objects.

WARNING: ERROR: The application did not install any shortcuts. Application did not pass multiuser session compliance check.

IMPACT IF NOT FIXED: Windows users might not be able to run the application seamlessly in concurrent sessions.

HOW TO FIX: : The application must support running multiple instances of the application across concurrent sessions both locally or remotely. The application should not require administrative privileges during runtime. Moreover, data and settings must not be shared across users or stored at a location that is shared across users. User data must be isolated to the users profile.