Not able to run on this version of windows

Not able to run on this version of windows missing function winsta winstationconnectw

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

When i try to open Process Explorer it Always says This:

Not Able To run on this version of windows:

missing function: winsta!WinStationConnectW

Not Able To run on this version of windows:

missing function: winsta!WinStationShadow

Not Able To run on this version of windows:

missing function: winsta!WinStationGetProcessSid

and for end just Sysinternals Process Explorer Has Stop

Procexp.exe

ver: 16.32.0.0

Windows 7 ultimate SP1 32 bits

i try to run it as Administrador and Same problem always

anyone know what to do:D Pls TY

Источник

Not able to run on this version of windows missing function winsta winstationconnectw

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

When i try to open Process Explorer it Always says This:

Not Able To run on this version of windows:

missing function: winsta!WinStationConnectW

Not Able To run on this version of windows:

missing function: winsta!WinStationShadow

Not Able To run on this version of windows:

missing function: winsta!WinStationGetProcessSid

and for end just Sysinternals Process Explorer Has Stop

Procexp.exe

ver: 16.32.0.0

Windows 7 ultimate SP1 32 bits

i try to run it as Administrador and Same problem always

anyone know what to do:D Pls TY

Источник

Not able to run on this version of windows missing function winsta winstationconnectw

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

When i try to open Process Explorer it Always says This:

Not Able To run on this version of windows:

missing function: winsta!WinStationConnectW

Not Able To run on this version of windows:

missing function: winsta!WinStationShadow

Not Able To run on this version of windows:

missing function: winsta!WinStationGetProcessSid

and for end just Sysinternals Process Explorer Has Stop

Procexp.exe

ver: 16.32.0.0

Windows 7 ultimate SP1 32 bits

i try to run it as Administrador and Same problem always

anyone know what to do:D Pls TY

Источник

Not able to run on this version of windows missing function winsta winstationconnectw

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

When i try to open Process Explorer it Always says This:

Not Able To run on this version of windows:

missing function: winsta!WinStationConnectW

Not Able To run on this version of windows:

missing function: winsta!WinStationShadow

Not Able To run on this version of windows:

missing function: winsta!WinStationGetProcessSid

and for end just Sysinternals Process Explorer Has Stop

Procexp.exe

ver: 16.32.0.0

Windows 7 ultimate SP1 32 bits

i try to run it as Administrador and Same problem always

anyone know what to do:D Pls TY

Источник

Not able to run on this version of windows missing function winsta winstationconnectw

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

General discussion

When i try to open Process Explorer it Always says This:

Not Able To run on this version of windows:

missing function: winsta!WinStationConnectW

Not Able To run on this version of windows:

missing function: winsta!WinStationShadow

Not Able To run on this version of windows:

missing function: winsta!WinStationGetProcessSid

and for end just Sysinternals Process Explorer Has Stop

Procexp.exe

ver: 16.32.0.0

Windows 7 ultimate SP1 32 bits

i try to run it as Administrador and Same problem always

anyone know what to do:D Pls TY

Источник

Process explorer not able to run on this version of windows

Профиль | Отправить PM | Цитировать

Изображения

	2019-09-13_212355.png
(9.8 Kb, 9 просмотров)
	2019-09-13_214709.png
(22.0 Kb, 6 просмотров)
	2019-09-13_214719.png
(26.9 Kb, 5 просмотров)
	2019-09-13_214740.png
(44.6 Kb, 4 просмотров)
	2019-09-13_214802.png
(45.2 Kb, 5 просмотров)

Скачал PE с сайта майкрософт, чтобы посмотреть на процессы в системе, а программа не запускается с несколькими ошибками. Ранее не наблюдал таких проблем.

Как починить, может быть что вирус заблокировал возможность запуска этой программы?

Сообщения: 51905
Благодарности: 14929

Если же вы забыли свой пароль на форуме, то воспользуйтесь данной ссылкой для восстановления пароля.

Сообщения: 51905
Благодарности: 14929

» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>

Сообщения: 26986
Благодарности: 7874

Сообщения: 51905
Благодарности: 14929

» width=»100%» style=»BORDER-RIGHT: #719bd9 1px solid; BORDER-LEFT: #719bd9 1px solid; BORDER-BOTTOM: #719bd9 1px solid» cellpadding=»6″ cellspacing=»0″ border=»0″>

Сообщения: 51905
Благодарности: 14929

Дополнительно выложите файл
C:UsersadmsAppDataLocalCrashDumpsprocexp64.exe.6360.dmp

Process Explorer v16.30

Not able to run on this version of Windows:
Missing function: winsta!WinStationConnectW

Not able to run on this version of Windows:
Missing function: winsta!WinStationShadow

Not able to run on this version of Windows:
Missing function: winsta!WinStationGetProcessSid

Answers

