Solved Unable to run sysinternals programs like autoruns.exe

zebal · Dec 2, 2023

None of the executables from sysinternals like process monitor are able to run due to some conflict with manifests for common controls.
When I run a program explorer process freezes. (taskbar, explorer everything get frozen)

Here is quote and screenshot from even viewer:

Activation context generation failed for "C:\tools\Autoruns.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_6eb991c088050a06.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_270c5ae97388e100.manifest.

Event ID 78
Source SideBySide

If you have same Windows build version as me do you having problem running sysinterals?
Any suggestions on how to fix the problem?

I have the latest executables from sysinternals.

x BlueRobot · Dec 2, 2023

I would try an SxSTrace using the following instructions:

Open the Start menu of Windows and type the command CMD
When you see Command Prompt on the list, right-click on it and select Run as administrator.
Copy and paste the following command into the command prompt and press enter.

Code:

SxsTrace Trace -logfile:SxsTrace.etl

Open the application that is causing the problem, as soon as it fails, press Enter to stop the tracing process.
Copy and paste the following command into the command prompt to generate the logfile of the SxSTrace on your desktop.

Code:

sxstrace Parse -logfile:SxSTrace.etl -outfile:"%userprofile%\desktop\SxSTrace.txt"

Post the logfile SxSTrace.txt as attachment in your next reply.

Have you also tried a component clean up using DISM?

Ghot · Dec 2, 2023

@zebal

I have Autoruns 13.98 and it runs fine... same Windows version.

As mentioned above, I would run the following in an elevated command prompt...
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase

zebal · Dec 2, 2023

Thank you, attached is trafe file.

x BlueRobot said:
Have you also tried a component clean up using DISM?

No, but will do now, thanks!

zebal · Dec 2, 2023

Ghot said:
I have Autoruns 13.98 and it runs fine... same Windows version.

I can't run to check version, but according to file properties mine is v4.10
I'll see if running older version works, if DISM doesn't solve the problem

Ghot · Dec 2, 2023

zebal said:
I can't run to check version, but according to file properties mine is v4.10
I'll see if running older version works, if DISM doesn't solve the problem

I believe your version is 14.10 but I get the idea.

I just checked. I ran Autoruns 14.10 on my comp and it works fine.

OAT · Dec 2, 2023

zebal said:
I can't run to check version, but according to file properties mine is v4.10
I'll see if running older version works, if DISM doesn't solve the problem

Are you sure you are have installed the 64-bit version? It looks like calls are being made thru the 32 bit one.
C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_6eb991c088050a06.manifest. Component

Ghot · Dec 2, 2023

x BlueRobot · Dec 2, 2023

zebal said:
Thank you, attached is trafe file.

Thanks, your SxSTrace looks to be okay, it seems that the amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_270c5ae97388e100 is the "winning" or active component.

Please let us know if a component clean up works, otherwise we can have a look at your SxS subkey.

OAT · Dec 2, 2023

Ghot said:
View attachment 79782

I know you do @Ghot, but if you go thru WSCC it lets you choose which one to install.
BTW @Ghot, why would you have an ARM version on your system?

Ghot · Dec 2, 2023

OAT said:
I know you do @Ghot, but if you go thru WSCC it lets you choose which one to install.
BTW @Ghot, why would you have an ARM version on your system?

Autoruns is portable... those are the files that are in the download.
The whole folder is only 6MB... so I just ignore the other versions.

They don't take up enough space to convince me to expend the energy to delete them.

OAT · Dec 2, 2023

Ghot said:
Autoruns is portable... those are the files that are in the download.
The whole folder is only 6MB... so I just ignored the other versions.

3 versions when only one is needed.
Thank God space is cheap! :wink:

zebal · Dec 2, 2023

Ghot said:
I believe your version is 14.10 but I get the idea.

Yeah sorry, it's 14.10.

OAT said:
Are you sure you are have installed the 64-bit version? It looks like calls are being made thru the 32 bit one.

Yes, I'm running 64 bit version of programs, but now also tried running x86 version and it's same problem

x BlueRobot said:
Please let us know if a component clean up works, otherwise we can have a look at your SxS subkey.

Unfortunately DISM command shared by @Ghot didn't fix the issue and I rebooted system afterwards.

But I noticed that after some time, ex. 4-5 minutes the program runs! it asks me for admin credentials and it opens.

What steps do you have next?

Ghot · Dec 2, 2023

OAT said:
3 versions when only one is needed.
Thank God space is cheap!

It's wasn't really a conscious thought. I download the zip file... extract it and run Autoruns64.exe
I don't really even "see" the others.

Now in another situation... VLC Media Player... I remove over half the files in that installation folder.
Because they're evil I tell you! Evil!

These are the only things I leave in the VLC folder...

This is the EVIL that I remove from VLC...

zebal · Dec 2, 2023

@x BlueRobot
Because it takes several minutes to run the program it's possible that SxS trace couldn't catch the error?
Maybe I should regenerate trace file with longer wait time until autoruns opens?

OAT · Dec 2, 2023

Ghot said:
It's wasn't really a conscious thought. I download the zip file... extract it and run Autoruns64.exe
I don't really even "see" the others.

I see , I use the 'clunky' GUI. But we divert...

zebal · Dec 2, 2023

OAT said:
It looks like calls are being made thru the 32 bit one.
C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.22621.2506_none_6eb991c088050a06.manifest. Component

Indeed, good catch! I completely missed that lol
According to event viewer x86 manifest version is active while x64 manifest is needed and can't be loaded since x86 is already active.

At least now we know what's the problem.

This is fresh installed Windows, it worked for first few days, problem occurred after some time, like 7 days after fresh install.

Wisewiz · Dec 2, 2023

Ghot said:
They don't take up enough space to convince me to expend the energy to delete them.

Oh, lawzy! I'm just exhausted! You wouldn't believe how difficult it is to delete six whole files!

Ghot · Dec 2, 2023

Every time I right click one to delete.... my mouse gets so heavy, I need to rest a bit.

johnlgalt · Dec 2, 2023

And then, every time you download a new version, you have to delete them again.

In this day and age if 4 MB is an issue - you've got bigger problems lol.

I'm with OAT though - WSCC FTW.