[1903, au] An app caused a problem with your default "X" setting, so it was reset to "Y"

[RLR]

Currently testing Windows 10 1903/1909 and coming across an issue the first time a user logs into a machine. When they log in, they get several messages saying: An app caused a problem with your default "X" setting, so it was reset to "Y". This message appears several times depending on the file type and program that has been reset. I've created an associations xml file which is applied via MDT and gpo which seems to be working. Even though, this message appears, it seems the apps don't get reset.

 

Done quite a bit of googling and seems to be quite common but can't find a solution.

 

We don't get this message on 1703.

Edited November 27, 2019 by RLR

[Warwick_Tech]

Currently testing Windows 10 1903/1909 and coming across an issue the first time a user logs into a machine. When they log in, they get several messages saying: An app caused a problem with your default "X" setting, so it was reset to "Y". This message appears several times depending on the file type and program that has been reset. I've created an associations xml file which is applied via MDT and gpo which seems to be working. Even though, this message appears, it seems the apps don't get reset.

 

Done quite a bit of googling and seems to be quite common but can't find a solution.

 

We don't get this message on 1703.

 

Common problem, no solution -

 

Sometimes we get it, sometimes we don't, but no apps seem to reset; again pushing appassociations.xml via GPO - running 1803 here

[chaplic]

Are you using the same app association file? they are NOT portable across windows versions.

[RLR]

Are you using the same app association file? they are NOT portable across windows versions.

 

Yea, I created a new one for the new version of Windows.

[Warwick_Tech]

Are you using the same app association file? they are NOT portable across windows versions.

 

Really? I thought it was just a generic file eg.

 

[RLR]

Think I've sorted it by coming across another issue. I noticed our new MDT task sequence with the new WIM file wasn't bitlockering our machines automatically. I could go in an initiate bitlocker manually. I looked at the logs and it said bitlocker is only supported on Enterprise and Server. This made me think I was using the wrong version of Windows. This came down to extracting the WIM file from the ISO using "dism /Get-WimInfo /WimFile:F:\sources\install.wim". This will list all the flavours of Windows 10 in the install.wim file. For example:

 

Index : 1

Name : Windows 10 Education

Description : Windows 10 Education

Size : 14,780,927,379 bytes

 

Index : 2

Name : Windows 10 Education N

Description : Windows 10 Education N

Size : 13,958,508,090 bytes

 

Index : 3

Name : Windows 10 Enterprise

Description : Windows 10 Enterprise

Size : 14,781,260,269 bytes

 

Index : 4

Name : Windows 10 Enterprise N

Description : Windows 10 Enterprise N

Size : 13,958,401,617 bytes

 

Index : 5

Name : Windows 10 Pro

Description : Windows 10 Pro

Size : 14,782,419,696 bytes

 

Index : 6

Name : Windows 10 Pro N

Description : Windows 10 Pro N

Size : 13,975,944,782 bytes

 

Index : 7

Name : Windows 10 Pro Education

Description : Windows 10 Pro Education

Size : 14,780,857,141 bytes

 

Index : 8

Name : Windows 10 Pro Education N

Description : Windows 10 Pro Education N

Size : 13,958,436,952 bytes

 

Index : 9

Name : Windows 10 Pro for Workstations

Description : Windows 10 Pro for Workstations

Size : 14,780,892,026 bytes

 

Index : 10

Name : Windows 10 Pro N for Workstations

Description : Windows 10 Pro N for Workstations

Size : 13,958,472,287 bytes

Out of all these versions the best one sounded like "Windows 10 Pro Education" as the only other option was "Windows 10 Eduacation" - "pro" being the difference. Windows 10 Pro doesn't support bitlocker via mdt and I guess it doesn't support certain GPOs like default applications. I found out that the one called "Windows 10 Education" is actually the enterprise version of Windows 10 Education. I'm now using this WIM and it works fine.

[chaplic]

New version windows, new assocation file - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/export-or-import-default-application-associations

 

 

Also,thanks RLR for mentioning that - I literally just did the same with my MDT on 1909, creating new build as I type..

[RLR]

I thought my issue was resolved by choosing the correct version of the WIM but I'm still getting it.

[thatley]

I found this on 1903 but you only seem to get 3 of the messages but that's only at first logon. With 1909, you get 12 messages which is ridiculous. Found this with older version of xml or a new one.

 

I worked around this by disabling only the "system" messages in the action centre with a GPO that changes this REG_DWORD setting:

 

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Notifications\Settings\windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel\

Set value to 0

 

Not had any issues so far, so keeping it until it gets fixed (if ever!)

[petben]

Hi thatley we too get this at login, Win10 1903, only sometimes of course. Does your reg key just stop the message? I imagine the actual behaviour will still be the same (e.g. it changes the .html default back to Edge) but just the message is suppressed?

 

 

I have been recently thinking of Win10 LTSC, but that's another Q altogether..

[RLR]

Hi thatley we too get this at login, Win10 1903, only sometimes of course. Does your reg key just stop the message? I imagine the actual behaviour will still be the same (e.g. it changes the .html default back to Edge) but just the message is suppressed?

 

 

I have been recently thinking of Win10 LTSC, but that's another Q altogether..

 

I haven't tested the reg key yet but I have found the messages that say the app has been reset back to default doesn't actually reset it back to default. Might be worth double checking if this is the same for you.

[thatley]

I haven't tested the reg key yet but I have found the messages that say the app has been reset back to default doesn't actually reset it back to default. Might be worth double checking if this is the same for you.

 

Hi,

 

On first log on to a machine, you get the messages and it doesn't change the defaults from the .xml. Log off then on again and .xml settings kick in. I think this has done this since 1803 what I can remember.

[petben]

Hi,

 

On first log on to a machine, you get the messages and it doesn't change the defaults from the .xml. Log off then on again and .xml settings kick in. I think this has done this since 1803 what I can remember.

 

So this is the behaviour without the reg key? Your reg key stops the messages..right?

 

Do you actually create this reg key? the only key I have in that settings key is Microsoft.ScreenSketch_8wekyb3d8bbwe!App

[thatley]

So this is the behaviour without the reg key? Your reg key stops the messages..right?

 

Do you actually create this reg key? the only key I have in that settings key is Microsoft.ScreenSketch_8wekyb3d8bbwe!App

 

Basically this reg key gets created if you toggle the "settings" to off in the Notifications & Actions screen. I just use a GPO to disable the "settings" notifications enabling that reg key so you don't get the messages on first logon (new profile).

 

So to clarify, with the "settings" notifications disabled, none of those messages will appear at first logon, but the 'defaultassociations.xml' still doesn't kick in until the user logs off and on again.