What version exactly are you running of Windows 7? is it by any chance a Home version?

The function you are reporting are generally available on windows 7..

I’m running a Pro and it works fine..

Can you give more details?

What version exactly are you running of Windows 7? is it by any chance a Home version?

The function you are reporting are generally available on windows 7..

I’m running a Pro and it works fine..

Can you give more details?

Is Win 7 profesional

The version 16.26 work fine

but the last version no

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Crear proceso
ID del hilo : 2420
Direccion de memoria:
Nombre de archivo :
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 00000000`77120000
Nombre de archivo : C:WindowsSYSTEM32ntdll.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 00000000`76f00000
Nombre de archivo : C:Windowssystem32kernel32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd1c0000
Nombre de archivo : C:Windowssystem32KERNELBASE.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd740000
Nombre de archivo : C:Windowssystem32SHLWAPI.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd6d0000
Nombre de archivo : C:Windowssystem32GDI32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 00000000`77020000
Nombre de archivo : C:Windowssystem32USER32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`feaf0000
Nombre de archivo : C:Windowssystem32LPK.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fe580000
Nombre de archivo : C:Windowssystem32USP10.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd630000
Nombre de archivo : C:Windowssystem32msvcrt.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`faf60000
Nombre de archivo : C:Windowssystem32IPHLPAPI.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fe9d0000
Nombre de archivo : C:Windowssystem32NSI.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fb040000
Nombre de archivo : C:Windowssystem32WINNSI.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd460000
Nombre de archivo : C:Windowssystem32RPCRT4.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`ff3e0000
Nombre de archivo : C:Windowssystem32WS2_32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f9040000
Nombre de archivo : C:Windowssystem32MPR.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fb920000
Nombre de archivo : C:WindowsWinSxSamd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9acCOMCTL32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fc1d0000
Nombre de archivo : C:Windowssystem32VERSION.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`facd0000
Nombre de archivo : C:Windowssystem32credui.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fef70000
Nombre de archivo : C:Windowssystem32SETUPAPI.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd230000
Nombre de archivo : C:Windowssystem32CFGMGR32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`feb00000
Nombre de archivo : C:Windowssystem32ADVAPI32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd440000
Nombre de archivo : C:WindowsSYSTEM32sechost.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fee90000
Nombre de archivo : C:Windowssystem32OLEAUT32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`ff1b0000
Nombre de archivo : C:Windowssystem32ole32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd270000
Nombre de archivo : C:Windowssystem32DEVOBJ.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd290000
Nombre de archivo : C:Windowssystem32CRYPT32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd110000
Nombre de archivo : C:Windowssystem32MSASN1.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f7610000
Nombre de archivo : C:Windowssystem32ACLUI.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd7f0000
Nombre de archivo : C:Windowssystem32SHELL32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f9590000
Nombre de archivo : C:Windowssystem32NTDSAPI.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fc0f0000
Nombre de archivo : C:Windowssystem32POWRPROF.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fae40000
Nombre de archivo : C:Windowssystem32WTSAPI32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fb870000
Nombre de archivo : C:Windowssystem32UxTheme.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd590000
Nombre de archivo : C:Windowssystem32COMDLG32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f9f60000
Nombre de archivo : C:Windowssystem32WINHTTP.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f9cf0000
Nombre de archivo : C:Windowssystem32webio.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 00000000`772f0000
Nombre de archivo : C:Windowssystem32PSAPI.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fd7c0000
Nombre de archivo : C:Windowssystem32IMM32.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fe9e0000
Nombre de archivo : C:Windowssystem32MSCTF.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f7600000
Nombre de archivo : C:Windowssystem32api-ms-win-core-synch-l1-2-0.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fb490000
Nombre de archivo : C:Windowssystem32ntmarta.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`ff150000
Nombre de archivo : C:Windowssystem32WLDAP32.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fcfa0000
Nombre de archivo : C:Windowssystem32CRYPTBASE.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Crear hilo
ID del hilo : 4788
Direccion de memoria: 00000000`77217ec0
Nombre de archivo :
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:00.000
Tipo de evento : Cerrar hilo
ID del hilo : 4788
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de salida: 0x00000000
==================================================

