Sysinternals
Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.
1,265 questions
Latest Autoruns (v14.1) has a bad manifest
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 50%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDA%3C/text%3E%3C/svg%3E)
Dimitry Andric
15
Reputation points
Similar to https://learn.microsoft.com/en-us/answers/questions/1196289/latest-32-bit-tcpview-(v4-18)-has-a-bad-manifest , I recently updated to the latest Sysinternals Suite as of June 27, 2023, and later noticed a message in the machine's Event Log:
Activation context generation failed for "C:\Program Files (x86)\SysinternalsSuite\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.19041.1110_none_a8625c1886757984.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_60b5254171f9507e.manifest.
This is the 32-bit version of Autoruns.exe. It starts up just fine, though.
The 64-bit version causes no messages in the Event Log, as far as I can determine.
Sysinternals
Sign in to answer