Oops profile did it again !

[Selur]

That file contained "after (fresh created).xml" and a "before (sharpening non-working).xml"
Since none of the screenshots or text you wrote said anything about 'sharpening', I got no clue what you want to say with 'sharpening non-working'.

Comparing the models the main differences I see are:
after:

<HybridData name="preferFFmpeg" value="false"/>
<HybridData name="preferFFmpegForAvisynthDecoding" value="true"/>
<HybridData name="keepResize" value="true"/>
<HybridData name="useFFmpegGPUDecoding" value="false"/>

before:

<HybridData name="preferFFmpeg" value="true"/>
<HybridData name="preferFFmpegForAvisynthDecoding" value="false"/>
<HybridData name="keepResize" value="false"/>
<HybridData name="useFFmpegGPUDecoding" value="true"/>

So I copied your "before (sharpening non-working).xml" into my profiles/global folder, started Hybrid and applied it.
Looking at the 'Crop/Resize->Base'-tab from which your screenshots were, I see:

Nothing is like your screenshots suggested.

Back to 'sharpening non-working', I loaded a random HD source, enabled compare view and started the Vapoursynth Preview:

The used 'DetailSharpen' does clearly work.
Since you didn't mention anything about your source, I also loaded a UHD source:

'DetailSharpen' does clearly work here too.
And also a SD source: (DetailSharpen originally is meant to sharpen details on downscaled source.)

sharpening is working there too.

Side notes:
Since you set 'Auto deinterlace handling' to 'none', I hope you really know that this does in Hybrid:

Deinterlace handling:
Sets what method will be used to deal with non-progressive content, assuming the output isn't marked as interlaced in the encoder.
Hybrid does only deinterlace if:
a. the source is non-progressive
b. the output is not interlaced
So:
- If your source is flagged as interlaced, but in reality is progressive: overwrite the scan type.
- If your source is flagged progressive, but in reality interlaced: overwrite the scan type.
- If your source is progressive and properly flagged, do not worry Hybrid will not try to deinterlace the source.
=> Do not set this to 'none', unless you really know what you are doing and what are the consequences are when using Hybrid with this setting set to 'none'.
Setting 'none' will force a scan type overwrite to 'progressive'.

source: 'Auto deinterlace handling'-tool-tip

Also disabling 'Auto adjust' usually seems like a bad idea too.


So, the overall conclusion is: I can't reproduce the issue here with the given information.

Question: is it possible the security settings for folder acces/restrictions (ie: where global profiles are stored) in win11 may confuse hybrid 0_o ?

Global Profiles are save in AppData/Roaming which is accessible by all applications. So unless you messed with your Windows 11, that is not the problem. (not having any issues here)

I have found a fairly new profile that was made via a previous install of hybrid (feb release..), that doesn't seem to work correct once loaded in the latest release of hybrid.
Namely Vapour Synth is missing totaly no filters shows !

Loading that profile here, it is correct that Vapoursynth-Tab is hidden, since 'Crop view' is enabled, and since the Avisynth/Vapoursynth filters are disabled during 'Crop view' those are disabled.
So that is as intended. Disable 'CropView' and the controls are visible and enabled again.

Cu Selur

Ps.: going to bed now.