==================================================
Hora del evento : 00:00:08.379
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6ed0000
Nombre de archivo : C:Windowssystem32dbghelp.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:08.386
Tipo de evento : Crear hilo
ID del hilo : 4860
Direccion de memoria: 00000000`7713aec0
Nombre de archivo :
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.040
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6c10000
Nombre de archivo : C:Windowssystem32mscoree.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.042
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6b70000
Nombre de archivo : C:WindowsMicrosoft.NETFramework64v4.0.30319mscoreei.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.049
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6b40000
Nombre de archivo : C:WindowsMicrosoft.NETFramework64v4.0.30319CorperfmonExt.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.050
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f2960000
Nombre de archivo : C:Windowssystem32MSVCR120_CLR0400.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.052
Tipo de evento : Crear hilo
ID del hilo : 1264
Direccion de memoria: 000007fe`f6b4beb0
Nombre de archivo :
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.067
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6b30000
Nombre de archivo : C:Windowssystem32netfxperf.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.074
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6ae0000
Nombre de archivo : C:WindowsMicrosoft.NETFramework64v4.0.30319perfcounter.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.076
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f6a40000
Nombre de archivo : C:Windowssystem32pdh.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.076
Tipo de evento : Excepcion
ID del hilo : 2420
Direccion de memoria: 000007fe`fd1ca49d
Nombre de archivo :
Mas informacion : Codigo de excepcion: 0x000006ba
==================================================

==================================================
Hora del evento : 00:00:09.183
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fe930000
Nombre de archivo : C:Windowssystem32CLBCatQ.DLL
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.185
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fa110000
Nombre de archivo : C:Windowssystem32taskschd.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.186
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fcf10000
Nombre de archivo : C:Windowssystem32SspiCli.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.187
Tipo de evento : Excepcion
ID del hilo : 2420
Direccion de memoria: 000007fe`fd1ca49d
Nombre de archivo :
Mas informacion : Codigo de excepcion: 0x000006d9
==================================================

==================================================
Hora del evento : 00:00:09.189
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`f9d60000
Nombre de archivo : C:WindowsSystem32mstask.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.191
Tipo de evento : Carga DLL
ID del hilo : 2420
Direccion de memoria: 000007fe`fc650000
Nombre de archivo : C:Windowssystem32WINSTA.dll
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.194
Tipo de evento : Excepcion
ID del hilo : 2420
Direccion de memoria: 000007fe`fd1ca49d
Nombre de archivo :
Mas informacion : Codigo de excepcion: 0x000006ba
==================================================

==================================================
Hora del evento : 00:00:09.268
Tipo de evento : Crear hilo
ID del hilo : 1412
Direccion de memoria: 00000001`3f9ec8d4
Nombre de archivo :
Mas informacion :
==================================================

==================================================
Hora del evento : 00:00:09.269
Tipo de evento : Excepcion
ID del hilo : 2420
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de excepcion: 0xc000041d
==================================================

==================================================
Hora del evento : 00:00:09.269
Tipo de evento : Cerrar hilo
ID del hilo : 2420
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de salida: 0xc000041d
==================================================

==================================================
Hora del evento : 00:00:09.269
Tipo de evento : Cerrar hilo
ID del hilo : 1264
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de salida: 0xc000041d
==================================================

==================================================
Hora del evento : 00:00:09.271
Tipo de evento : Cerrar hilo
ID del hilo : 4860
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de salida: 0xc000041d
==================================================

==================================================
Hora del evento : 00:00:09.271
Tipo de evento : Cerrar proceso
ID del hilo : 1412
Direccion de memoria:
Nombre de archivo :
Mas informacion : Codigo de salida: 0xc000041d
==================================================

you are getting an Access Denied on something..

Also the exit code is really strange:

Get a ProcMon trace while loading Process Explorer and share it

Hmmm I just tried it on the same Windows version and it worked fine for me. Sounds like it might be environmental.

In addition to other suggestions, could you tell me.

2) Is there an application crash error (Event ID 1000) in the event log to indicate a crash? And if so was a memory dump created?

3). Was this running with admin privileges?

I have the same problem with Process Explorer 16.30 on Windows 7×86 Pro, Windows 7×64 Pro, Windows Server 2008×64 R2. All these systems are VM on VMWare Workstation 15.5.0.

Just run procexp.exe as usual application

2) Is there an application crash error (Event ID 1000) in the event log to indicate a crash? And if so was a memory dump created?

Memory dump was not created.

3) Was this running with admin privileges?

Get a ProcMon trace while loading Process Explorer and share it

Here is zip-file with ProcMon trace:

looks like it goes in exception after calling AddLocalAlternateComputerNameW..

wer can generate a dump if properly cofigured.

Actually it wrote the report under:
C:ProgramDataMicrosoftWindowsWERReportArchiveAppCrash_procexp.exe_1b2b625c3275e0b57e67dd990b7ac9116689e51_084d8d50Report.wer

Add these registry keys to collect a dump after a crash:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsWindows Error ReportingLocalDumps

DumpFolder REG_EXPAND_SZ %LOCALAPPDATA%CrashDumps

DumpCount REG_DWORD 10

DumpType REG_DWORD 2

looks like it goes in exception after calling AddLocalAlternateComputerNameW..

wer can generate a dump if properly cofigured.

Actually it wrote the report under:
C:ProgramDataMicrosoftWindowsWERReportArchiveAppCrash_procexp.exe_1b2b625c3275e0b57e67dd990b7ac9116689e51_084d8d50Report.wer

