question

BenKosar-4450 avatar image
1 Vote"
BenKosar-4450 asked ITBuchs-4905 edited

Windows10 1909 Upgrade - An App Default Was Reset

My org is using WIn10 Pro (volume license) build 1809. We want to upgrade to 1909. We use PDQ Deploy to download the install.wim and run this command to install:
start /wait c:\UpgradeInstall\1903\setup.exe /auto upgrade /Compat IgnoreWarning /installfrom c:\UpgradeInstall\1903\sources\install.wim /dynamicupdate enable /showoobe none /quiet

As a background we use a default associations configuration file (we've named to win10-default-associations.xml) which is applied via GPO.

After the windows upgrade when a user logs in they are assaulted with a flurry of about 15-30-ish messages that a app default was reset. And the default apps are all reset generally to MS products, PDF's are switched from adobe to edge, etc. There have been a number of exports done with DISM and in all manner of testing the upgrade to either 1903 or 1909. This is holding up my beta testing of 1909. Does anyone have any info or a solution?

I've been following this thread, in which by word of mouth supposedly there is supposed to be a fix of some kind in this month's patch tuesday.
https://social.technet.microsoft.com/Forums/en-US/ad37cd15-315e-4f9b-ba34-bcbd987981fc/quotan-app-default-was-resetquot-error-newly-sysprep-windows-10-ltsc-2019-enterprise-image?forum=win10itprosetup

Does anyone happen to have any inside info, more specifics, or anything at all? If there is a hotfix, patch, etc, would love to get my hands on it, or at least know what it is so I can open a case with MS and request it.

windows-10-setup
Comments Locked · 3
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LucasA avatar image LucasA ·

On which Win10 version was the default associations configuration file generated ?
Can you try to create the default associations file from Windows 10 1909, don't change anything and deploy it on a test computer to see if it works as-is ?

0 Votes 0 ·
BenKosar-4450 avatar image BenKosar-4450 LucasA ·

GPO was generated with 1809. I've tried isolating and not having the 1809 .xml touch the test machines, and have tried importing 1909 .xml files and they had the same result (even when taking a vanilla 1909 .xml and applying it, with minimal changes. pdf and chrome as browser via http and https extensions )

0 Votes 0 ·
LucasA avatar image LucasA BenKosar-4450 ·

Have you checked that no program tries to change file associations on first logon, for example ? Just to be sure that the issue is not caused by something else...

Additionnally, can you confirm that you proceed as follows: change the default association on a "reference" computer using the Settings app (GUI), then generate the file with Dism /Online /Export-DefaultAppAssociations:c:\path\AppAssoc.xml and that you don't edit the file manually afterwards ?


The problem appears again after gpupdate /force followed by a logoff/logon ? Or does it only happens once per profile?
Did you use /Import-DefaultAppAssociations with Dism or just the GPO settings to import the file on the computers ?


0 Votes 0 ·

10 Answers

Joyqiao-3755 avatar image
0 Votes"
Joyqiao-3755 answered IvanHung-2499 published

Hi,
I noticed you are using PDQ deploy which is not supported by Microsoft. I would recommend to use Sysprep to check the issue again.
As we have encounter same issue with your referred thread, I would provide my knowledge here for you and other similar issue customers' reference.

When using copyprofile true, the current user's profile gets copied over to the c:\users\default and is used as the default template for a new user creation by windows
For this default user account the following entries already exist
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\<fileextensions>\userChoice\Hash
However the hash is based off the SID of the user account in whose context the sysprep was run
So now when a new user logs on OEMDefaultAssociations.xml gets applied, the Hash that is already present is detected as invalid causing a application notification storm of app resets.

Based on discussion with feature team for FileExts, Sysprep copyprofile in unattend.xml is not fully supported for this scenario. Incase copyprofile option still needs to be used, then the end user/Deployment admin, needs to ensure before the copyprofile runs, to copy the target profile as the default profile,

The source profile really should not have anything in either of these locations either:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations
Also delete the entry
FileAssociationsUpdateVersion
from HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations

The above steps will ensure that the default profile is not seeded with the old user's file extension choices. and regular user defaults get applied as per OEMDefaultAssociations.xml

Please feedback your action result here.

Bests,

Comments Locked · 3
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BenKosar-4450 avatar image BenKosar-4450 ·

PDQ Deploy isn't really the issue - all it does is execute code remotely. It does things as if it was logged in via the account used. I also have the same result when run locally on the machine.

Installing a new build that would use sysprep I could see working, however I use MDT with a clean image, and things are done after the image is laid down. Can you use sysprep to upgrade a win10 build? What about machines that have multiple users on an existing box? Our org usually has a minimum of 5 different user accounts on each machine. So how would you make a sysprep solution work?

0 Votes 0 ·
EDUBS-9156 avatar image EDUBS-9156 BenKosar-4450 ·

Did you find an answer for this? I'm having the same issue as you are post-upgrade. I was following the other thread that said there was a hotfix, but that thread redirected here, and isn't actually here. Anyway, this isn't an issue with sysprep. I do my deployments right from a clean wim extracted from the ISO. During deployment (within windows under the Administrator account) we use copyprofile to copy region settings to other profiles, and after upgrade, domain accounts receive this error when logging in. I'd really love to get that hotfix that was mentioned.

0 Votes 0 ·
IvanHung-2499 avatar image IvanHung-2499 ·

Joyqiao,

hi, would you please explain or how to do this step>> "needs to ensure before the copyprofile runs, to copy the target profile as the default profile,"

thanks

0 Votes 0 ·
David42-6994 avatar image
0 Votes"
David42-6994 answered David42-6994 published

I was also suffering from 11 notifications when each new user logs in after installing a system prepared with Sysprep.

In my case I finally discovered this was caused by the single account I am required to create when installing the virgin copy of Windows prior to customising it and sysprepping it. By going into sysprep audit mode and deleting that account before doing Sysprep generalise, the problem has gone away for me.

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

beeryurt avatar image
0 Votes"
beeryurt answered jaybird283-2674 commented

I just tested the April patch and on my first random device the pop ups have gone from 12 ton1, so clearly there was an issue with windows 10, this was only tested on 1909

Comments Locked · 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

jaybird283-2674 avatar image jaybird283-2674 ·

beeryurt, which patch did you use?
Did you apply it to the 1809 machine before you did your in place upgrade?

0 Votes 0 ·
BenKosar-4450 avatar image
0 Votes"
BenKosar-4450 answered BenKosar-4450 published

I did find an answer. Copyprofile must have some functionality because if you add copyprofile: false then in my test env I was able to get things to function - even with my 1809-based defaultapps.xml

In MDT this means (in x64 bit) download the WSIM 1903 fix, open the unattend (in the share under control, then the task squence) and open the unattend file and save it. If you save with the updated WSIM you will be able to edit the file within MDT (new task sequences do not generate properly for some reason, WSIM fixes them with the fix applied). From there you can add copyprofile: false (just search for copyprofile, add to phase4). This seemed to do the trick for me. I'm not sure how you would otherwise modify a install.wim.

MS released an updated 1909 install disc, I think it was on 3/27 via the Volume License center. This version appears to have the fix as running without copyprofile: false (just default) seems to do the trick, though I'm pretty early in my initial testing.

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ottafish-1432 avatar image
0 Votes"
ottafish-1432 answered ottafish-1432 published

No change for me. Same 3 pop up errors as before.
It's really frustrating that I'm holing up the release of 1909 to our fleet.

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

BenKosar-4450 avatar image
0 Votes"
BenKosar-4450 answered

I have two default app settings were changed messages, one for holographic something, and another for xbl-something. These are probably because I don't have the extensions defined in my defaultappassosciations.xml file (which now works after the march disc update!). I don't intend on fixing those. What the march update doesn't fix is win10's inherant angryness with changing the default browser.

I will say if I do a upgrade task sequence with MDT it does some extra steps natively. I"m not sure what all it does, but if you change the unattend.xml to copyprofile:false, you don't get the app default change messages, but you do get the default browser changed to edge message. (We have https/s/etc defined via appassociations.xml so they still function). We've decided to install using the cmd line upgrade and install.wim method, and will live with the 3 warning messages it now gives.

Note - if you use Policypak there is a add you have to do for msra to exploitprotection.

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ITBuchs-4905 avatar image
0 Votes"
ITBuchs-4905 answered MattL-5267 commented

This update seems to fix the issue. Tested it today... No more strange App Default Reset messages
https://support.microsoft.com/en-us/help/4550945

Comments Locked · 1
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

MattL-5267 avatar image MattL-5267 ·

I placed a call with Microsoft Support back in January and they finally released the fix. I tested the above patch and it fixed the app reset problems I was having.

0 Votes 0 ·
jaybird283-2674 avatar image
0 Votes"
jaybird283-2674 answered

Did you just inject that update into your 1909 upgrade media?

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

romanelo avatar image
0 Votes"
romanelo answered

Tested on 1909, can confirm KB4550945 resolves this issue, I can't believe it took 1 year to fix this.

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ITBuchs-4905 avatar image
0 Votes"
ITBuchs-4905 answered ITBuchs-4905 edited

Just noticed that with the patch installed if you logon with a user profile for the first time the reset messages again appear... windows 10 1909 18363.815

Comments Locked
5 |1600 characters needed characters left characters exceeded
Toggle Comment visibility. Current Visibility: Visible to all users

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.