@void:
If you are bored AND it's been raining for 3 days AND you polished all your silverware ... twice ...
Currently Everything shows in Win10's taskmanager in the "Operating system context" column of the dtails tab: Windows Vista.
(It does no harm, btw.)
That can be "solved" by adding an <compatibility> section to the application's manifest.
Happy silverware polishing
Application manifest: compatibility section
Re: Application manifest: compatibility section
Fixed for the next update, thanks.
Re: Application manifest: compatibility section
It's 'unfixed' in 1.4.1.947 (didn't check other versions).
docs.microsoft.com/en-us/windows/compatibility/application-executable-manifest
https://docs.microsoft.com/en-us/window ... -manifests
docs.microsoft.com/en-us/windows/compatibility/application-executable-manifest
https://docs.microsoft.com/en-us/window ... -manifests
Re: Application manifest: compatibility section
I've added to the Everything manifest for the next major version:
I need to test this some more before I release this change with Everything 1.4 as it may cause compatibility issues.
Code: Select all
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
</application>
</compatibility>
Re: Application manifest: compatibility section
The supportedOS and compatibility manifest settings only apply to Vista or later.
This will make no difference when running Everything on Windows XP.
Everything will still be compatible with Windows XP.
This will make no difference when running Everything on Windows XP.
Everything will still be compatible with Windows XP.
Re: Application manifest: compatibility section
Fine with me; I'm only reporting ...
Or fix some.
I came here because of the "Shell Resource Leaks" thread and vaguely remembered that thread handling was different when using this compatibility manifest setting. Turns out that was for RPC calls, so not applicable, but bottom line: it's not only cosmetic, but might actually change application behaviour.
Anyway: waiting for the next major version sounds like a good idea.