Add these registry keys to collect a dump after a crash:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsWindows Error ReportingLocalDumps

DumpFolder REG_EXPAND_SZ %LOCALAPPDATA%CrashDumps

DumpCount REG_DWORD 10

DumpType REG_DWORD 2

Here is dmp and wer files for procexp.exe:

We need help from MarkC here, because without symbols I’m a little bit lost..

The exception is an Access Violation

DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT

And these are the thread executing..

1 thread [stats]: 1
77bc70b4 ntdll!KiFastSystemCallRet
77bc6a04 ntdll!NtWaitForMultipleObjects+0xc
77bafe3b ntdll!TppWaiterpThread+0x33d
77953c45 kernel32!BaseThreadInitThunk+0xe
77be37f5 ntdll!__RtlUserThreadStart+0x70
77be37c8 ntdll!_RtlUserThreadStart+0x1b

1 thread [stats]: 2
77bc70b4 ntdll!KiFastSystemCallRet
77bc6a04 ntdll!NtWaitForMultipleObjects+0xc
75e369dc KERNELBASE!WaitForMultipleObjectsEx+0x100
7794bc8e kernel32!WaitForMultipleObjectsExImplementation+0xe0
7794bcfc kernel32!WaitForMultipleObjects+0x18
6fae1c7b CorperfmonExt!HandlerAuxThreadProc+0x55
77953c45 kernel32!BaseThreadInitThunk+0xe
77be37f5 ntdll!__RtlUserThreadStart+0x70
77be37c8 ntdll!_RtlUserThreadStart+0x1b

1 thread [stats]: 3
77bc70b4 ntdll!KiFastSystemCallRet
77bc6a24 ntdll!ZwWaitForSingleObject+0xc
75e3179c KERNELBASE!WaitForSingleObjectEx+0x98
7794baf3 kernel32!WaitForSingleObjectExImplementation+0x75
7794baa2 kernel32!WaitForSingleObject+0x12
00adf6b9 procexp+0x6f6b9
00b17885 procexp+0xa7885
77953c45 kernel32!BaseThreadInitThunk+0xe
77be37f5 ntdll!__RtlUserThreadStart+0x70
77be37c8 ntdll!_RtlUserThreadStart+0x1b

1 thread [stats]: 4
77bc70b4 ntdll!KiFastSystemCallRet
77bc57d4 ntdll!NtDelayExecution+0xc
75e31876 KERNELBASE!SleepEx+0x65
75e31818 KERNELBASE!Sleep+0xf
7797e72d kernel32!WerpReportFault+0x3f
7795ef30 kernel32!BasepReportFault+0x20
7795eeaa kernel32!UnhandledExceptionFilter+0x1af
77bf7f1a ntdll!__RtlUserThreadStart+0x62
77b9e304 ntdll!_EH4_CallFilterFunc+0x12
77b9e18c ntdll!_except_handler4+0x8e
77bc71b9 ntdll!ExecuteHandler2+0x26
77bc718b ntdll!ExecuteHandler+0x24
77b9f96f ntdll!RtlDispatchException+0x127
77bc7017 ntdll!KiUserExceptionDispatcher+0xf
00000000 0x0
00a9df39 procexp+0x2df39
00a775c1 procexp+0x75c1
00a74850 procexp+0x4850
00a832a3 procexp+0x132a3
00a82ce8 procexp+0x12ce8
00a7d263 procexp+0xd263
00a75146 procexp+0x5146
77953c45 kernel32!BaseThreadInitThunk+0xe
77be37f5 ntdll!__RtlUserThreadStart+0x70
77be37c8 ntdll!_RtlUserThreadStart+0x1b

5 stack(s) with 5 threads displayed (5 Total threads)

The interesting thing is the Software_NX_Fault.. On a machine with Data Execution Prevention (DEP) enabled, an attempt by software to execute non-executable code will cause it to crash.

Do you have DEP enabled on your machine?? Procexp should not crash ion any case, but just to «mitigate» the problem now you can try disabling DEP..

Other possible cause is corrupted memory.. one of your memory stick is corrupted and should be changed.. If you have some spare stick to try you can change them and see what happens..

Let’s see if MarkC can shed some more light on this..

Источник

Видео

Источник

