OneCoreUAP.OneSync being reintroduced despite disabled in Preset

TT9tWhD$q

Member
  • host W10 Pro x_64 1909 b18363.657
  • target same as host
  • NTL 1.9.0.7330 x_64 portable mode
______

Whilst present in the Preset

XML:
<Feature name="OneCoreUAP.OneSync~~~~0.0.1.0">false</Feature>

the NTL UI showing it as set/enabled after having loaded such preset. Is that intended? Also having is unset/disabled in the Preset it would have been expected that pertaining service - Sync Host - to be grayed out and disabled but that does not happen.
 
That's Exchange ActiveSync... feature on demand, tested it now on 1903 and it disabled fine.
Then tested the preset load on the enabled image to get pending disabling, seems to work as well.

Can you walk me through how to see the issue?
It's about the Feature On Demand, does it remove the service is up to Microsoft's packages.
To remove OneSync component, use the Components page instead - with its caveats prompted on first use.

Thanks.
 
Ah, I was not aware of the correlation between Exchange ActiveSync and that FOD package, though it is clearly mentioned here FOD ...

And with Exchange ActiveSync locked from the compatibility settings for Office it makes sense that the FOD package shall remain.
 
Back
Top