Closed ghost closed 4 years ago
Well... to sum it up, your proposal basically is "If you'd like to use Phone-PC linking, don't disable the functionality for Phone-PC linking" :)
The EnableMmx
isn't needed, as the feature is enabled by default. Moreover touching that key caused some nasty problems with start menu cache resets (#145).
Although DisableWindowsConsumerFeatures
is indeed required for the phone linking to work, it may also have unwanted side effects as it enables application suggestions and other obtrusive functions. So my proposal is that I review what exactly does DisableWindowsConsumerFeatures
do and what impact does it have to keep it enabled. If the other registry keys present in DisableAppSuggestions
handle their job even without DisableWindowsConsumerFeatures
, then the key can be removed from the tweak and DisableSharedExperiences
gets a nice note stating that it shouldn't be used if one would like to link a phone (which at that point will be a bit tautological anyway as that's one of the main reasons why one would use Shared Experiences).
So the fix is more pragmatic than I thought. In recent Windows builds, DisableWindowsConsumerFeatures
is applicable only to Education and Enterprise SKUs and seems to have no effect on Home and Pro. The other DisableAppSuggestions
keys along with DisableBackgroundApps
and UnpinStartMenuTiles
seem to do good enough job hiding the crapware.
So I'll remove DisableWindowsConsumerFeatures
and then the only thing you need to do on fresh installations in order to keep Phone-PC linking is simply not apply DisableSharedExperiences
.
Can be useful to add functions for to handle Phone-PC linking. These can be the functions:
Some doubts and open questions :
DisableAppSuggestions
. This can be a side effect.DisableSharedExperiences
. Also this can be a side effect.These points cause an execution affected by the order of the calls: the user must be aware of this and must decide how to act.
What do you think about it? @Disassembler0