Другие темы раздела
Windows 7 Фризит онлаин трансляция (просмотр) в 1080p https://www.cyberforum.ru/ windows7/ thread2505199.html Всем доброго вечера. Не уверен на счет правильного выбора темы, если что прошу перенести в соответствующую. Недавно переустановил винду. Накатил дрова, все как обычно. Но при просмотре твитч или…	Windows 7 Клонирование дисков Добрый день. Имею HDD, на нем при установке Win7 создалось 2 раздела — системный 100 мгб (24 мгб использовано и 76 мгб свободно) и второй раздел. Клонирую (а также восстанавливаюсь из копии,…
Windows 7 Отсутсвие звука в Windows 7 уже 2й день маюсь, шаманю, все без результатов. Сперва думал конфликт оборужования в диспечере задач было 2 желтых треугольника, их исправили(использовал форум): Pci- контролер Simple Communications… https://www.cyberforum.ru/ windows7/ thread2504484.html	Windows 7 Черный прямоугольник в трее В Windows каждый раз при загрузки операционной системы появляется такой вот черный прямоугольник на месте кнопки «свернуть все окна» потом, при запуске браузера или иных приложений он исчезает. Что… https://www.cyberforum.ru/ windows7/ thread2504396.html
Windows 7 WIn7 загружается только «на горячую» после установки Доброго всем дня! Подскажите(кто сталкивался может) куда еще копать и что смотреть, проблема такова: При установке ОС на ПК система загружается и стартует без сбоев и проблем, работает так-же…	Windows 7 Ошибка Win32 https://www.cyberforum.ru/ windows7/ thread2503495.html Тут такая проблема, после компиляции программы в Microsoft Visual Studio 19, высвечивается ошибка: — Не удалось запустить программу «…Hazel.dll» — «…Hazel.dll» не является допустимым…
Windows 7 Пропадают системные значки на панели задач, в настройках они неактивны https://www.cyberforum.ru/ windows7/ thread2503159.html Здравствуйте. Операционная система Windows7 SP1 64bit. Компьютер настольный, домашний. Система не переустанавливалась около трёх лет. Стали пропадать системные значки громкости и сети на панели…	Проблема с установкой Windows 7 Windows 7 Здрасьте, решил установить на свой компухтер Windows 7. Но проблема то в том, что когда я загружаюсь с флешки, идет процесс выгрузки файлов для инсталлера. Но когда появляется окно с выбором языка…
Windows 7 Распознать сеть как домашняя в Windows 7 Распознать сеть как «домашняя» в Windows 7? У меня все сети по умолчанию распознаются как общественные. Одна сеть — интернет — то есть выход по модему в интернет. Другая сеть одноранговая по… https://www.cyberforum.ru/ windows7/ thread2502816.html	Windows 7 Windows 7 и G-Sync Всем доброго времени суток. Не давно приобрёл видеокарту и монитор которые поддерживают G-Sync, но когда начал копаться в настройках NVIDIA то не обнаружил функции G-Sync вообще (в настройках… https://www.cyberforum.ru/ windows7/ thread2502790.html
Windows 7 Периодически не включается тачпад Здравствуйте. После переустановки W7 на нетбуке Asus eee1001px, при включении нетбука часто не включается тачпад и не работает горячая клавиша включения тачпада, а только после перезагрузок. Драйвера…	Windows 7 Не запускается винда https://www.cyberforum.ru/ windows7/ thread2502227.html В общем, после некорректного завершения работы винда перестала запускаться. Точнее, она не может зайти под моим профилем, поэтому создаёт временный. Все варианты решения, которые нашёл, мне не…

Read this article to learn how to fix the problem with running an application on PC, and we will find out why this error appears and how to solve the problem.

The core of the problem

On the Internet, there are lots of websites offering to install various applications and programs. At an early stage, Windows 10 operating system can detect and warn the user of possible issues, or even block a harmful application or program at once.

For this purpose, Microsoft has improved greatly the built-in defense component, SmartScreen. Its main task is to protect the user from apps provided by questionable developers. SmartScreen helps to reveal any previously detected malware, applications or websites created for malicious purposes, and takes informed decisions on blocking their access, download or use on your personal computer or another computing device.

At the first stage, SmartScreen analyzes all applications, programs and webpages for any suspicious activities. The next step will be to compare suspicious apps and webpages with the list of programs and websites recognized to be harmful. In case of a coincidence, SmartScreen will block download or installation for such a program, and display a corresponding notification for the user.

Obviously, SmartScreen is quite a useful feature in Windows 10 and using it seems absolutely justified. However, frequent error messages or warning notifications displayed while you are working with an application or website that you trust can become quite irritating. In that case, SmartScreen is easy to disable – if you know the app we are talking about is absolutely safe.

This security feature can display quite a number of various warnings and error messages, but most of these can be sorted out on your own. Mostly, these are issues related to providing additional permissions or signing in to an account with administrator’s rights.

Still, cases when you see a SmartScreen message saying This app can’t run on your PC are totally different. Such messages only suggest that you contact the program’s developer for advice – and that’s all. Also, you can face such messages when apps that used to run seamlessly on your computer, suddenly can’t start, for no evident reason. Yet don’t worry: even if you see the error This app can’t run on your PC in Windows 10, here’s what you can do.

The error This app can’t run on your PC

