This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 22%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBK%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(265.6, 31%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
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 ?
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 )
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 ?
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,
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?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 38%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 44%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIH%3C/text%3E%3C/svg%3E)
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 19%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIB%3C/text%3E%3C/svg%3E)
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 73%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ER%3C/text%3E%3C/svg%3E)
Tested on 1909, can confirm KB4550945 resolves this issue, I can't believe it took 1 year to fix this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 94%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
Did you just inject that update into your 1909 upgrade media?
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
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(310.4, 67%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
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.