Description of problem:
No Win32 binaries will execute. All files of type  'PE32 executable (GUI) Intel 80386, for MS Windows' fail with the error:  
wine: Bad EXE format for C:\Program Files (x86)\...

Version-Release number of selected component (if applicable):
1.7.22

How reproducible:
Consistent using RHEL 7 and CentOS 7

Steps to Reproduce:
1. Install wine (and dependencies) from the epel repository on CentOS7 or RHEL 7 AWS builds
2. execute winecfg
3. copy /usr/lib64/wine/fakedlls/mountmgr.sys to ${WINEPREFIX}/drive_c/windows/system32//drivers/mountmgr.sys (Per Bug ID 1177959 workaround)
4. winecfg - confirm drives show.
5. execute "wine ${WINEPREFIX}/drive_c/Program\ Files\ \(x86\)/AutoHotkey/AutoHotkeyU32.exe" 
6. Note error. 
7. Try it's 64bit version: execute "wine ${WINEPREFIX}/drive_c/Program\ Files\ \(x86\)/AutoHotkey/AutoHotkeyU64.exe"
8. note no error occurs. 

Actual results:
For example take this app.  A common keymapping tool:

AU3_Spy.exe:              PE32 executable (GUI) Intel 80386, for MS Windows
AutoHotkeyA32.exe:        PE32 executable (GUI) Intel 80386, for MS Windows
AutoHotkey.exe:           PE32+ executable (GUI) x86-64, for MS Windows
AutoHotkey_L_Install.exe: PE32 executable (GUI) Intel 80386, for MS Windows
AutoHotkeyU32.exe:        PE32 executable (GUI) Intel 80386, for MS Windows
AutoHotkeyU64.exe:        PE32+ executable (GUI) x86-64, for MS Windows

Note they proide both x86-64 64bit executables and 32bit 80386 executables. Only the PE32+ (x86-64) executables will run using 64bit restricted wine. All others report   
wine: Bad EXE format for C:\Program Files (x86)\AutoHotKey\AutoHotkeyU32.exe.
Even though they are valid executables.

Expected results:
The PE32 applications should execute just as the PE32+ ones do.

Additional info: A great many applications buitl in Windows only provide 32bit versions. The functionality is necessary in order for wine to be viable.