If you see such a message, it means there is a compatibility error. The application you are trying to install is incompatible with your operating system, Windows 10. You may also encounter this error if the application requires special permissions to run – and the current user account lacks them. This error only appears when you are trying to install an application, and never does when you start one. If an application is already installed to your computer, starting it will never trigger this error. There are two ways to fix it.

Use your account with administrator rights

When you see this error message, it might be due to your signing in to an account which doesn’t have administrator rights. To exclude this one out, check the account you are using now. If the current account is not the administrator’s one, switch to that account, and try installing the application again. If this method doesn’t work, try another one on the list.

32-bit or 64-bit application

If you’re using the 32-bit version of Windows 10 and trying to run a 64-bit version of the program, the error should have been expected. Similarly, if you’re trying to install a 32-bit program onto a 64-bit version of Windows 10, this error may also take place. If the problem comes from bitness, there’s only one solution – you’ve got to find the proper version of the necessary application and install it.

Disable SmartScreen in Windows 10

Sometimes, the error This app can’t run on your PC may be false. That’s why if the advice I have given you in this article didn’t help you and you still face this error, and you still need to run this app despite the warning, try disabling SmartScreen filter. In this tutorial, we will show you three ways to disable the security feature, as it is applied to the entire Windows 10 operating system, to applications received from Microsoft Store, and to the system’s featured browser, Microsoft Edge.

Disable SmartScreen in Windows 10 with Windows Defender Security Center

In this case, you should open Windows Defender Security Center. It can be done in a few ways.

Click on the Start button on the Taskbar, and open the main Windows menu, then click the gearwheel symbol. Alternatively, drag the scroll bar down until you find the line Settings.

In the application window, drag the slider down and select the section Update and Security.

On the left, select Windows Security, and on the right click on Open Windows Defender Security Center.

It opens the main window of Windows Defender Security Center.

In the side menu on the right, select App & browser control. You will be redirected to the page where you can configure SmartScreen for applications and browsers.

Here, you can disable Check apps & files, SmartScreen for Microsoft Edge and SmartScreen for Microsoft Store apps. Check the Off option in corresponding sections.

When the pop-up notification from Windows User Account Control asks Do you want to allow this app to make changes to your device? click Yes for the changes to take effect.

Disable SmartScreen in Windows 10 with the Registry Editor

Note: It is important to remember that anything you do to the registry is on your own responsibility. Any actions involving the registry may cause irreversible consequences. Windows 10 may begin working with errors, some apps or programs may not be able to start, the operating system can crash or have problems when booting. Before you start modifying the registry, we strongly recommend backing it up, just in case. To do it, open the Registry Editor, choose the File tab in the main menu, and select Export. The operating system will suggest you to give a name to the registry backup and select the directory where to save it. Choose a name that will help you to remember when exactly this backup was created. The best name would be the date of creation, for example, 02-04-2019. After that, click Save. Now you will have a registry backup file which you can use to restore it if necessary.

One more time, open the Run dialogue box in any of the ways described in this article (for example, by pressing the keyboard shortcut Windows + R for quick access to the Runwindow). In the command prompt field, type the command for opening the Registry Editor (regedit) and click ОК to perform the command.

When the pop-up notification from Windows User Account Control asks Do you want to allow this app to make changes to your device? click Yes and open the Registry Editor window.

In the left-side part of the window, follow the path:

HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsSystem

You can also use a different method for accessing this particular section of the registry. Just copy and paste it into the address bar of the Registry Editor (it’s under the main menu). This way, you can avoid possible errors when selecting the registry section, as the left panel displays many similar directories, and this specific method helps you make sure you use the correct address.

Right-click on an empty area on the right, select New from the context menu that appears, and click on the nested menu option DWORD value (32 bit).

Give the new DWORD value the name EnableSmartScreen. Double-click on it, or right-click on it and select Modify from the menu.

In the window Edit DWORD value (32 bit) set the Value data to0 (this value data will be used by default). Click ОК or press Enter on your keyboard to save the changes to the value.

Now close the Registry Editor window and restart your computer. After that, SmartScreen will be disabled.

Disable SmartScreen in Windows 10 with the Local Group Policy Editor

If your computer is running Windows 10 Home Edition, you won’t be able to use the functionality of the Local Group Policy Editor, as this utility is not excluded into this particular version of the operating system. For other versions of Windows 10, do the following.

Open the Run dialogue box in any of the ways described in today’s article (for example, right-click on the Start button in the Taskbar, and select the Run dialogue box in the menu that opens). In the Command Prompt window, type the command gpedit.msc.

Click ОК or press Enter on your keyboard to confirm your action, and the Local Group Policy Editor window will appear.

In the left-side panel, follow this path:

Computer Configuration – Administrative Templates – Windows Components – Windows Defender SmartScreen.

