Did this article resolve your question/issue?



What is the prowin32.exe.manifest file?

« Go Back


TitleWhat is the prowin32.exe.manifest file?
URL NameP126075
Article Number000150027
EnvironmentProduct: OpenEdge
Version: All supported versions
OS: Windows
Question/Problem Description
What is the prowin32.exe.manifest file?

What is the prowin.exe.manifest file?

What is the prowc.exe.manifest file?

What does the *.exe.manifest file located in %DLC%\bin do?

Why does removing the prowin32.exe.manifest change some behavioral aspects of the COMBO-BOX widget?

Is there any loss in functionality that may result from the deletion of the prowin32.exe.manifest file?

How to achieve Basic application user-interface without applying Windows Basic Theme?

How to achieve Classic application user interface without applying Windows Classic Theme?

How to get the Windows XP look and feel?
Steps to Reproduce
Clarifying Information
With the .exe.manifest in place:
With .manifest

Without the .exe.manifest in place:
Without .manifest
Error Message
Defect/Enhancement Number
The .manifest file determines whether a Progress GUI client uses the Windows Themes interface or not.
  • prowin32.exe.manifest (32-bit GUI client) - first introduced in OpenEdge 10.1A.
  • prowin.exe.manifest (64-bit GUI client) - first introduced in OpenEdge 11.3.
  • prowc.exe.manifest (32-bit/64-bit WebClient) - first introduced in OpenEdge 10.1B (32-bit) and OpenEdge 11.4 (64-bit).
The .manifest is an XML file that tells Windows that the associated executable should use specific versions of one or more system components. In OpenEdge's case, the .manifest file tells Windows to use version 6 of the Microsoft Common Controls library. This library implements new versions of the basic controls (buttons, edit controls, combo-boxes, etc) which can be displayed with the Windows Themes look and feel. The behavior of the combo-box has changed in some small ways in this library.

The .manifest file is present by default. Customers wishing to revert to the basic or classic Windows look and feel can rename the file, e.g. %DLC%\bin\prowin32.exe.manifest. 

Removing or renaming the .manifest file reverts to version 5.82 of the Common Controls library causing Windows to use the original non-XP controls. 
If users are not using Windows Themes on a Windows system, then deleting or renaming the .manifest file results in no loss of functionality. 
References to other documentation:

Progress article(s):
000022414, How to package a .manifest file for Windows XP look and feel?
Last Modified Date5/28/2019 7:14 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.