HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts The source profile really should not have anything in either of these locations either: 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, 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.īased on discussion with feature team for FileExts, Sysprep copyprofile in unattend.xml is not fully supported for this scenario. However the hash is based off the SID of the user account in whose context the sysprep was run HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\FileExts\\userChoice\Hash 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įor this default user account the following entries already exist I would recommend to use Sysprep to check the issue again.Īs we have encounter same issue with your referred thread, I would provide my knowledge here for you and other similar issue customers' reference. I noticed you are using PDQ deploy which is not supported by Microsoft. 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.ĭoes 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. This is holding up my beta testing of 1909.
There have been a number of exports done with DISM and in all manner of testing the upgrade to either 1903 or 1909. And the default apps are all reset generally to MS products, PDF's are switched from adobe to edge, etc. Start /wait c:\UpgradeInstall\1903\setup.exe /auto upgrade /Compat IgnoreWarning /installfrom c:\UpgradeInstall\1903\sources\install.wim /dynamicupdate enable /showoobe none /quietĪs a background we use a default associations configuration file (we've named to win10-default-associations.xml) which is applied via GPO.Īfter 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. We use PDQ Deploy to download the install.wim and run this command to install: My org is using WIn10 Pro (volume license) build 1809.
0 kommentar(er)