There are two subsections, Explorer and Microsoft Edge. Each of them contains a policy setting Configure Windows SmartScreen that allows you to enable or disable the filter as you like. Double-click on it, or right-click on it and select Edit from the menu.

In the window that opens, check the option for Disabled, then click Apply and ОК to save the changes you have made.

Apply this algorithm to every subsection: Explorer and Microsoft Edge. In the first subsection, it disables checking files in Windows 10, and in the second subsection it turns off SmartScreen in Microsoft Edge. After saving the changes, close the Local Group Policy Editor, and the SmartScreen feature will be disabled.

There is also a way to disable SmartScreen in Microsoft Edge in the browser settings. Open Microsoft Edge and click on the three-dot button in the top right corner to open the main menu.

Select Settings.

Then click View advanced settings.

Scroll down to find the line Help protect me from malicious sites and downloads with Windows Defender SmartScreen and set the slider to Off.

Finally, when the SmartScreen feature is disabled, make sure that your application starts and works correctly now. If you see the error again, the problem must be in the application itself, not in the security feature.

Then all you can do is to wait for another update to fix this issue, or find another program to replace the faulty app. If you disabled the SmartScreen feature, make sure you turn it on again after the necessary application is installed. It’s not a good idea to leave your system open to threats and without protection, so turn the feature on again and improve the security of your operating system.

See the full article with all additional video tutorials. If you still have any questions, please ask in a comments. Also visit our Youtube channel, there are over 400 video tutorials.

Back to top button

by Milan Stanojevic

Milan has been enthusiastic about technology ever since his childhood days, and this led him to take interest in all PC-related technologies. He’s a PC enthusiast and he… read more

Updated on March 4, 2021

Computer errors are relatively common and some Windows 10 users reported ERROR_EXE_MACHINE_TYPE_MISMATCH error on their PC.

This error is followed by this message:

This version of %1 is not compatible with the version of Windows you’re running

That being the case, we will cover all the steps that you need to take to fix this issue in the article below.

---

How do I fix the Version is not compatible with Windows error?

1. Change Android Studio settings

Many users reported that this problem occurs in Android Studio, but you can fix it by changing few settings. To do that, follow these steps:

1. Download and install 32-bit JDK
2. Click on File > Project Structure dialog.
3. Now uncheck Use embedded JDK.
4. Select the 32-bit version of JDK that you downloaded.
   • Optional: Decrease the memory footprint for Gradle in gradle.properties to -Xmx768m.

By default Android Studio uses embedded JDK, however this JDK requires 64-bit Windows in order to work. As a result, you’ll get this problem on any 32-bit version of Windows.

To fix it you just need to install JDK separately and change couple of settings as shown above. After doing that, Android Studio should start working without any problems.

---

2. Run the application as an administrator

1. Find the application that is giving you this error and right-click it.
2. Choose Run as administrator from the menu.
   

If running the application as an administrator fixes the problem, you’ll have to start it every time by using this method. Alternatively, you can set the application to always start with administrator privileges. To do that, follow these steps:

1. Right-click the problematic application and choose Properties from the menu.
   
2. Go to Compatibility tab and check Run this program as an administrator option.
3. Now click Apply and OK to save changes.
   

Sometimes this error can occur if you don’t have the necessary privileges to run the desired application. However, you can grant yourself the necessary privileges by following the steps mentioned above.

After doing that, the application will always start with administrator privileges so you won’t experience this error anymore.

---

3. Download the problematic file again

In some cases, you can get This version of %1 is not compatible with the version of Windows you’re running error due to corrupted download. Sometimes your files might not be properly downloaded and this can lead to this and many other errors.

If you’re having this problem while trying to run downloaded files, we strongly recommend to download the problematic files again. After doing that, check if the issue still persists.

Alternatively you can download the problematic file using a different web browser and check if that solves the problem.

---

4. Make sure that you’re using the correct application

1. Right click the problematic file.
2. Choose Open with and select one of the suggested applications.
   

If you manage to open your file without any errors, you need to set a default application for this file type. To do that, follow these steps:

1. Right click the problematic file and choose Open with > Choose another app.
   
2. Now select the application that you want to use for this file type.
3. Check Always use this app to open option and click on OK.
   
4. Optional: If the desired application isn’t on the list, you can click on More apps > Look for another app on this PC. After finding the desired application, repeat the previous step.

Several users reported this error while trying to open images with certain applications. According to them, their settings were changed and all images were set to open with a nonexistent application.

To fix the problem, be sure to open the problematic file with the correct application.  Sometimes your default application settings don’t update properly leading to this and many other errors. If you’re having this problem, be sure to try this solution out.

---

5. Check if you’re using 64-bit version of Windows

This error can affect almost any application, and the most likely cause is the 32-bit version of Windows. Certain applications are optimized for 64-bit operating systems and they won’t work on 32-bit versions of Windows.

If you don’t know which version of Windows you’re running, you can easily check it by following these steps:

