-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
Wine-7.5 couldn’t start .exe file
I tried to execute some `setup.exe` file and it didn’t event started. When i run it in terminal i have this output:
Code: Select all
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.5 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
0080:err:x11settings:X11DRV_ChangeDisplaySettingsEx Failed to write L"\\\\.\\DISPLAY1" display settings to registry.
0080:err:system:NtUserChangeDisplaySettings Changing L"\\\\.\\DISPLAY1" display settings returned -3.
0080:err:explorer:initialize_display_settings Failed to initialize registry display settings for L"\\\\.\\DISPLAY1".
0118:err:module:load_wow64_ntdll failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.
Screenfetch output:
Code: Select all
/:-------------:\ krp@fedora
:-------------------:: OS: Fedora
:-----------/shhOHbmp---:\ Kernel: x86_64 Linux 5.16.9-200.rog.fc35.x86_64
/-----------omMMMNNNMMD ---: Uptime: 6h 29m
:-----------sMMMMNMNMP. ---: Packages: 3636
:-----------:MMMdP------- ---\ Shell: bash 5.1.8
,------------:MMMd-------- ---: Resolution: 1600x900
:------------:MMMd------- .---: DE: GNOME 41.4
:---- oNMMMMMMMMMNho .----: WM: Mutter
:-- .+shhhMMMmhhy++ .------/ WM Theme:
:- -------:MMMd--------------: GTK Theme: Adwaita-dark [GTK2/3]
:- --------/MMMd-------------; Icon Theme: Adwaita
:- ------/hMMMy------------: Font: Cantarell 11
:-- :dMNdhhdNMMNo------------; Disk: 1,7T / 2,1T (80%)
:---:sdNMMMMNds:------------: CPU: Intel Core i7-10750H @ 12x 5GHz [51.0°C]
:------:://:-------------:: GPU: NVIDIA GeForce RTX 2060
:---------------------:// RAM: 8399MiB / 15770MiB
Wine version:
Any idea what to do?
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
Re: Wine-7.5 couldn’t start .exe file
Post
by bigkrp »
Here output
Code: Select all
mingw32-wine-gecko.noarch 2.47.2-2.fc34 @fedora
mingw64-wine-gecko.noarch 2.47.2-2.fc34 @fedora
wine.x86_64 7.5-1.fc35 @updates
wine-alsa.i686 7.5-1.fc35 @updates
wine-alsa.x86_64 7.5-1.fc35 @updates
wine-arial-fonts.noarch 7.5-1.fc35 @updates
wine-cms.i686 7.5-1.fc35 @updates
wine-cms.x86_64 7.5-1.fc35 @updates
wine-common.noarch 7.5-1.fc35 @updates
wine-core.i686 7.5-1.fc35 @updates
wine-core.x86_64 7.5-1.fc35 @updates
wine-courier-fonts.noarch 7.5-1.fc35 @updates
wine-desktop.noarch 7.5-1.fc35 @updates
wine-dxvk.i686 1.10.1-1.fc35 @updates
wine-dxvk.x86_64 1.10.1-1.fc35 @updates
wine-dxvk-d3d9.i686 1.10.1-1.fc35 @updates
wine-dxvk-d3d9.x86_64 1.10.1-1.fc35 @updates
wine-dxvk-dxgi.i686 1.10.1-1.fc35 @updates
wine-dxvk-dxgi.x86_64 1.10.1-1.fc35 @updates
wine-filesystem.noarch 7.5-1.fc35 @updates
wine-fixedsys-fonts.noarch 7.5-1.fc35 @updates
wine-fonts.noarch 7.5-1.fc35 @updates
wine-ldap.i686 7.5-1.fc35 @updates
wine-ldap.x86_64 7.5-1.fc35 @updates
wine-marlett-fonts.noarch 7.5-1.fc35 @updates
wine-mono.noarch 7.1.1-1.fc35 @updates
wine-ms-sans-serif-fonts.noarch 7.5-1.fc35 @updates
wine-openal.i686 7.5-1.fc35 @updates
wine-openal.x86_64 7.5-1.fc35 @updates
wine-opencl.i686 7.5-1.fc35 @updates
wine-opencl.x86_64 7.5-1.fc35 @updates
wine-pulseaudio.i686 7.5-1.fc35 @updates
wine-pulseaudio.x86_64 7.5-1.fc35 @updates
wine-small-fonts.noarch 7.5-1.fc35 @updates
wine-symbol-fonts.noarch 7.5-1.fc35 @updates
wine-system-fonts.noarch 7.5-1.fc35 @updates
wine-systemd.noarch 7.5-1.fc35 @updates
wine-tahoma-fonts.noarch 7.5-1.fc35 @updates
wine-times-new-roman-fonts.noarch 7.5-1.fc35 @updates
wine-twain.i686 7.5-1.fc35 @updates
wine-twain.x86_64 7.5-1.fc35 @updates
wine-webdings-fonts.noarch 7.5-1.fc35 @updates
wine-wingdings-fonts.noarch 7.5-1.fc35 @updates
winetricks.noarch 20210825-1.fc35 @fedora
-
jkfloris
- Level 12
- Posts: 2903
- Joined: Thu Aug 14, 2014 10:10 am
Re: Wine-7.5 couldn’t start .exe file
Post
by jkfloris »
That looks good.
Back to your original question. Does the setup work in a clean wineprefix?
Code: Select all
WINEPREFIX=${HOME}/wine-test wine setup.exe
The winetricks warnings can probably be solved by updating the program.
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
Re: Wine-7.5 couldn’t start .exe file
Post
by bigkrp »
Not sure about your question.. so i did
Code: Select all
WINEPREFIX=${HOME}/wine-test wine setup.exe
And here output:
Code: Select all
wine: created the configuration directory '/home/krp/wine-test'
002c:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
002c:fixme:winediag:LdrInitializeThunk wine-staging 7.5 is a testing version containing experimental patches.
002c:fixme:winediag:LdrInitializeThunk Please mention your exact version when filing bug reports on winehq.org.
0048:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0050:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
MESA-INTEL: warning: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
MESA-INTEL: warning: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
0048:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0048:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0048:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0050:err:ole:StdMarshalImpl_MarshalInterface Failed to create ifstub, hr 0x80004002
0050:err:ole:CoMarshalInterface Failed to marshal the interface {6d5140c1-7436-11ce-8034-00aa006009fa}, hr 0x80004002
0050:err:ole:apartment_get_local_server_stream Failed: 0x80004002
0048:err:ole:start_rpcss Failed to open RpcSs service
0050:fixme:imm:ImeSetActiveContext (0x267050, 0): stub
0050:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000267050): stub
002c:fixme:imm:ImeSetActiveContext (0x2598d0, 1): stub
002c:fixme:imm:ImmReleaseContext (0000000000010054, 00000000002598D0): stub
0078:err:winedevice:ServiceMain Failed to load L"C:\\windows\\system32\\win32k.sys"
0078:err:winedevice:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgkrnl.sys"
0078:err:winedevice:ServiceMain Failed to load L"C:\\windows\\system32\\drivers\\dxgmms1.sys"
0088:fixme:file:NtLockFile I/O completion on lock not implemented yet
0088:fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0088:err:mscoree:LoadLibraryShim error reading registry key for installroot
0090:err:module:load_wow64_ntdll failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
0088:err:msi:execute_command unable to execute command 1359
0088:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
0088:fixme:msi:internal_ui_handler internal UI not implemented for message 0x0b000000 (UI level = 1)
00a0:fixme:font:freetype_set_outline_text_metrics failed to read full_nameW for font L"Material Icons Outlined"!
00a0:fixme:font:freetype_set_outline_text_metrics failed to read full_nameW for font L"Material Icons Round"!
00a0:fixme:font:freetype_set_outline_text_metrics failed to read full_nameW for font L"Material Icons Sharp"!
00a0:fixme:font:freetype_set_outline_text_metrics failed to read full_nameW for font L"Material Icons Two Tone"!
00a0:fixme:imm:ImeSetActiveContext (0x25b660, 1): stub
00a0:fixme:imm:ImmReleaseContext (000000000002007A, 000000000025B660): stub
wine: failed to open L"C:\\windows\\syswow64\\rundll32.exe": c0000135
wine: configuration in L"/home/krp/wine-test" has been updated.
0024:fixme:actctx:parse_depend_manifests Could not find dependent assembly L"Microsoft.Windows.Common-Controls" (6.0.0.0)
0134:err:module:load_wow64_ntdll failed to load L"\\??\\C:\\windows\\syswow64\\ntdll.dll" error c0000135
Application could not be started, or no application associated with the specified file.
ShellExecuteEx failed: Internal error.
Setup doesn’t work well(
-
bigkrp
- Level 2
- Posts: 10
- Joined: Sat Apr 23, 2022 9:21 am
Re: Wine-7.5 couldn’t start .exe file
Post
by bigkrp »
jkfloris wrote: ↑Wed May 11, 2022 11:11 am
It seems that Wine is failing to create a wineprefix (a «fake» Windows installation).
Can you reinstall Wine or use the Wine packages from WineHQ?
This helps me, thank you!
При попытке установить программу на вашем компьютере с Windows, Если вы видите “ShellExecuteEx failed” в сопровождении различных кодов, то этот пост поможет вам.
Сопутствующие коды ошибок могут быть: 2, 5, 67, 255, 1155, 1460, 8235, 2147221003, и т.д. Эта ошибка обычно возникает, если установщик требует прав администратора, файл установки был поврежден или существует конфликт приложений.
ShellExecuteEx — это функция ОС, которая выполняет операцию над указанным файлом. Если операция завершится неудачно, вы получите эту ошибку.
- Запустите исполняемый файл от имени администратора
- Повторно загрузите или переустановите программу
- Запустить Средство Проверки Системных Файлов
- Сброс звуков по умолчанию.
Давайте подробно рассмотрим эти методы.
Попробуйте запустить приложение от имени администратора
Запуск приложений с правами администратора. Даже если приложение не удается запустить, попробуйте переустановить приложение с правами администратора. Просто щелкните правой кнопкой мыши на файле установщика и нажмите кнопку Запуск от имени администратора.
Загрузите установщик еще раз, а затем установите повторно
Иногда, когда вы загружаете любое приложение для установки, вы возможно столкнулись с ситуацией, когда программа установки не будет работать и приложение не будет установлено. Это может произойти из-за поврежденного или файла установщика.
Попробуйте загрузить то же самое с официального сайта приложения или любого доверенного источника. Также можно отключить антивирус на время установки и далее добавить приложение в исключения антивируса ( Внимание!!, вы должны быть уверены, что в этом файле нет вирусов или он из надежного источника)
Здесь вы можете приобрести ключ лицензии Windows 10 Pro 2020. Вы сразу же получаете ваш собственный уникальный ключ активации. После ввода лицензионного ключа вы начинаете использовать лицензионную операционную систему без ограничений, а также получать последующие пакеты обновлений, выпускаемые Microsoft.
Запустите сканирование SFC
Запуск сканирования SFC делается для замены потенциально поврежденных системных файлов. Таким образом, если ошибка возникает из-за поврежденного системного файла, то следующие шаги должны помочь вам исправить ошибку.
SFC scan не только находит проблемный системный файл, но и исправляет его.
Нажмите Клавишу Win + X . Откроется меню быстрого доступа.
Нажмите на Windows PowerShell (администратор) . Если вместо PowerShell отображается Командная строка, выберите пункт Командная строка (администратор) .
Выполните команду: sfc /scannow
Подождите несколько секунд, так как требуется время для завершения сканирования.
Если проблема в этом, то ошибка должна быть решена.
Но если есть действительно большая проблема, то вы можете столкнуться с сообщением, говорящим: «Windows Resource Protection нашел поврежденные файлы, но не смог исправить».
Вам просто нужно перезагрузить машину в безопасном режиме и снова запустить вышеуказанную команду.
Сброс системных звуков по умолчанию
Вы можете подумать, что как сброс системного звука по умолчанию может решить системную ошибку, такую как “ShellExecuteEx”? Но некоторые пользователи сообщили, как этот шаг решил их проблему.
Откройте диалоговое окно Выполнить, нажав клавишу Win + R.
И введите mmsys.cpl нажмите Enter.
Нажмите на вкладку Звуки. Выберите «По умолчанию» в звуковой схеме.
Нажмите на кнопку Применить, а затем на кнопку ОК.
Recently, lots of Windows 10 users have reported that they are getting “shellexecuteex failed code 2” while installing .exe files. Since Windows is well-reputed in ruining the user experience, errors like these are now considered ‘Normal’. For Windows users, reinstalling Windows operating system is a common thing, and the cycle of installing and formatting the operating system never seems to end.
After receiving multiple messages from our visitors regarding the ‘shellexecuteex failed code 2’ error message, we have researched and found that the error occurs due to some bugs. The bug is fixed in the latest build of Windows OS, but, the problem is that the users who are using the pirated version of Windows OS won’t get the update.
So, for those users, we are going to discuss a few best methods that could fix the ‘shellexecuteex failed code 2’ in no-time. Since the main cause of the error message is yet to be found, users need to follow all methods to fix the shellexecuteex failed code 2 error message.
1. Scan your computer with Powerful security tool
Well, this is one of the first things which you need to do while dealing with errors. It’s worth to note that virus, malware, spyware, adware, etc. sometimes plays with the system files which can trigger different errors. So, before you make up your mind to follow the other methods, make sure to scan your computer. Even if the full system scan fails to fix the error message, it will eliminate the security threats. So, make sure to scan your system with security tools to fix the ‘shellexecuteex failed code 2’ error message.
2. Try running in Administrator mode
Well, if you are getting the error while installing programs, then you can try running the installer with Administrator privileges. If there’s something wrong with the permissions, then running the installer in Administrator mode will probably eliminate the ‘shellexecuteex failed code 2’ error message. Installing apps in Administrator mode is easy; users need to right-click on the installer and select the option ‘Run as administrator’. Some apps also require administrator privileges to install, so if this is what triggers the error, then it will be fixed.
3. Re-Download The Installer & Install
If you are getting the ‘shellexecuteex failed code 2’ error message while installing any app or game that you have just downloaded, then we recommend you to redownload the installer. There might be some fault in the installation file which is triggering the ‘shellexecuteex failed code 2’ error message. So, in such a scenario, users need to uninstall the app or traces of it and install it again. Also, make sure to run the installer in ‘Administrator mode’.
4. Revert the System Sounds To the default
Well, some users have reported that reverting the system sounds to the default has fixed the error message. The problem usually occurs when the module you are trying to install or use fails to handle the system sounds properly. So, if that was the issue, then you need to revert the system sounds to the default to fix the error message.
Step 1. First of all, press Windows Key + R to open the RUN dialog box.
Step 2. On the RUN dialog box, enter mmsys.cpl and hit enter.
Step 3. Next, you need to select the ‘Sounds’ tab and then select ‘Windows default’ under the Sound Scheme.
That’s it! You are done. Now just restart your computer to fix the shellexecuteex failed error message from Windows 10.
5. Run SFC Command
Well, the error message “shellexecuteex failed code 2” also occurs due to corrupted system files. So, if you are getting the error message due to corrupted system files, then you need to use the SFC command. The SFC Command on Windows will most probably fix all corrupted, missing or changed system files. Here’s how to use SFC command to fix shellexecuteex failed code 2 error message.
Step 1. First of all, type in CMD on the search menu and right-click on the command prompt. From the right-click menu, select ‘Command Prompt (Admin)’
Step 2. Now on the command prompt window, enter the command ‘sfc /scannnow’ and press enter.
Step 3. Now, wait for a few seconds until the scan completes. If you get an error ‘Windows Resource Protection found corrupt files but was unable to fix’, then run the same command in the Safe mode.
That’s it; you are done! This is how you can use the SFC command to fix “shellexecuteex failed code 2” from Windows 10.
6. System Repair
Well, if the SFC command has failed to fix the shellexecuteex failed code 2 error message, then you need to repair your system. However, you need to have a working Windows bootable DVD or USB to perform a system repair. The Windows System repair utility will fix various problems related to System 32 files, restore points, registry, etc.
Simply insert the Windows installation DVD or USB drive and reboot the computer. During the startup, you will be asked to press any key to boot from DVD or USB. Press any key and on the next page, select ‘Repair’. Now just follow the on-screen instruction to repair your system.
So, these are the best methods to fix ‘shellexecuteex failed code 2′ error message from Windows computer. If you know any other method to fix the error, let us know in the comment box below.’
Download Windows Speedup Tool to fix errors and make PC run faster
When you try to install a program on your Windows computer if you see a “ShellExecuteEx failed” accompanied by different codes, then this post will help you. The accompanying error codes could be 2, 5, 67, 255, 1155, 1460, 8235, 2147221003, etc. . This error usually occurs, if the installer requires administrator privileges, the setup file has become corrupted, or there is application conflict. ShellExecuteEx is an OS function that performs an operation on a specified file. If the operation fails, you get this error.
In this article, we will show you how to deal with ShellExecuteEx failed errors in Windows 11/10. You have the following options:
- Run the Exe file as administrator
- Re-download or reinstall the program
- Run System File Checker
- Reset Sounds to default
- Install or run the program in Clean Boot State.
Let us take a look at these methods in detail.
1] Try running the application as an administrator
Running applications with admin rights make applications run with more power. Even if the application fails to open up, try re-installing the application with admin rights. Just right click on the installer file and click on Run as administrator.
2] Download the installer again and then install
Sometimes when you download any application to install, you may have faced a situation where the setup won’t run and the app won’t install. This may happen due to a corrupt or defective installer file. Try downloading the same from the application’s official website or any trusted source.
3] Run SFC scan
You may know that running an SFC scan is done for replacing potentially corrupted system files. So, if the error is occurring due to a corrupted system file then the following steps should help you. SFC scan not only finds a problematic system file but also fixes it.
- Press Win Key + X. A Quick Access Menu will open up.
- Click on Windows PowerShell (Admin). If it shows Command Prompt instead of PowerShell then select Command Prompt (Admin).
- Run the command: sfc /scannow
- Wait for some moments as it takes time to complete the scan.
If everything goes right, the error should get resolved. But, if there is a really big problem then you may encounter a message saying: ‘Windows Resource Protection found corrupt files but was unable to fix’. You just need to restart your machine in Safe Mode and run the above command again.
4] Reset System Sounds to default
You may think that how resetting system sound to default can solve a system error like “ShellExecuteEx”? But some of the users have reported how this step solved their problem and it is worth mentioning, it may solve your problem too.
Open Run dialog box by pressing Win Key + R.
Type mmsys.cpl and press Enter.
Click on Sounds Tab. Select Windows Default in Sound Scheme.
Click on Apply and then on OK.
The problem should have gone by now.
5] Install or run the program in Clean Boot State
To avoid program conflicts, you may install or run the program in Clean Boot State and see if that helps you.
These are some of the methods you can try to resolve the error. Let us know if this helped.
Shubham is a PHP Developer, who is skilled in PHP, DOM, Angular, JavaScript, and C#. He loves talking about Microsoft technologies.
Recently, lots of Windows 10 users have reported that they are getting “shellexecuteex failed code 2” while installing .exe files. Since Windows is well-reputed in ruining the user experience, errors like these are now considered ‘Normal’. For Windows users, reinstalling Windows operating system is a common thing, and the cycle of installing and formatting the operating system never seems to end.
After receiving multiple messages from our visitors regarding the ‘shellexecuteex failed code 2’ error message, we have researched and found that the error occurs due to some bugs. The bug is fixed in the latest build of Windows OS, but, the problem is that the users who are using the pirated version of Windows OS won’t get the update.
So, for those users, we are going to discuss a few best methods that could fix the ‘shellexecuteex failed code 2’ in no-time. Since the main cause of the error message is yet to be found, users need to follow all methods to fix the shellexecuteex failed code 2 error message.
1. Scan your computer with Powerful security tool
Well, this is one of the first things which you need to do while dealing with errors. It’s worth to note that virus, malware, spyware, adware, etc. sometimes plays with the system files which can trigger different errors. So, before you make up your mind to follow the other methods, make sure to scan your computer. Even if the full system scan fails to fix the error message, it will eliminate the security threats. So, make sure to scan your system with security tools to fix the ‘shellexecuteex failed code 2’ error message.
2. Try running in Administrator mode
Well, if you are getting the error while installing programs, then you can try running the installer with Administrator privileges. If there’s something wrong with the permissions, then running the installer in Administrator mode will probably eliminate the ‘shellexecuteex failed code 2’ error message. Installing apps in Administrator mode is easy; users need to right-click on the installer and select the option ‘Run as administrator’. Some apps also require administrator privileges to install, so if this is what triggers the error, then it will be fixed.
3. Re-Download The Installer & Install
If you are getting the ‘shellexecuteex failed code 2’ error message while installing any app or game that you have just downloaded, then we recommend you to redownload the installer. There might be some fault in the installation file which is triggering the ‘shellexecuteex failed code 2’ error message. So, in such a scenario, users need to uninstall the app or traces of it and install it again. Also, make sure to run the installer in ‘Administrator mode’.
4. Revert the System Sounds To the default
Well, some users have reported that reverting the system sounds to the default has fixed the error message. The problem usually occurs when the module you are trying to install or use fails to handle the system sounds properly. So, if that was the issue, then you need to revert the system sounds to the default to fix the error message.
Step 1. First of all, press Windows Key + R to open the RUN dialog box.
Step 2. On the RUN dialog box, enter mmsys.cpl and hit enter.
Step 3. Next, you need to select the ‘Sounds’ tab and then select ‘Windows default’ under the Sound Scheme.
That’s it! You are done. Now just restart your computer to fix the shellexecuteex failed error message from Windows 10.
5. Run SFC Command
Well, the error message “shellexecuteex failed code 2” also occurs due to corrupted system files. So, if you are getting the error message due to corrupted system files, then you need to use the SFC command. The SFC Command on Windows will most probably fix all corrupted, missing or changed system files. Here’s how to use SFC command to fix shellexecuteex failed code 2 error message.
Step 1. First of all, type in CMD on the search menu and right-click on the command prompt. From the right-click menu, select ‘Command Prompt (Admin)’
Step 2. Now on the command prompt window, enter the command ‘sfc /scannnow’ and press enter.
Step 3. Now, wait for a few seconds until the scan completes. If you get an error ‘Windows Resource Protection found corrupt files but was unable to fix’, then run the same command in the Safe mode.
That’s it; you are done! This is how you can use the SFC command to fix “shellexecuteex failed code 2” from Windows 10.
6. System Repair
Well, if the SFC command has failed to fix the shellexecuteex failed code 2 error message, then you need to repair your system. However, you need to have a working Windows bootable DVD or USB to perform a system repair. The Windows System repair utility will fix various problems related to System 32 files, restore points, registry, etc.
Simply insert the Windows installation DVD or USB drive and reboot the computer. During the startup, you will be asked to press any key to boot from DVD or USB. Press any key and on the next page, select ‘Repair’. Now just follow the on-screen instruction to repair your system.
So, these are the best methods to fix ‘shellexecuteex failed code 2′ error message from Windows computer. If you know any other method to fix the error, let us know in the comment box below.’
If you want to find a solution to the “Shellexecuteex Failed” error, this post is what you need. It will show you some possible causes of the “Shellexecuteex Failed” error. In addition, it will also introduce you to several workable methods for this error. Now get these methods from MiniTool.
What Causes the “Shellexecuteex Failed” error on Windows?
Here are a few situations you might encounter:
- The application doesn’t have admin privileges
- System File Corruption
- Custom System sounds are crashing the app
- Application conflict
- Overprotective Local policy
If you want to find the methods for the “Shellexecuteex Failed” error, keep reading.
Method 1: Run the Application as Administrator
If you meet a “Shellexecuteex Failed” error when you open or install an application, it is likely to cause problems due to an unexpected application shutdown or installation of an executable because it does not have administrator access.
The following part will show you how to run an application as an administrator.
Step 1: Right-click on the application that is triggering the error, and select Properties.
Step 2: Select the Compatibility tab and check Run this program as administrator under the Settings section. Click Apply.
Step 3: Run the application again and see if the “Shellexecuteex Failed” error is fixed.
Method 2: Run DISM and SFC Scans
In some cases, the “Shellexecuteex Failure” error occurs because the installation could not be completed due to some type of system file corruption.
Follow the steps below to fix this error.
Step 1: Press Windows + R keys to open the Run dialog box. Type cmd and press Ctrl + Shift + Enter to run Command Prompt as an administrator.
Step 2: Type sfc /scannow and press Enter to perform an SFC scan.
Tip: Do not interfere with the window until this process is complete. Interrupting this operation may result in more logical errors that are more difficult to fix.
Step 3: After the scan is complete, restart the computer and wait for the next boot to complete. When the operating system is fully loaded, follow Step 1 to open Command Prompt again.
Step 4: Execute the commands: Dism.exe /online /cleanup-image /scanhealth and Dism.exe /online /cleanup-image /restorehealth to perform a DISM scan.
Tip: Before starting this process, make sure your Internet connection is stable.
Step 5: After the DISM scan is complete, restart the computer to see if the “Shellexecuteex Failed” error is fixed.
Method 3: Revert the System Sounds to the Default
In this case, you also fix the issue by resetting all Windows sounds to the default.
Step 1: Press Windows + R keys to open the Run dialog box. Type mmsys.cpl and click OK to open the Sound screen.
Step 2: Select the Sounds tab and then change the Sound Scheme to Windows Default. Click Apply and then click OK.
Step 3: Restart your computer to see if the “Shellexecuteex Failed” error disappears.
Method 4: Perform a Clean Boot
If the errors haven’t been fully resolved so far, you may be experiencing a “Shellexecuteex failure” error due to some kind of third-party conflict. Many potential applications could conflict with the ones that the application that is displaying the error, so your best approach to the problem is to configure your computer to start with a clean boot.
Step 1: Press Windows + R keys to open the Run dialog box. Type mscofig and click OK to open the System Configuration menu.
Step 2: Click the Services tab and then check Hide all Microsoft Services.
Step 3: Click Disable all to prevent all third party services from being started the next time your computer starts.
Step 4: Select the Startup tab and click Open Task Manager.
Step 5: Select each startup service systematically and then click Disable. This step ensures that no startup services are invoked the next time the system starts.
Step 6: Restart the computer to see if the error is still existing. If the error no longer occurs, complete the installation, then reverse engineer the steps above and re-enable the previously disabled services.
Method 5: Adjust the “Only elevate executables” Policy
In cases where the problem is caused by an improperly signed executable, in order to avoid this particular problem, you can adjust one Group policy named Only elevate executables that are signed and validated.
Step 1: Press Windows + R keys to open the Run dialog box. Type gpedit.msc and press Ctrl + Shift + Enter to open Local Group Policy Editor with admin privileges.
Step 2: Navigate to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options. Double-click User Account Control: Only elevate executables that are signed and validated.
Step 3: Select the Local Security Setting tab and then ensure the policy is set to Disabled. Click Apply and then click OK.
Step 4: Restart the computer to see if the issue is fixed.
Method 6: Perform a Clean Install
If none of the above methods can solve this problem, you’re probably dealing with an underlying corruption problem that cannot be fixed by conventional means. You can only solve this problem by resetting each Windows component.
The quickest way is to perform a clean install. This process will cause you to lose any personal data.
The most effective way to take longer is to install the fix – in place install. During this process, you can retain all personal effects.
Bottom Line
In conclusion, this post has shown you some possible reasons for the “Shellexecuteex Failed” error. Meanwhile, it also shows you some useful methods to fix this problem. If you encounter this issue, you can try these methods.






















