QT Designer wont run
-
I've been using Qt along with Visual Studio 2017 for about a year now without any problems. I am trying to move over to a different computer, installed everything the same as I had on the other computer, but Qt Designer will not run. I get an error message that Qt Designer has stopped working with the option to close or debug. I've uninstalled and reinstalled and have also tried installing older versions but nothing helps. The new computer is a Lenovo ThinkPad running Windows 10 Enterprise 2016.
-
Hi and welcome to devnet,
What graphic card do you have on that machine ?
Can you run Qt Creator ? -
Hi. It's got an Intel HD Graphics 520. And no, Qt Creator also does not run.
-
I need to correct my previous post. Qt Creator does run fine. Just Qt Designer seems to be giving me a problem. I can open ui files in Qt Creator, but it fials if I try to open them with Qt Designer:
-
One more interesting thing I just stumbled across. I had installed an older version that is working on my other PC - vers 5.10.1. I uninstalled this and started installing the latest version. While the install was still going on, I was poking around in the Qt folders and happen to double click on designer.exe in C:\Qt\5.12.3\msvc2015_64\bin. It opened fine. I then tried to run designer.exe in some other folders such as C:\Qt\5.12.3\msvc2017\bin and they all failed. After the installation completed, I went back to C:\Qt\5.12.3\msvc2015_64\bin and tried to run designer.exe again and now it also failed. Looks like some file being added by the install is causing this to fail. When I run the installer am I selecting more than I should causing conflicting versions of files to be installed?
-
Did you modify your PATH environment variable ?
-
Yes I did modify the path, but that does not help.
I have noticed something I can not explain. If I run the MaintenanceTool and make a modification to the Qt installation, as it is running, if I keep trying to open Qt Designer, at some point it will run. Once running it will work fine. However, once MaintenanceTool is finished, if I close Qt Designer and try to reopen it, it will once again fail to run. There is a very limited window while MaintenaceTool is running when Qt Designer will open successfully. It seems to be right near the very end of the installation when the progress bar is indicating that is > 90% done. I first thought that the problem was due to a conflict with a file being installed. But by looking at the files that are being installed when I do this, I no longer think this is the case. Does MaintenanceTool make any other system changes such as registry entries, etc? Is it possible that at the end of the install process it is clearing out a registry entry which then allows me to run Qt Designer, but then it rewrites an registry entry that once again breaks it? I did try deleting some registry entries earlier based upon other error reports I found in the forum, but that did not help. I will search for additional entries later when I have time. Right now I do have Qt Designer running (using the above procedure) so I am going ahead with some development I need to get done.
-
Just in case, Qt Creator provides an editor based on Designer.
Can you check with a tool like Dependency Walker where Designer find its dependencies ?
On a side note, you should not modify your PATH environment variable system wide.
-
Thanks for your help with this. The Qt Creator editor is a good alternative. I did run Dependency Walker - long time since I have looked at the output from this and not sure what I am seeing right now, but I've pasted the an abreviated version of the output below (too long to paste the whole thing) if it tells you something. Thanks again.
| System Information |
| Search Order |
-
*
- Legend: F File E Error (path not valid) *
-
*
Side-by-Side components (Windows 2000/XP/2003/Vista/+)
[F ] c:\windows\winsxs\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.2938_none_c58b03c797c07d8c\COMCTL32.DLL
[F ] c:\windows\winsxs\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.2969_none_f678e0c2f2505d00\GDIPLUS.DLL
The system's "KnownDLLs" list
[F ] c:\windows\system32\ADVAPI32.DLL
[F ] c:\windows\system32\BCRYPTPRIMITIVES.DLL
[F ] c:\windows\system32\CFGMGR32.DLL
[F ] c:\windows\system32\CLBCATQ.DLL
[F ] c:\windows\system32\COMBASE.DLL
[F ] c:\windows\system32\COMCTL32.DLL
[F ] c:\windows\system32\COMDLG32.DLL
[F ] c:\windows\system32\COML2.DLL
[F ] c:\windows\system32\CRYPT32.DLL
[F ] c:\windows\system32\DIFXAPI.DLL
[F ] c:\windows\system32\GDI32.DLL
[F ] c:\windows\system32\GDI32FULL.DLL
[F ] c:\windows\system32\GDIPLUS.DLL
[F ] c:\windows\system32\IMAGEHLP.DLL
[F ] c:\windows\system32\IMM32.DLL
[F ] c:\windows\system32\KERNEL.APPCORE.DLL
[F ] c:\windows\system32\KERNEL32.DLL
[F ] c:\windows\system32\KERNELBASE.DLL
[F ] c:\windows\system32\LPK.DLL
[F ] c:\windows\system32\MSASN1.DLL
[F ] c:\windows\system32\MSCTF.DLL
[F ] c:\windows\system32\MSVCP_WIN.DLL
[F ] c:\windows\system32\MSVCRT.DLL
[F ] c:\windows\system32\NORMALIZ.DLL
[F ] c:\windows\system32\NSI.DLL
[F ] c:\windows\system32\NTDLL.DLL
[F ] c:\windows\system32\NTDLL.DLL
[F ] c:\windows\system32\OLE32.DLL
[F ] c:\windows\system32\OLEAUT32.DLL
[F ] c:\windows\system32\POWRPROF.DLL
[F ] c:\windows\system32\PROFAPI.DLL
[F ] c:\windows\system32\PSAPI.DLL
[F ] c:\windows\system32\RPCRT4.DLL
[F ] c:\windows\system32\SECHOST.DLL
[F ] c:\windows\system32\SETUPAPI.DLL
[F ] c:\windows\system32\SHCORE.DLL
[F ] c:\windows\system32\SHELL32.DLL
[F ] c:\windows\system32\SHLWAPI.DLL
[F ] c:\windows\system32\UCRTBASE.DLL
[F ] c:\windows\system32\USER32.DLL
[F ] c:\windows\system32\WIN32U.DLL
[F ] c:\windows\system32\WINDOWS.STORAGE.DLL
[F ] c:\windows\system32\WINTRUST.DLL
[F ] c:\windows\system32\WLDAP32.DLL
[F ] c:\windows\system32\WOW64.DLL
[F ] c:\windows\system32\WOW64CPU.DLL
[F ] c:\windows\system32\WOW64WIN.DLL
[F ] c:\windows\system32\WS2_32.DLL
The application directory
[ ] C:\Qt\5.12.3\msvc2015_64\bin
The 32-bit system directory
[ ] C:\Windows\system32
The 16-bit system directory (Windows NT/2000/XP/2003/Vista/+)
[ ] C:\Windows\system
The system's root OS directory
[ ] C:\Windows
The application's registered "App Paths" directories
The system's "PATH" environment variable directories
[ ] C:\Program Files\Microsoft MPI\Bin
[ ] C:\Windows\system32
[ ] C:\Windows
[ ] c:\Qt\5.12.3\bin\| Module Dependency Tree |
-
*
- Legend: F Forwarded Module ? Missing Module 6 64-bit Module *
-
D Delay Load Module ! Invalid Module *
-
* Dynamic Module E Import/Export Mismatch or Load Failure *
-
^ Duplicate Module *
-
*
[ 6] DESIGNER.EXE
[ 6] QT5DESIGNERCOMPONENTS.DLL
[ ^6] QT5DESIGNER.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5XML.DLL
[ ^6] QT5CORE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5DESIGNER.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5XML.DLL
[ ^6] QT5CORE.DLL
[ E ] MSVCP140.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-LOCALE-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-CONVERT-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-FILESYSTEM-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-TIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-ENVIRONMENT-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-UTILITY-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[DE ] CONCRT140.DLL
[ E ] MSVCP140.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STRING-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5PRINTSUPPORT.DLL
[ ^6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5CORE.DLL
[ E ] WINSPOOL.DRV
[ E ] COMDLG32.DLL
[ E ] GDI32.DLL
[ E ] USER32.DLL
[ E ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ E ] VCRUNTIME140.DLL
[ ^6] API-MS-WIN-CRT-STDIO-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-HEAP-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-MATH-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ ^6] API-MS-WIN-CRT-RUNTIME-L1-1-0.DLL
[FE ] UCRTBASE.DLL
[ 6] QT5WIDGETS.DLL
[ ^6] QT5GUI.DLL
[ ^6] QT5CORE.DLL
[ E ] UXTHEME.DLL
[ E ] MSVCRT.DLL
[ ? ] API-MS-WIN-CORE-LIBRARYLOADER-L1-2-0.DLL
[ E6] API-MS-WIN-CORE-SYNCH-L1-2-0.DLL
[FE ] KERNEL32.DLL
[FE6] API-MS-WIN-CORE-SYNCH-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-HEAP-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-ERRORHANDLING-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-PROCESSTHREADS-L1-1-2.DLL
[ ? ] API-MS-WIN-CORE-LOCALIZATION-L1-2-1.DLL
[ ? ] API-MS-WIN-CORE-DEBUG-L1-1-1.DLL
[ ^6] API-MS-WIN-CORE-HANDLE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-SYSINFO-L1-2-1.DLL
[ ? ] API-MS-WIN-CORE-LIBRARYLOADER-L1-2-2.DLL
[ ? ] API-MS-WIN-CORE-FILE-L1-2-1.DLL
[ ^6] API-MS-WIN-CORE-STRING-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ^6] API-MS-WIN-CORE-UTIL-L1-1-0.DLL
[FE ] KERNEL32.DLL
[FE ] NTDLL.DLL
[ ? ] API-MS-WIN-CORE-WINRT-ERROR-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-REGISTRY-L1-1-0.DLL
[ ? ] API-MS-WIN-SECURITY-BASE-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-HEAP-L2-1-0.DLL
[ ? ] API-MS-WIN-CORE-MEMORY-L1-1-2.DLL
[ ^6] API-MS-WIN-CORE-PROFILE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-STRING-L2-1-0.DLL
[ ? ] API-MS-WIN-CORE-PROCESSENVIRONMENT-L1-2-0.DLL
[ ^6] API-MS-WIN-CORE-TIMEZONE-L1-1-0.DLL
[FE ] KERNEL32.DLL
[ ? ] API-MS-WIN-CORE-SIDEBYSIDE-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-ATOMS-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-KERNEL32-LEGACY-L1-1-1.DLL
[ ? ] API-MS-WIN-CORE-STRING-OBSOLETE-L1-1-0.DLL
[ ? ] API-MS-WIN-CORE-SHLWAPI-OBSOLETE-L1-2-0.DLL
[ ? ] API-MS-WIN-CORE-LOCALIZATION-OBSOLETE-L1-3-0.DLL
[ E ] NTDLL.DLL
[ E ] GDI32.DLL
[ E ] USER32.DLL
[FE ] NTDLL.DLL
[ ? ] API-MS-WIN-CORE-DELAYLOAD-L1-1-1.DLL
[D? ] API-MS-WIN-CORE-COM-L1-1-1.DLL
[DE ] OLEAUT32.DLL
[D? ] API-MS-WIN-CORE-WINRT-STRING-L1-1-0.DLL
[D? ] API-MS-WIN-SECURITY-SDDL-L1-1-0.DLL
[DE ] CRYPTSP.DLL
[DE ] DWMAPI.DLL
[DE ] WINDOWSCODECS.DLL...
| Module List |*
-
*
- Legend: D Delay Load Module ? Missing Module 6 64-bit Module *
-
* Dynamic Module ! Invalid Module *
-
E Import/Export Mismatch or Load Failure *
-
*
Module File Time Stamp Link Time Stamp File Size Attr. Link Checksum Real Checksum CPU Subsystem Symbols Preferred Base Actual Base Virtual Size Load Order File Ver Product Ver Image Ver Linker Ver OS Ver Subsystem Ver
[ ? ] API-MS-WIN-CORE-APIQUERY-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-APPCOMPAT-L1-1-1.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-APPINIT-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-ATOMS-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-CALENDAR-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-L1-1-0 Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-L1-1-1.DLL Error opening file. The system cannot find the file specified (2).
[ ? ] API-MS-WIN-CORE-COM-MIDLPROXYSTUB-L1-1-0.DLL Error opening file. The system cannot find the file specified (2).| Log |*
Error: At least one required implicit or forwarded dependency was not found.
Error: At least one module has an unresolved import due to a missing export function in an implicitly dependent module.
Error: Modules with different CPU types were found.
Error: A circular dependency was detected.
Warning: At least one delay-load dependency module was not found.
Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module. -