1. Press Windows Key + S and enter system.
2. Choose System from the menu.
   
3. Once the System window opens, you can see all the necessary information regarding your PC in the System section under System type. You can see the type of processor you’re using as well as Windows version.
   • Keep in mind that 64-bit versions of Windows can only work with 64-bit processors.
     

In most cases, this error will occur if you’re trying to run a 64-bit application on a 32-bit Windows. These types of applications can’t run on 32-bit Windows, so you’ll have to reinstall Windows and switch to a 64-bit version.

Alternatively, you can check if the 32-bit version of the application you’re trying to run is available. If so, be sure to download it and it will work without any issues on 32-bit version of Windows.

Since 64-bit architecture offers better performance, some developers are developing applications exclusively for 64-bit systems. If that’s the case with your application, you won’t be able to run it at all, unless you install 64-bit version of Windows.

---

6. Set default application for ODM files

Many users reported that they are getting this error while trying to download ODM titles using OverDrive. The issue is caused because file association is changed, but you can fix that by following these steps:

1. Press Windows Key + I to open the Settings app.
2. Go to System section and choose Default apps.
3. Scroll all the way down and click on Choose default apps by file type.
   
4. Locate .odm file type and click Choose a default next to it.
   
5. Select OverDrive and save changes.

After doing that, you’ll be able to work with ODM files with ease.

Alternatively, you can associate file extensions with applications by following these steps:

1. Press Windows Key + X and choose Control Panel.
   
2. When Control Panel opens, choose Default Programs.
   
3. Select Associate a file type or protocol with a program.
   
4. Locate .odm file type on the list and double click it.
5. Select OverDrive and save changes.

Although this error occurs with ODM files and OverDrive, it can also happen with other applications and file types. Even if you don’t use OverDrive, you can try out this solution if you notice problems with specific file types.

---

7. Use a virtual machine

If you’re trying to run an old application and getting This version of %1 is not compatible with the version of Windows you’re running message, it’s rather possible that you’re trying to run a 16-bit application.

These types of applications can’t run on any new versions of Windows, but you might be able to circumvent this problem by using a virtual machine. Virtual machine is a virtualization software that allows you to run another operating system inside your current operating system.

Virtualization can be demanding on your resources, so before trying to use a virtual machine, be sure to check if you have enough hardware power to run it.

If you’re trying to run a 16-bit application, you can try installing 32-bit version of Windows XP on a virtual machine. This isn’t the simplest solution, especially if you don’t have an old copy of Windows XP lying around.

If you can’t set up a virtual machine with Windows XP, you might want to try using tools such as DOSBox. This is a DOS emulator you can use to run older 16-bit applications on your PC with ease.

Although this solution is relatively simple, it only applies to older applications that are giving you this error. If this problem occurs with any modern application, this solution won’t be able to fix it.

---

8. Reinstall the problematic application

This error can affect various apps, and the common cause for this problem is a corrupted installation.

To fix the problem you just have to uninstall the problematic application from your PC and install it again. Few users reported that reinstalling the application fixed the problem for them, so be sure to try it out.

---

9. Don’t install application in compatibility mode

1. Right click the setup file and choose Properties from the menu.
   
2. Go to Compatibility tab and make sure that Run this program in compatibility mode for option isn’t checked.
3. Click Apply and OK to save changes.
   
4. After doing that, try to run the setup again.

Compatibility mode is a useful feature for older applications, but it doesn’t work in all cases. Sometimes this feature can cause errors such as this one to appear, and in order to fix it it’s advised to turn this feature off.

Some applications, such as Norton antivirus, can give you this error during the installation process. It seems that these applications can’t install properly if you’re using compatibility mode.

To fix this issue, you need to turn off the compatibility mode for the application you’re trying to install.

---

10. Install the latest Windows updates

1. Press Windows Key + I to open the Settings app.
2. Once the Settings app opens, navigate to Update & security section.
3. Now click Check for updates button. Windows will check for any available updates and download them in the background.
   

After downloading the necessary updates, try to run the problematic application again and check if the problem is resolved.

Windows 10 is a great operating system, but it’s not perfect, so certain bugs and glitches can occur once in a while. If you’re having this error on your PC, we advise you to download and install the latest Windows updates.

Microsoft is frequently releasing updates and fixing various bugs and glitches, and in most cases these updates are downloaded automatically in the background. However, sometimes it can happen that you skip an update, so it’s always a good idea to check for updates manually.

---

This error message and the ERROR_EXE_MACHINE_TYPE_MISMATCH error can appear on any PC. Fortunately for you, these errors aren’t serious and they’ll usually appear on 32-bit Windows while trying to run a 64-bit applications.

If you encounter any of these errors, feel free to try any of our solutions, but let us know which ones worked best for you by leaving us a message in the comments section below.