locked
"An App Default Was Reset" error newly sysprep Windows 10 LTSC 2019 Enterprise image completely breaking image. RRS feed

  • Question

  • This is driving me up the wall. I don't know what's wrong. No matter what I do, I get the error "An App Default Was Reset - An app caused a problem with the default app setting for '.x' files so it was reset to 'x software'."

    Why is this happening? I am building a VM with LTSC 2019 Enterprise to deploy on my campus. Issue only arises on domain/network profiles, local accounts don't seem to be affected.

    When the error occurs, it more or less bricks the OS. Internet Explorer no longer works or even opens, the search function no longer works, most apps within settings no longer open. I cannot run an sfc /scannow function in CMD (it says the service couldn't be started). In fact, most programs and apps no longer work. Often times, I can't even get CMD to elevate. It shows that it is elevated but then nothing will run in elevation, CMD just tells me that I must be elevated to do this task.

    I'm at a total loss here. Absolutely nothing found from Google has been helpful. I really don't want to use standard Windows 10 with how frequently Windows updates breaks the OS and how bloated the software is with excess garbage.

    LTSB 2016 is no longer a viable solution as it is not compatible with new Dell laptops, otherwise I would just stick with that. I've been using it for 3ish years.

    I am not very knowledgeable when it comes to creating images/sysprep etc. You'll most likely have to talk to me as if I'm a child and I'll do my best respond with accurate and detailed answers.

    Please help. Thank you.

    Wednesday, October 16, 2019 9:18 PM

All replies

  • Hi,

     

    The app defaults are reset by Windows 10 if it finds that an incompatible third-party program making changes to file associations directly, rather than directing users to the Default Apps window.

     

    Please refer to the link below:

    https://www.tenforums.com/tutorials/45792-fix-app-default-reset-error-windows-10-a.html

    Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.

     

    Hope above information can help you.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, October 17, 2019 2:02 AM
  • Hello.

    So, that's what I thought too. So I created a brand new VM, installed the .iso, then before doing anything else, I sysprep (both with a usual answerfile and even a blank one, just in case it was a setting I was making), and the problem still persisted.

    Again, this happens ONLY only network users. Local users do not have this problem.

    edit: also, I had already tried that "fix". I've ran it on the image, syspreped and applied, issue still persisted. Ran the fix on a computer that was already having the issue, still persisted. I even deleted the network users/profiles after running the fix, issue still persisted.
    • Edited by TippsAttack Thursday, October 17, 2019 2:02 PM
    Thursday, October 17, 2019 2:00 PM
  • Hi,

     

    That's strange happens only network users.

     

    Maybe try the solution the following link mentioned:

    https://www.winhelponline.com/blog/windows-10-resetting-file-associations/

    Note: This is a third-party link and we do not have any guarantees on this website. And Microsoft does not make any guarantees about the content.

     

    Best Regards,

    Freana


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 18, 2019 8:32 AM
  • Hi,

     

    Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.

     

    Best Regards,

    Farena


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 21, 2019 6:38 AM
  • That solution does'nt work on the 1903 version.  Any ideas on fixing this issue with the 1903 version?  I am having this problem on my reference image after running sysprep.  This only started happening after installing the cumulative updates for September.  

    Note: when I created the reference image, I ran the Powershell command: get-appxpackage -allusers|remove-appxpackage, and this removes most of the apps.  I also use a group policy to disable the app store, and disable any updates from the app store.

    After I run sysprep after the September updates I start getting the default app resetting message about 18 times.  The first message I receive is for ms-xbl-3d8b930f, which I believe refers to xbox live.  For some reason xbox is being installed when sysprep is run.  Xbox was not on the reference image.  

    Lastly I also use the  dism /online /Export-DefaultAppAssociations:C:\default\default.xml that is used with a group policy to refer to the default.xml for the default app settings.

    Tuesday, October 22, 2019 6:53 PM
  • I am creating an image as well. I took it back to basics:

    test 1. Windows 10 1903 LTSC, no apps installed, no OS updates, unattended.xml that just sets the computer name and admin/password.

    Result : When the sysprep completed, everything behaves as normal. Success

    Test 2. Windows 10 1903 LTSC, no apps installed, with OS updates applied, unattended.xml that just sets the computer name and admin/password.

    Result : When the sysprep completed, everything behaves as normal. Success

    Test 3. Windows 10 1903 LTSC, no apps installed, with OS updates applied. Included "Copyprofile" to the unattended.xml, which also sets the computer name and admin/password.

    Results : Post sysprep, first autologin, the file Associations all reset. Failed

    Eventlog:    SetDefault-Info: Association=https, ProgId=IE.HTTPS, U=S-1-5-21-2772914167-1314923040-1412238795-500, T=2019:10:04:31:18:56, H=RepslEqtnwQ=</Data>

    I am going to test if this occurs on an unpatched OS.

    No 3rd party app is causing this.

    Thursday, October 31, 2019 7:15 PM
  • Are you using "Copyprofile" in your unattend.xml?
    Thursday, October 31, 2019 7:16 PM
  • Yes.  I use copy profile.  I also set the admin password in the xml file.  I don't set the computer name.
    Thursday, October 31, 2019 7:39 PM
  • I have created my image with the below components:

    1. Windows 10 1809 LTSC

    2. Apps: Office 2016 x86, Firefox, Google Chrome, Adobe Acrobat Reader DC, Vmware Tools

    3. Minor OS customizations

    4. Applied all patches for OS and Office etc. Restarted

    5. Uninstalled patch kb4519338

    6. My unattend.xml performs, copyprofile, sets computername, sets admin/password, region, organization

    7. Run sysprep.exe /oobe /generalize /shutdown /unattend:{path to xml - C:\File\Path\To\unattend.xml}

    This created a clean image with no "App resets" on first login. I then ran windows update to apply reapply kb4519338.

    Its not the cleanest solution. But applying one update is not that much of a time increase. In testing tomorrow, I'll compare the below key on a sysprep'd computer without app reset problems and one with the reset problems. It could be interesting. 

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\{.extension}\UserChoice

    Anyway, I hope this helps. It what worked for me.

    Thursday, October 31, 2019 11:38 PM
  • What does {.extension} represent in  HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\{.extension}\UserChoice
    Friday, November 1, 2019 3:32 PM
  • This key is where the file extension associations are kept on a per user basis.

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\

    The "{.extension}" represents the extension. ie for a pdf file it would be :

    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.pdf\UserChoice

    Apparantly Microsoft made a change(a while ago) that require any file association changes to be made via API. You used to be able to modify the registry keys. Now Windows 10 detect these changes as "corrupt" and initiates  reset of the extension.(from what I read)

    Unfortunately in my additional testing, I applied patch kb4519338 on a Windows 10 1809 LTSC with no applications, after a clean completed sysprep that contained a "Copyprofile". Logon a new account and during profile setup, "App Reset" popups occur.

    I think its a MS Bug with the October patch.

    I have seen post of people using defprof. It might be a solution. If I find any other solutions, I'll let you know. If you find one, it would be good if you could post.

    Thanks

    Friday, November 1, 2019 9:44 PM
  • I have read many articles online regarding this issue. A common thread is that the file extensions are reset due to a 3rd party application writing to the registry instead of using the API.

    https://devblogs.microsoft.com/oldnewthing/?p=96175

    However I have a process monitor capture of a clean Windows 10 1809 LTSC computer(ie no 3rd Party apps). With all current patches installed and it continually resets file extensions on first logons. The process that is doing this is explorer.exe, launched by winlogon.exe.  All processes are Microsoft Processes.

    I am looking for a solution that can either be applied to the "Default" profile, HKLM or within a Mandatory profile.

    It would be great if someone within Microsoft could investigate this issue. I have only experienced it since the October updates.

    Tuesday, November 5, 2019 9:56 PM
  • I've been seeing very similar issues, if not the exact same issue. I had an MDT task sequence, including loading default app associations via the DISM command, perfected in early September but when running the same task sequence a week ago, I encountered lots of app reset notification issues. At first it was Edge and Photos being reset for .png and IE.HTTP file associations, but then I tried the LTSC version and encountered different issues. 

    I even went through the insanity of trying to determine which part of a defaultappassociations xml file was causing the issues to occur. Built in Windows app associations were fine, if I only changed those specific file extensions, without adding anymore, it would be okay. I eventually discovered that even though the message was "User choice has been reset to prog id PBrush for .png", the issue has literally nothing to do with .png files or the paint application. 

    For example, this default app association XML file works okay (I think...I tried at least 30 different versions):

    <?xml version="1.0" encoding="UTF-8"?>
    <DefaultAssociations>
      <Association Identifier=".3g2" ProgId="VLC.3g2" ApplicationName="VLC media player" />
      <Association Identifier=".3gp" ProgId="VLC.3gp" ApplicationName="VLC media player" />
      <Association Identifier=".3gp2" ProgId="VLC.3gp2" ApplicationName="VLC media player" />
      <Association Identifier=".3gpp" ProgId="VLC.3gpp" ApplicationName="VLC media player" />
      <Association Identifier=".aac" ProgId="VLC.aac" ApplicationName="VLC media player" />
      <Association Identifier=".adt" ProgId="WMP11.AssocFile.ADTS" ApplicationName="Windows Media Player" />
      <Association Identifier=".adts" ProgId="VLC.adts" ApplicationName="VLC media player" />
      <Association Identifier=".avi" ProgId="VLC.avi" ApplicationName="VLC media player" />
      <Association Identifier=".bmp" ProgId="ImageGlass.AssocFile.BMP" ApplicationName="ImageGlass" />
      <Association Identifier=".dib" ProgId="ImageGlass.AssocFile.DIB" ApplicationName="ImageGlass" />
      <Association Identifier=".emf" ProgId="ImageGlass.AssocFile.EMF" ApplicationName="ImageGlass" />
      <Association Identifier=".flac" ProgId="VLC.flac" ApplicationName="VLC media player" />
      <Association Identifier=".gif" ProgId="ImageGlass.AssocFile.GIF" ApplicationName="ImageGlass" />
      <Association Identifier=".htm" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier=".html" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier=".ico" ProgId="ImageGlass.AssocFile.ICO" ApplicationName="ImageGlass" />
      <Association Identifier=".jfif" ProgId="ImageGlass.AssocFile.JFIF" ApplicationName="ImageGlass" />
      <Association Identifier=".jpe" ProgId="ImageGlass.AssocFile.JPE" ApplicationName="ImageGlass" />
      <Association Identifier=".jpeg" ProgId="ImageGlass.AssocFile.JPEG" ApplicationName="ImageGlass" />
      <Association Identifier=".jpg" ProgId="ImageGlass.AssocFile.JPG" ApplicationName="ImageGlass" />
      <Association Identifier=".m2t" ProgId="VLC.m2t" ApplicationName="VLC media player" />
      <Association Identifier=".m2ts" ProgId="VLC.m2ts" ApplicationName="VLC media player" />
      <Association Identifier=".m3u" ProgId="VLC.m3u" ApplicationName="VLC media player" />
      <Association Identifier=".m4a" ProgId="VLC.m4a" ApplicationName="VLC media player" />
      <Association Identifier=".m4v" ProgId="VLC.m4v" ApplicationName="VLC media player" />
      <Association Identifier=".mkv" ProgId="VLC.mkv" ApplicationName="VLC media player" />
      <Association Identifier=".mod" ProgId="WMP11.AssocFile.MPEG" ApplicationName="Windows Media Player" />
      <Association Identifier=".mov" ProgId="VLC.mov" ApplicationName="VLC media player" />
      <Association Identifier=".MP2" ProgId="VLC.mp2" ApplicationName="VLC media player" />
      <Association Identifier=".mp3" ProgId="VLC.mp3" ApplicationName="VLC media player" />
      <Association Identifier=".mp4" ProgId="VLC.mp4" ApplicationName="VLC media player" />
      <Association Identifier=".mp4v" ProgId="VLC.mp4v" ApplicationName="VLC media player" />
      <Association Identifier=".mpa" ProgId="VLC.mpa" ApplicationName="VLC media player" />
      <Association Identifier=".MPE" ProgId="VLC.mpe" ApplicationName="VLC media player" />
      <Association Identifier=".mpeg" ProgId="VLC.mpeg" ApplicationName="VLC media player" />
      <Association Identifier=".mpg" ProgId="VLC.mpg" ApplicationName="VLC media player" />
      <Association Identifier=".mpv2" ProgId="VLC.mpv2" ApplicationName="VLC media player" />
      <Association Identifier=".mts" ProgId="VLC.mts" ApplicationName="VLC media player" />
      <Association Identifier=".pcx" ProgId="ImageGlass.AssocFile.PCX" ApplicationName="ImageGlass" />
      <Association Identifier=".pgm" ProgId="ImageGlass.AssocFile.PGM" ApplicationName="ImageGlass" />
      <Association Identifier=".png" ProgId="ImageGlass.AssocFile.PNG" ApplicationName="ImageGlass" />
      <Association Identifier=".ppm" ProgId="ImageGlass.AssocFile.PPM" ApplicationName="ImageGlass" />
      <Association Identifier=".psd" ProgId="ImageGlass.AssocFile.PSD" ApplicationName="ImageGlass" />
      <Association Identifier=".tif" ProgId="ImageGlass.AssocFile.TIF" ApplicationName="ImageGlass" />
      <Association Identifier=".tiff" ProgId="ImageGlass.AssocFile.TIFF" ApplicationName="ImageGlass" />
      <Association Identifier=".TS" ProgId="VLC.ts" ApplicationName="VLC media player" />
      <Association Identifier=".TTS" ProgId="VLC.tts" ApplicationName="VLC media player" />
      <Association Identifier=".txt" ProgId="txtfile" ApplicationName="Notepad" />
      <Association Identifier=".url" ProgId="IE.AssocFile.URL" ApplicationName="Internet Browser" />
      <Association Identifier=".wav" ProgId="VLC.wav" ApplicationName="VLC media player" />
      <Association Identifier=".webp" ProgId="ImageGlass.AssocFile.WEBP" ApplicationName="ImageGlass" />
      <Association Identifier=".website" ProgId="IE.AssocFile.WEBSITE" ApplicationName="Internet Explorer" />
      <Association Identifier=".wm" ProgId="WMP11.AssocFile.ASF" ApplicationName="Windows Media Player" />
      <Association Identifier=".wma" ProgId="VLC.wma" ApplicationName="VLC media player" />
      <Association Identifier=".wmf" ProgId="ImageGlass.AssocFile.WMF" ApplicationName="ImageGlass" />
      <Association Identifier=".wmv" ProgId="VLC.wmv" ApplicationName="VLC media player" />
      <Association Identifier=".WPL" ProgId="WMP11.AssocFile.WPL" ApplicationName="Windows Media Player" />
      <Association Identifier=".xbm" ProgId="ImageGlass.AssocFile.XBM" ApplicationName="ImageGlass" />
      <Association Identifier=".xpm" ProgId="ImageGlass.AssocFile.XPM" ApplicationName="ImageGlass" />
      <Association Identifier="http" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier="https" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
    </DefaultAssociations>

    However, this one does not:

    <?xml version="1.0" encoding="UTF-8"?>
    <DefaultAssociations>
      <Association Identifier=".3g2" ProgId="VLC.3g2" ApplicationName="VLC media player" />
      <Association Identifier=".3gp" ProgId="VLC.3gp" ApplicationName="VLC media player" />
      <Association Identifier=".3gp2" ProgId="VLC.3gp2" ApplicationName="VLC media player" />
      <Association Identifier=".3gpp" ProgId="VLC.3gpp" ApplicationName="VLC media player" />
      <Association Identifier=".aac" ProgId="VLC.aac" ApplicationName="VLC media player" />
      <Association Identifier=".adt" ProgId="WMP11.AssocFile.ADTS" ApplicationName="Windows Media Player" />
      <Association Identifier=".adts" ProgId="VLC.adts" ApplicationName="VLC media player" />
      <Association Identifier=".avi" ProgId="VLC.avi" ApplicationName="VLC media player" />
      <Association Identifier=".bmp" ProgId="ImageGlass.AssocFile.BMP" ApplicationName="ImageGlass" />
      <Association Identifier=".cda" ProgId="VLC.cda" ApplicationName="VLC media player" />
      <Association Identifier=".dib" ProgId="ImageGlass.AssocFile.DIB" ApplicationName="ImageGlass" />
      <Association Identifier=".emf" ProgId="ImageGlass.AssocFile.EMF" ApplicationName="ImageGlass" />
      <Association Identifier=".flac" ProgId="VLC.flac" ApplicationName="VLC media player" />
      <Association Identifier=".gif" ProgId="ImageGlass.AssocFile.GIF" ApplicationName="ImageGlass" />
      <Association Identifier=".htm" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier=".html" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier=".ico" ProgId="ImageGlass.AssocFile.ICO" ApplicationName="ImageGlass" />
      <Association Identifier=".jfif" ProgId="ImageGlass.AssocFile.JFIF" ApplicationName="ImageGlass" />
      <Association Identifier=".jpe" ProgId="ImageGlass.AssocFile.JPE" ApplicationName="ImageGlass" />
      <Association Identifier=".jpeg" ProgId="ImageGlass.AssocFile.JPEG" ApplicationName="ImageGlass" />
      <Association Identifier=".jpg" ProgId="ImageGlass.AssocFile.JPG" ApplicationName="ImageGlass" />
      <Association Identifier=".m2t" ProgId="VLC.m2t" ApplicationName="VLC media player" />
      <Association Identifier=".m2ts" ProgId="VLC.m2ts" ApplicationName="VLC media player" />
      <Association Identifier=".m3u" ProgId="VLC.m3u" ApplicationName="VLC media player" />
      <Association Identifier=".m4a" ProgId="VLC.m4a" ApplicationName="VLC media player" />
      <Association Identifier=".m4v" ProgId="VLC.m4v" ApplicationName="VLC media player" />
      <Association Identifier=".mka" ProgId="VLC.mka" ApplicationName="VLC media player" />
      <Association Identifier=".mkv" ProgId="VLC.mkv" ApplicationName="VLC media player" />
      <Association Identifier=".mod" ProgId="WMP11.AssocFile.MPEG" ApplicationName="Windows Media Player" />
      <Association Identifier=".mov" ProgId="VLC.mov" ApplicationName="VLC media player" />
      <Association Identifier=".MP2" ProgId="VLC.mp2" ApplicationName="VLC media player" />
      <Association Identifier=".mp3" ProgId="VLC.mp3" ApplicationName="VLC media player" />
      <Association Identifier=".mp4" ProgId="VLC.mp4" ApplicationName="VLC media player" />
      <Association Identifier=".mp4v" ProgId="VLC.mp4v" ApplicationName="VLC media player" />
      <Association Identifier=".mpa" ProgId="VLC.mpa" ApplicationName="VLC media player" />
      <Association Identifier=".MPE" ProgId="VLC.mpe" ApplicationName="VLC media player" />
      <Association Identifier=".mpeg" ProgId="VLC.mpeg" ApplicationName="VLC media player" />
      <Association Identifier=".mpg" ProgId="VLC.mpg" ApplicationName="VLC media player" />
      <Association Identifier=".mpv2" ProgId="VLC.mpv2" ApplicationName="VLC media player" />
      <Association Identifier=".mts" ProgId="VLC.mts" ApplicationName="VLC media player" />
      <Association Identifier=".pcx" ProgId="ImageGlass.AssocFile.PCX" ApplicationName="ImageGlass" />
      <Association Identifier=".pgm" ProgId="ImageGlass.AssocFile.PGM" ApplicationName="ImageGlass" />
      <Association Identifier=".png" ProgId="ImageGlass.AssocFile.PNG" ApplicationName="ImageGlass" />
      <Association Identifier=".ppm" ProgId="ImageGlass.AssocFile.PPM" ApplicationName="ImageGlass" />
      <Association Identifier=".psd" ProgId="ImageGlass.AssocFile.PSD" ApplicationName="ImageGlass" />
      <Association Identifier=".tif" ProgId="ImageGlass.AssocFile.TIF" ApplicationName="ImageGlass" />
      <Association Identifier=".tiff" ProgId="ImageGlass.AssocFile.TIFF" ApplicationName="ImageGlass" />
      <Association Identifier=".TS" ProgId="VLC.ts" ApplicationName="VLC media player" />
      <Association Identifier=".TTS" ProgId="VLC.tts" ApplicationName="VLC media player" />
      <Association Identifier=".txt" ProgId="txtfile" ApplicationName="Notepad" />
      <Association Identifier=".url" ProgId="IE.AssocFile.URL" ApplicationName="Internet Browser" />
      <Association Identifier=".wav" ProgId="VLC.wav" ApplicationName="VLC media player" />
      <Association Identifier=".webp" ProgId="ImageGlass.AssocFile.WEBP" ApplicationName="ImageGlass" />
      <Association Identifier=".website" ProgId="IE.AssocFile.WEBSITE" ApplicationName="Internet Explorer" />
      <Association Identifier=".wm" ProgId="WMP11.AssocFile.ASF" ApplicationName="Windows Media Player" />
      <Association Identifier=".wma" ProgId="VLC.wma" ApplicationName="VLC media player" />
      <Association Identifier=".wmf" ProgId="ImageGlass.AssocFile.WMF" ApplicationName="ImageGlass" />
      <Association Identifier=".wmv" ProgId="VLC.wmv" ApplicationName="VLC media player" />
      <Association Identifier=".WPL" ProgId="WMP11.AssocFile.WPL" ApplicationName="Windows Media Player" />
      <Association Identifier=".xbm" ProgId="ImageGlass.AssocFile.XBM" ApplicationName="ImageGlass" />
      <Association Identifier=".xpm" ProgId="ImageGlass.AssocFile.XPM" ApplicationName="ImageGlass" />
      <Association Identifier="http" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
      <Association Identifier="https" ProgId="ChromeHTML" ApplicationName="Google Chrome" />
    </DefaultAssociations>

    The only difference between the two files? These two lines added to the non-working version:

    <Association Identifier=".cda" ProgId="VLC.cda" ApplicationName="VLC media player" />
    <Association Identifier=".mka" ProgId="VLC.mka" ApplicationName="VLC media player" />

    That is the difference between a config that doesn't immediately give the user a popup that says the default program for .png files was reset to paint, and one that does. It is complete insanity.

    The even crazier part? The popup notifications are a lie. It doesn't actual reset anything! It continues to work fine with the correctly set default app associations!

    By the way, this is all with a plain 1809 LTSC install with no updates. As soon as you install the latest updates, there is nothing you can do to avoid the app reset notification regarding your browser being reset to Internet Explorer (which is also a lie).

    So I finally resorted to using the SetUserFTA tool available elsewhere on the internet that I setup to run on the User's first login and set their defaults then. That actually worked quite well...until I installed updates from the stock 1809 LTSC install. At which point as soon as you download a random .jpg, .mp3, .mp4, etc. You'll immediately get a popup about an app reset for that specific file extension...and it's still a lie since nothing has actually been reset.

    Another interesting thing, when I'm creating a bunch of users to test the new user popup experience, sometimes I'll create a user and everything will be fine with no popups. Then I'll create another user and they'll get multiple popups without me changing a single thing. There is no rhyme or reason to this and it is complete madness.

    One of the things that irks me the most: the logs are lying to you!

    The event log might say "User choice has been reset to prog id PBrush for .png" but in reality, nothing was actually reset and the issue has nothing to do with Paint or .png file. And the popup notifications that says "An App caused a problem" Give me a break! What app? What problem? What exactly did this app do? I'm sorry that trying to import an default-appassociations XML exported file from this exact same Windows version with the exact same applications is causing issues for you!

    This has been the last straw for me. I was alright trying to keep up with Microsoft's once-every-six-month new OS versions before this but now I'm done. I'm deploying LTSC everywhere and I'll reevaluate in 2021 or whenever a new LTSC version comes out. 

    I'm now trying to decide if I need to either find a way to block all Windows notifications by default or ship our MDT task sequence with August updates before it seems like everything disintegrated.

    Wednesday, November 6, 2019 1:36 AM
  • Has anyone had any success? I am still having this issue. Sometimes, the computer gets to unresponsive that I can't do basic things. Internet Explorer won't open, the search function won't work, sfc /scannow errors out and won't run. 

    How is this a "stable" build? I don't understand what is going on. This is crazy.

    I seriously need to find a solution because LTSB 2016 is no longer support on new Laptop parts.

    Thursday, November 7, 2019 8:23 PM
  • Unfortunately, the link didn't help. Within the article itself it has a "Update" 1809 and later, this fix doesn't work." Which applies to this LTSC.

    Are there different versions of LTSC? If I don't have to use 1809/1903, that would be FANTASTIC.

    Thursday, November 7, 2019 8:26 PM
  • Any luck? what did you find? Have you found a solution?
    Thursday, November 7, 2019 8:27 PM
  • I am, yes, but I also tested an Unattend.xml that didn't have it, problem persisted.
    Thursday, November 7, 2019 8:27 PM
  • For what its worth, I was able to obtain a Windows 10 Enterprise ISO with all the updates through October.  I installed, removed all the apps using powershell command get-appxpackage -allusers|remove-appxpackage.  I paused updates so n new updates could install, and I disabled the store using gpedit.msc.

    I ran sysprep, with the copy profile option, and at first logon I get the app reset message.  Note: the only thing installed was Windows 10.  No other apps were installed.

    Friday, November 8, 2019 5:12 PM
  • Man, that is crazy broken!

    Is there ANYONE who uses LTSC 2019 (1803/1809/1903) joined to a domain in an Enterprise environment and it work as well as LTSB?

    Friday, November 8, 2019 5:30 PM
  • I think this happens when a local profile is present and the computer is sysprepped?
    Friday, November 8, 2019 7:51 PM
  • The only local profile that is enabled is the built-in administrator account.  The account I am force to created during the Windows 10 installation is disabled.
    Friday, November 8, 2019 9:35 PM
  • Dear young men, a respectful greeting to all of you ...
    I have been, until today, a strong reader of the forum, I have decided only now to write and to contribute in the merit of the question Sysprep / default app.

    Obviously I find in Windows 10 1903, the same problem as the default app reset .....
    I found (looking for 2 weeks) this article, which is a little dated but could be useful for some starting point or workaround.

    https://blogs.technet.microsoft.com/windowsinternals/2017/10/25/windows-10-how-to-configure-file-associations-for-it-pros/


    I stay in "listening" .....


    • Edited by kgiammy Monday, November 11, 2019 10:34 AM
    Monday, November 11, 2019 10:30 AM
  • Hi Tipps

    I am looking at this again tonight. I had to put it down and move onto something else. But am back looking at it tonight.

    We only use LTSC 2019 and it works well. The image I created for deploying our physical estate was in the first half of the year and it doesn't have the "App reset" problems. Its only with the recent updates that there has been an issue and these don't affect our current users because, in the original image I didn't use "CopyProfile" in the xml.

    Also, if any users did have the problem, its likely its not a reoccuring problem. ie in my testing, once I have logged in and all the "App Resets" have occurred. They don't reoccur on subsequent logins.

    The reason I am pursuing the problem is because I need to create an image for a Non-Persistant VDI desktop with a mandatory profile. So I have used the "Copy profile" in the xml, so the mandatory profile I set up can be more efficient.  I could look at using DefProf instead of the MS solution....but it just really bugs me when standard stuff doesn't work.

    In your image development are you using the "Copyprofile" option in the unattend.xml?

    Monday, November 11, 2019 4:47 PM
  • Thanks kgiammy, I had seen that article previously. It does have useful information. Unfortunately doesn't fix the issue and the cause referenced in the article isn't relevant to my problem. My testing is with a clean LTSC 2019 os and no apps.
    Monday, November 11, 2019 4:52 PM
  • It seems like there are two issues occurring simultaneously.

    1) The normal 1903/1809 Windows 10 Pro is broken and receiving app result popups starting on the Sept Cumulative updates after deploying with MDT or similar, importing a defaultappassociations .xml file, and logging in as a new user.

    2) The 1809 LTSC appears to have the default app reset notifications appear after working with any specific extension for the first time, such as downloading a .jpg file.

    Issue 2 can be resolved like this:

    Use the third-party tool SetUserFTA to set user default app associations with a login script. ALSO, manually run the SetUserFTA tool for the SYSTEM user. This will stop the popups since the popups are actually for the SYSTEM user having its app associations reset, not the user you are testing.

    I can't include links so just Google for "SetUserFTA" and look for the kolbi cz blog from the dev.

    /blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/

    See the note from the developer (Ctrl+F search for "NOVEMBER 7, 2019 AT 7:42 PM") where he pointed out that these app reset notifications are for the SYSTEM user.

    Now the fact that the SYSTEM user is having its app associations reset and then the popups are showing up for any other user? You'll have to ask Microsoft about that one...

    Monday, November 11, 2019 7:40 PM
  • Sorry .... I resume my previous post with 2 lines ....

    I performed the sysprep test (Win 10 Pro - 1903 updated to date) using, as indicated in the link I posted earlier, the DISM command .....

    In the default app I set the default browser "internet explorer" and then "adobe reader" to manage files with pdf extension.
    I created the "temp" folder on disk C and then executed ...

    1) Dism.exe / online /export-defaultappassociations:C:\temp\CustomFileAssoc.xml

    and immediately after
     2) Dism.exe / online / import-defaultappassociations:C:\temp\CustomFileAssoc.xml

    done this, I launched the sysprep command
    and all the rest (/ generalize / oobe / shutdown unattend: etc etc ....)

    The system after reboot (post sysprep) still continues to report
    ".... An App Default Was Reset ......" at least 12 times ....
    HOWEVER
    I can assure you that in my case Internet explorer remains DEFAULT BROWSER and ADOBE READER default app for PDFs.

    I hope I was helpful.....

    Greetings and health .....
    Tuesday, November 12, 2019 11:03 AM
  • kgiammy,

    Could you see if you have the same issue prior to updating to a September, October, or (now) November cumulative update? I think something affecting these notifications was broken in every Cumulative update during and since September. I also think I spoke too soon in my previous message regarding SetUserFTA. I think the issue still might be present even after doing what I mentioned if you update to a recent cumulative update. I'm still testing this though.

    Could you also clarify if you experience any issues without importing any default app associations XML file? If you don't configure that at all, do you still see the "An app default was reset" message?

    Tuesday, November 12, 2019 9:36 PM
  • Glad it is not just me experiencing this. Experiencing exactly the same issue when building images for my large corporation.

    If you are installing 1903 with any cumulative update from September 2019 or later you will be afflicted by this. I have spent ages trying to solve it with no success - you will receive about 20 file association reset notifications the first time any new user logs in (nothing actually gets reset!)

    I did the following tests

    1. Install a fresh 1903 from the v1 iso (so only up to date to April 2019)

    2. Put into audit mode

    3. immediately sysprep without touching anything (generalise/oobe) with CopyProfile set to true

    4. works fine

    Then I repeated the above but after step 2 I installed the latest cumalative update and then carried on with steps 3 & 4 

    The result is the reset notifcations. So they broke something and have yet to fix it...

    Incidentally I have obtained the 1909 ISO and repeated the above but the issue is still there so sadly they have not resolved this issue even with the latest shiniest version of Windows 10. I hope something is done to fix this soon because frankly it just looks like amateur hour when my clients log in for the first time on brand new machines.

    Saturday, November 16, 2019 9:33 PM
  • So I am also trying to update our district image. Coming from 1809 and trying to upgrade to 1909. Like everyone else has said I've tried everything suggested. I did some additional testing with just a bare OS (no updates) and 1909 still nags the user with 13 app reset notifications on first login. This is a problem for us because we have thousands of student that are going to experience this every time they log into a new computer and students rotate computers a lot.

    When I remove the "CopyProfile" flag from my sysprep file the problem goes away, but this is not a solution for us. We use the Copy Profile for back ground preferences, app preferences etc.

    So now what? Do we go back to 1903 and not update it? Come on Microsoft this is a big problem. Please direct some resources to this to get it fixed.


    • Edited by Hoof-Arted Monday, November 18, 2019 3:59 PM
    Monday, November 18, 2019 3:58 PM

  • When I remove the "CopyProfile" flag from my sysprep file the problem goes away, but this is not a solution for us. We use the Copy Profile for back ground preferences, app preferences etc.

    I'm pretty stuck too, trying to come up with an idea that doesn't need "CopyProfile" since this has been a sore spot on Sysprep for literally years now.  But fixing this very useful function would be best.  It seems dumb to create workarounds and hacks to deal with CopyProfile malfunctions.
    Monday, November 18, 2019 5:43 PM
  • This sounds tedious, but I never use copyprofile.  Usually with sysinternals procmon and the filter "category = write", I can figure out a simple file or registry change to script what's necessary.  My default profile is 3 megs.

    • Edited by JS2010 Monday, November 18, 2019 5:52 PM
    Monday, November 18, 2019 5:51 PM
  • Can you provide more detail on the process you are using, instead of using copyprofile?  I use copyprofile, so when a new user logs in, they get the correct desktop, and the correct bookmarks for Internet Explorer, Firefox, and Chrome.
    Monday, November 18, 2019 9:12 PM
  • @zeb2100

    I know about the SetupComplete.cmd script that runs after the first user logs in.  I'm already using this mechanism to do some specific per-machine tweaking.  Specifically, at the moment, I use it to grow the 'OS' partition to fill the target computer's drive, regardless of it's size.  I generate all my images on a 50GB HDD image, so this comes in handy, and no need to have technicians manually go in and resize the partitions after deployments.

    I'm probably going to be investigating doing everything from that script that I normally use 'CopyProfile' to handle.  It's going to be more work to fine tune the script, but I guess once it's done, I can forget about 'CopyProfile' for the forseeable future.  Tired of coming back to issues with it again and again.

    Here's the two scripts I use presently:

    SetupComplete.cmd:

    @echo off
    bcdedit /timeout 3
    set LOCALAPPDATA=%USERPROFILE%\AppData\Local
    set PSExecutionPolicyPreference=Unrestricted
    powershell "%systemdrive%\Windows\ComputerCorps\ResizeOSPartition.ps1"

    ResizeOSPartition.ps1:

    Write "Resizing OS Partition to fill remaining disk, please wait..."
    $Partition = Get-Volume -FileSystemLabel "OS" | Get-Partition
    $NewSize = (Get-PartitionSupportedSize -InputObject $Partition).sizeMax
    Resize-Partition -InputObject $Partition -Size $NewSize
    Write "Done."

    • Edited by Chetar Ruby Monday, November 18, 2019 9:20 PM
    Monday, November 18, 2019 9:18 PM
  • There's various ways to set preferences in each browser.  Chrome has a master_preferences file.  Firefox has a mozilla.cfg file.  There's probably a way to set the wallpaper with group policy.  I just overwrite c:\windows\WEB\wallpaper\Windows\img0.jpg.  I don't normally set bookmarks, just the homepage.  I use group policy to set the IE homepage.
    • Edited by JS2010 Monday, November 18, 2019 9:28 PM
    Monday, November 18, 2019 9:23 PM
  • Can you try the latest update on 1903 to see if the issue still persists? https://support.microsoft.com/en-us/help/4498140 

    You would need to update image before running sysprep copyprofile and testing. 



    Monday, November 18, 2019 10:22 PM
  • Can you try the latest update on 1903 to see if the issue still persists?

    You would need to update image before running sysprep copyprofile and testing. 



    1903 unpatched from the ISO works, but if you run Windows Updates inside audit mode it breaks. 1909 is broken in the ISO.

    So our only option is to currently build an unpatched 1903 image and hope MS fixes this because we cannot move to 1909 at the moment.

    Tuesday, November 19, 2019 2:21 PM
  • I just tested a Windows 10 Enterprise version 1909 image.  It has no updates, and only the operating system is installed.  If copyprofile is true, and I run sysprep, I get the default app messages.  If copyprofile is set to false, then I don't get any default app message.

    As I had mentioned before, we use copyprofile so all desktops get the same settings when a use logs in.  

    Wednesday, November 20, 2019 5:55 PM
  • I'm experiencing the same problem with Windows 10 1909.  I also started off with a fresh install with Office 2016.  No updates or tweaks were made and copyprofile was not used.  What I noticed was the first logon(Domain User) I didn’t get any default app messages.  Once another user logged on the messages started to appear.  It’s the same message, 5 or 6 all Microsoft Edge.

    Thursday, November 21, 2019 9:01 PM
  • I found this temporary band-aid but by no means is it a fix, it just stops the annoying messages and sound.

    https://blogs.technet.microsoft.com/platforms_lync_cloud/2017/05/05/disabling-windows-10-action-center-notifications/

    I have no idea if this will lead to other issues, but if you use the  "Disable Settings Notifications" via Group policy it does work.
    Thursday, November 21, 2019 9:46 PM
  • I did some more tests last week and only now read this latest post from MCRBHS,

    I believe that:
    The problem seems to be generated by the "Windows Welcome Screen" function that appears every time a new user / profile is started.
    In my case, before the sysprep was launched, I:

    1) through the policy settings I have disabled the first run of the edge browser
    2) I, manually, from the "settings -> Notifications & actions" menu, deactivating all notifications … ( disable Windows welcome screen )
    3) I then launched DISM import / export commands ... as from previous posts ....
    4) I then executed the sysprep / generalize ......... /unattend.xml (copyprofile: true)

    upon reboot there is no "app default reset" error and the apps set as default before the sysprep are kept .....

    Thank you all….

    Friday, November 29, 2019 12:14 PM
  • I looked at the policy settings to disable the first run of the edge browser, and I am not seeing it.  Can you give me the specific setting that you changed?  Thanks.
    Monday, December 2, 2019 6:39 PM
  • It looks like this procedure worked for me.  I kept the copyprofile option in sysprep to true.  I disabled the first run of the edge browser, and I deactivated all notifications.  I also created a default app associations file, using dism, and the group policy that sets the default associations file.  The computer did not have any messages when it logged in the first time, and no messages appeared when I joined the computer to the domain, and logged in with a domain account.
    Tuesday, December 3, 2019 5:31 PM
  • I didn't like the solution that consist of disabling all notifications.

    I spent some hours of testing and just like all of you the copy profile cause de notifications.

    I ended up editing the ntuser.dat of default profile to customize the user desktop/experience disable copy profile and voila :)

    This is just a workaround and not a viable solution.

    Regards


    • Edited by FLW System Thursday, December 12, 2019 2:36 PM
    Thursday, December 12, 2019 2:35 PM
  • Can you try the latest update on 1903 to see if the issue still persists? > 

    You would need to update image before running sysprep copyprofile and testing. 




    Anyway you can provide anymore insight into when this will be addressed from Microsoft? We are kind of stuck without an upgrade path currently as we need the "CopyProfile" feature to work AND the notifications to not be turned off.
    • Edited by Hoof-Arted Monday, December 16, 2019 8:11 PM
    Monday, December 16, 2019 8:06 PM
  • tinfever - your post blew me away. Especially this part:

    "Another interesting thing, when I'm creating a bunch of users to test the new user popup experience, sometimes I'll create a user and everything will be fine with no popups. Then I'll create another user and they'll get multiple popups without me changing a single thing. There is no rhyme or reason to this and it is complete madness."

    I hate to say it but I am glad I am not alone :-)

    I also feel bad for my customer because I kept coming back to them with the same news - we aren't there just yet. Each time when I thought I made some progress, something else broke. I also went down that road with SetUserFTA (customer has VDI environment) but lately UEM/DEM fixed it in the earliest release so as long as I can bypass the Default App Reset issue I can declare the official "win"!

    Here's the deal - I have one pool in one site (VDI pool) and I'd send a local user to test the session. He tells me how he gets all these annoying notifications about Default App Reset. That was my most recent "test pool". Then another user (same domain level user - another domain admin) logs in and he's like - I don't get any! Then I'd login and get the notifications. 

    Also, another pool that's been "calm" is the pool where I had the entire Settings-Apps-Default apps window crashing upon trying to pick the Music Player of Video Player and select Windows Media Player or VLC. The entire settings window just goes crashing with the application log saying how the fault is on immersive control panel and settings.exe process. Well, go figure... 

    Then I logged onto completely different environment for another customer that's running a 20k user VDI environment while trying to look into something completely not related to this and I got the App Default Reset message upon logging into their VDI session. I just "gulped" and don't want to write what I said out loud :-)

    Anyhow - I am opening a ticket with MSFT as soon as I see my Contract ID on my Partner Login. I just activated it yesterday and it says up to 3 business days to show up so I will be posting my findings on each thread I commented on.

    Thank you for reading my thoughts! Sorry I don't have any resolution but I just wanted to share my experiences. I posted my original issue here with the full application log error and what happened after I did sysprep with copyprofile.

    https://social.technet.microsoft.com/Forums/en-US/772dc4b2-d074-49a8-856e-bf23f3c43d05/brand-new-install-of-1903-or-1909-immersive-control-panel-issues?forum=win10itprogeneral

    Cheers!

    Zack


    Friday, December 20, 2019 4:07 AM
  • Hi Zack, Did you have any joy with MSFT?  I too have this issue :/

    Monday, January 6, 2020 8:36 PM
  • This is absolutely driving me nuts!!!  I'm having these exact same issues and I've tried all the suggestions i've compiled from all across the web but this error completly breaks the build!

    Where is the fix MS?!?!?!  I need to use the built in CopyProfile and Start/task layout customizations to deploy all of my 5 base master images to transition us from win7 to 1809 LTSC 2019 and it needs to work NOW!  Time is up!  Im beyond purturbed at the state of this issue and the inordinate amount of time thats been WASTED trying to fix this.

    Thursday, January 9, 2020 6:19 PM
  • Is there any progress on getting a fix for this?  I'm still forced to generate images with a 1903 ISO because 1909 vomits the default app reset messages with CopyProfile.  I really need this to work again.

    Thursday, January 9, 2020 6:45 PM
  • Hmm, it looks like under all of these registry keys (powershell)


    get-item hkcu:\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\*\UserChoice

    get-item hkcu:\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\*\UserChoice |
      % name

    There's a property called "Hash".  Probably after a sysprep,  the hash gets invalid and has to be reset.  Maybe there's some way to delete all these UserChoice keys before sysprepping, and that would fix the problem?  I tried the extreme action of deleting the whole FileExts key (loading the hive under a different account), which FileExts key doesn't exist under the Default profile.  And after a sysprep, the App Reset messages didn't come back.  But I'm not sure how harmful this is.  

    By the way, all this stuff is logged under Logname 


    Microsoft-Windows-Shell-Core/AppDefaults


    in the Event Viewer.  


    Here's a way to search all the logs in powershell.  The event viewer gets errors about too many possible results.  I originally searched for "png" in log messages.


    Get-WinEvent -ListLog * -ea 0 | 
    foreach { get-winevent -filterhashtable @{logname=$_.logname;
    starttime='2:45 pm'; endtime='3:45 pm} -ea 0 } |
    where message -match 'User choice has been reset to'


       ProviderName: Microsoft-Windows-Shell-Core

    TimeCreated                     Id LevelDisplayName Message
    -----------                     -- ---------------- -------
    1/9/2020 3:30:05 PM          62441 Information      User choice has been reset to prog id AppX6eg8h5sxqq90pv53845wmnbewywdqq5h for .mp4
    1/9/2020 3:30:05 PM          62441 Information      User choice has been reset to prog id AppX6eg8h5sxqq90pv53845wmnbewywdqq5h for .mp4
    1/9/2020 3:30:05 PM          62441 Information      User choice has been reset to prog id AppX6eg8h5sxqq90pv53845wmnbewywdqq5h for .avi
    1/9/2020 3:30:05 PM          62441 Information      User choice has been reset to prog id AppX6eg8h5sxqq90pv53845wmnbewywdqq5h for .avi


    I don't understand why these UserChoice keys get created.  In my case, I've never used the Settings app once to set the defaults.

    • Edited by JS2010 Friday, January 10, 2020 12:49 PM
    Thursday, January 9, 2020 9:16 PM
  • I have been battling with these app reset for a while now.  There is a couple things I noticed.   I’m using Windows 10 1909 with the latest patches.  I didn’t make any modifications, remove any apps or even set default app associations.

    It’s always the same errors.

    • Ms-xbl-3d8b930f
    • Microsoft-edge-holographic
    • Microsoft-edge
    • Default browser setting

    This only happens for new users who haven’t logged on the machine before.  If it doesn’t happen for the first user the errors will start to appear after 2nd or 3rd.

    I carried out a couple of test with different CPU configurations.  All the same accounts were used.
    2 CPU cores - I didn’t get any errors
    4 CPU cores – hit or miss, the errors do appear but not all the time
    8 CPU cores – consistently get the errors after login

    It just doesn’t make sense..

    Tuesday, January 14, 2020 7:55 PM
  • Hi,

    This is driving me crazy too, I have spent many days on this issue!

    If I install a vanilla version of Windows 10 Education x64 1903 or 1909 I get the same four Notifications when a network user logs on. This is without any software installed or Windows updates applied.

    It’s always the same errors.

    • Ms-xbl-3d8b930f files
    • Microsoft-edge-holographic files
    • Microsoft-edge files
    • Default browser setting

    I can find no solution to this, surely Microsoft needs to address this issue.

    Thanks,

    Matt


    Wednesday, January 15, 2020 12:26 PM
  • One of Microsoft's support engineer was able to reproduce the app reset message after switching to an 8 core virtual machine.  I don't know why switching to a higher cpu core count the app reset message appear is beyond me.  Btw, this also happens to local accounts but only after a network user logs in and starts to get the app reset messages.

    Waiting to hear back from Microsoft on a fix or directions on how to resolve this issue.


    • Edited by Matt L_ Thursday, January 16, 2020 7:36 PM spelling
    Thursday, January 16, 2020 7:28 PM
  • I don't know why it would be so hard to reproduce.  Login and create a profile, sysprep, then login again.

    • Edited by JS2010 Thursday, January 16, 2020 8:43 PM
    Thursday, January 16, 2020 8:42 PM
  • We've suspected for some time that there is a timing issue somewhere - the faster (or more cores) a device is, the higher the probability that the error is seen.

    Let's hope very much that someone with a Microsoft support entitlement can get this fixed...

    Friday, January 17, 2020 6:32 PM
  • Anything new yet? We have the same issue. Opened a case with MS and so far nothing they suggested has helped.
    Monday, February 10, 2020 7:53 PM
  • Anything new yet? We have the same issue. Opened a case with MS and so far nothing they suggested has helped.
    Yeah... I don't understand the absence of a response on this. I guess we are just skipping the 1909 update? Maybe they will have a fix in 20H1.
    Tuesday, February 11, 2020 12:21 PM
  • I thought I was close in solving this issue but the support engineer went on vacation for two weeks.  Now its back to the other engineer can't reproduce the issue.
    Wednesday, February 12, 2020 4:28 PM
  • Hi Matt_L

    Might be worth copying to your engineer a link to this thread. This problem is a big issue and they simply need to try harder!  It's not difficult to reproduce.

    TheDude

    Thursday, February 13, 2020 2:03 PM
  • Hello,

    I'm french :)

    Here is an extract from a link I can't post (I've got a non verifyed profile whereas I've got my account since 2014...)

    "Some user profile settings, including Default Apps, are encrypted by using a hash that is specific to the user. If you copy these settings to another user profile, Windows treats them as invalid and resets them the first time that the user signs in. Windows does not support using CopyProfile to copy these settings.

    Serious problems might occur if you modify the registry incorrectly. Before you modify it, backup the registry for restoration in case problems occur.

    When you prepare the source user profile, delete the following registry entries:

    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\FileAssociationsUpdateVersion
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations

    If these entries do not exist, Windows loads the normal Default Apps settings from the oemdefaultassociations.xml file when the user signs in to Windows for the first time."...

    Does it help?

    • Proposed as answer by TechieGeezer Thursday, February 13, 2020 10:13 PM
    Thursday, February 13, 2020 8:37 PM
  • "Some user profile settings, including Default Apps, are encrypted by using a hash that is specific to the user. If you copy these settings to another user profile, Windows treats them as invalid and resets them the first time that the user signs in. Windows does not support using CopyProfile to copy these settings.

    Serious problems might occur if you modify the registry incorrectly. Before you modify it, backup the registry for restoration in case problems occur.

    When you prepare the source user profile, delete the following registry entries:

    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\FileAssociationsUpdateVersion
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations

    If these entries do not exist, Windows loads the normal Default Apps settings from the oemdefaultassociations.xml file when the user signs in to Windows for the first time."...

    Comes from this link

    https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/customize-the-default-user-profile-by-using-copyprofile

    info was added on Jan 17th 2020

    Thursday, February 13, 2020 10:21 PM
  • Exact but I was not allowed to post the link ;)

    Thank you @TechieGeezer


    Friday, February 14, 2020 6:34 AM
  • A quick update on the support ticket with Microsoft...

    We basically started from scratch. 

    • Loaded the SW_DVD9_Win_Pro_10_1909_64BIT_English_Pro_Ent_EDU_N_MLF_X22-17395.ISO into SCCM.
    • Created a Build and Captured TS.  No tweaks, apps or anything was added.
    • Loaded the WIM into SCCM
    • Imaged a VM with the imported WIM
    • App resets started to occur after the second login for both domain and local users.

    • Captured procmon bootlog on a 8 cpu core VM.  Errors occured
    • Captured procmon bootlog on a 2 cpu core VM.  No errors.  

    The engineer will be analyzing the logs and hopefully they can find something.

    CopyProfile was never used..

    Friday, February 14, 2020 6:59 PM
  • Thanks for the update Matt L_  - well done.

    Our recreation scenario, if it helps:

    • Install fresh 1909 into audit mode using CTRL-SHIFT-F3
    • (Either capture and download or stay on same hardware, or virtual hardware)
    • Sysprep with no modifications (so no copyprofile)

    This is the same result as using an extensively built image using DISM association import and export (but still no copyprofile).

    We can get a 2 core VM to show the issue if the machine has had time to do some of its background tasks and settle down (e.g. store updates, .net stuff) - this might take leaving it for a day or so. Anyway, the quicker the logon time then the more likelihood of the issue occurring, as far as we can see.

    Friday, February 14, 2020 10:49 PM
  • Hey, did you come up with any answers from the MS Engineer as to the how/why/workarounds for this issue?
    Wednesday, February 19, 2020 5:46 PM
  • Hoping that Microsoft has a work around for this issue? Currently have the new 1909 image ready for deployment with new hardware but getting this popup when users log in is a show stopper currently. 
    Thursday, February 20, 2020 3:20 PM
  • I haven't heard of anything yet.  Its only been a couple days.  

    The workaround I'm using is to disable or turn off the "Settings" Notification for new users.  All other notification should still get pushed to the action center.

    reg load "hku\Default" "C:\Users\Default\NTUSER.DAT"
    reg add "hkey_users\default\Software\Microsoft\Windows\CurrentVersion\Notifications\Settings\windows.immersivecontrolpanel_cw5n1h2txyewy!microsoft.windows.immersivecontrolpanel" /v "Enabled" /t "REG_DWORD" /d 0 /f
    reg unload "hku\Default"

    Thursday, February 20, 2020 5:14 PM
  • This same thing is happening to me After an 1809 > 1909 upgrade, using a 1909 ISO to upgrade. In 1809, I change some regional settings Under the Administrator account and add keyboard inputs, then copy those settings to the Welcome Screen, system accounts, and new users. It worked fine up until 1909. The upgrade goes through with no issues, but when you log in as a domain user, you get spammed by the default app reset message. It's very annoying and I hope there is a fix soon. Anyone else run into this with upgrades?
    Sunday, February 23, 2020 6:38 PM
  • Hello,

    I'm french :)

    Here is an extract from a link I can't post (I've got a non verifyed profile whereas I've got my account since 2014...)

    "Some user profile settings, including Default Apps, are encrypted by using a hash that is specific to the user. If you copy these settings to another user profile, Windows treats them as invalid and resets them the first time that the user signs in. Windows does not support using CopyProfile to copy these settings.

    Serious problems might occur if you modify the registry incorrectly. Before you modify it, backup the registry for restoration in case problems occur.

    When you prepare the source user profile, delete the following registry entries:

    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\FileAssociationsUpdateVersion
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations

    If these entries do not exist, Windows loads the normal Default Apps settings from the oemdefaultassociations.xml file when the user signs in to Windows for the first time."...

    Does it help?

    For what it's worth, I tried doing this today. I deleted these registry keys Under the local admin account prior to doing a copyprofile. Then I upgraded Windows to 1909 and still got the errors upon logging in with a domain account.
    Monday, February 24, 2020 7:21 PM
  • I heard back from the engineer and its a known issue or bug.  No ETA on the fix...  They were able to reproduce it in house.
    Tuesday, February 25, 2020 4:10 PM
  • I heard back from the engineer and its a known issue or bug.  No ETA on the fix...  They were able to reproduce it in house.
    If they ever provide you with a fix, please share it here. I wish I found this thread before hours of troubleshooting, but such is life.
    Thursday, February 27, 2020 12:59 AM
  • I've tried this another way. We're using Windows 10 Enterprise LTSC 1809 with all latest Windows updates installed (tried with and without apps installed, doesn't make a difference, both give app reset messages) and building a mandatory profile solution. I also ran into the same problem, suddenly. A month ago I made a test profile without any problems.

    But I've tried most of the things in this thread. Except this particular solution. Another user (EDubsWindoze) tried this solution prior doing the copyprofile. Well, I did this AFTER doing the copy profile and editing the ntuser.dat. I removed all those things and voila, now it works without any app default reset messages on logging in.

    I'm going to do another test run in setting up a new clean mandatory profile to see if it's really working fine now.

    Edit: tested with a new clean mandatory profile, confirmed working as well
    • Edited by Genivos Friday, February 28, 2020 3:22 PM
    Friday, February 28, 2020 2:46 PM
  • Hello,

    I'm french :)

    Here is an extract from a link I can't post (I've got a non verifyed profile whereas I've got my account since 2014...)

    "Some user profile settings, including Default Apps, are encrypted by using a hash that is specific to the user. If you copy these settings to another user profile, Windows treats them as invalid and resets them the first time that the user signs in. Windows does not support using CopyProfile to copy these settings.

    Serious problems might occur if you modify the registry incorrectly. Before you modify it, backup the registry for restoration in case problems occur.

    When you prepare the source user profile, delete the following registry entries:

    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\FileAssociationsUpdateVersion
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
    • HKEY_CURRENT_USER\Software\Microsoft\Windows\Shell\Associations\UrlAssociations

    If these entries do not exist, Windows loads the normal Default Apps settings from the oemdefaultassociations.xml file when the user signs in to Windows for the first time."...

    Does it help?

    Apologies, my previous reply was about the above registry keys. Somehow I didn't quote it.
    Friday, February 28, 2020 2:51 PM
  • Found this thread after opening a support ticket with MS. They gathered my info and checked out my test machine and are going to do some work on their end and get back to me.

    I've tried a very basic test of using a Windows 1909 Enterprise from our VLSC and installed it manually on a desktop (no unattended, no domain, no GPOs, etc). I am not customizing a default user or using sysprep and copyprofile.

    Steps and results

    1. Install Windows 10 onto an HP Z230 SFF desktop.

    2. Login with local administrator account changed the web browser to use Internet Explorer as the default app via the Settings>Default Apps

    4. Ran DISM to export the new xml file (IEOnlyDefaultAppAssoc.xml)

    5. Ran DISM to import the IEOnlyDefaultAppAssoc.xml file.

    6. Login with a new non-admin account (first account usually doesn't get any notifications)

    7. Login with a 2nd new non-admin account.

    7. This account gets 5 notifications in the action center that an app was reset. The notification are for Ms-xbl-3d8b930f, Microsoft-edge-holographic, Microsoft-edge, and a couple for the default
    browser.

    This app reset issue even occurs without using the copyprofile. 

    Friday, February 28, 2020 10:26 PM
  • If you follow Microsoft's instructions for building a Win10 1909 image, and set CopyProfile to true, you will get app reset notifications at user profile creation.

    Sysprepping using this command and the unattend below will recreate the problem:

    C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown /unattend:D:\CopyProfile.xml

    The unattend is simply:

    <CopyProfile>true</CopyProfile>

    That's it. If you boot to audit mode, change nothing and run that during image development, you will recreate the problem. It happens with the vanilla 1909 ISO, and also when updated to KB4532693

    This is a serious oversight by the developers. Did they did not realize or care that the Default user's hashed app associations will be copied over to new user's profiles, and break the registry?! Their documentation for CopyProfile has changed recently. Yes, they've told us it won't copy the Start Menu/Taskbar or default app associations for a while. But now CopyProfile cannot be set to true at all.

    Their janky registry hack did not work. It reduces the number of notifications and changes the messages to say it was reset to TWINUI.


    I've wasted so much time on this, and my organization's future deployment of 1909 has halted. Our students login to computers in labs which cannot save profiles. We can't have any notifications pop-up every time they log in because not only is it annoying, but we will get helpdesk tickets from it.


    Saturday, February 29, 2020 2:57 PM
  • If you follow Microsoft's instructions for building a Win10 1909 image, and set CopyProfile to true, you will get app reset notifications at user profile creation.

    Sysprepping using this command and the unattend below will recreate the problem:

    C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown /unattend:D:\CopyProfile.xml

    The unattend is simply:

    <CopyProfile>true</CopyProfile>

    That's it. If you boot to audit mode, change nothing and run that during image development, you will recreate the problem. It happens with the vanilla 1909 ISO, and also when updated to KB4532693

    This is a serious oversight by the developers. Did they did not realize or care that the Default user's hashed app associations will be copied over to new user's profiles, and break the registry?! Their documentation for CopyProfile has changed recently. Yes, they've told us it won't copy the Start Menu/Taskbar or default app associations for a while. But now CopyProfile cannot be set to true at all.

    Their janky registry hack did not work. It reduces the number of notifications and changes the messages to say it was reset to TWINUI.


    I've wasted so much time on this, and my organization's future deployment of 1909 has halted. Our students login to computers in labs which cannot save profiles. We can't have any notifications pop-up every time they log in because not only is it annoying, but we will get helpdesk tickets from it.


    I'm using CopyProfile as well since I need a mandatory profile and ran into the same issues as yours with 1809 Enterprise LTSC. But with the registry modification as I described, I don't have those notifications anymore at all, I don't have reduced messages. Anyways, maybe it's different for 1909. We only use LTSC version etc.

    I realize it's not a solution to remove those registry entries, more a work around till they actually solved what is wrong. It does take a longe time I have to say looking at this thread.

    Monday, March 2, 2020 5:36 AM
  • In what way are you editing ntuser.dat? Interested to see if I can replicate this. While it might resolve issues with new deployments, Microsoft needs to address the underlying issue, because if you use this 1909 ISO to upgrade Windows on an existing PC that has had the copyprofile (or app defaults) run on it, you're going to see these errors.

    On a side note, are people seeing this on every login? I'm only seeing it on initial login after an upgrade.

    Tuesday, March 3, 2020 2:29 PM
  • I'm guessing their editing the default user ntuser.dat file to remove the settings notifications like Matt L_ posted earlier.

    This is what I have done as well as a work around until I get an answer from our MS Support ticket.

    Like I mentioned before, this problem occurs on a fresh manual 1909 build without using sysprep and copyprofile. I didn't modify the default user at all. The only thing I did was change the web browser, export the xml, and reimport it back in again to overwrite the C:\Windows\System32\OEMDefaultAssociation.xml file and the problem occurs. Sometimes it doesn't occur until you login with a 2nd new account.

    And to answer your last question, no I only have seen this during the initial login and once they are dismissed they don't seem to show up again. It appears to be scareware since the web browser doesn't actually get reset to Edge like the notifications suggest.

    Tuesday, March 3, 2020 3:30 PM
  • I spoke with the software engineer and they confirmed it is a bug.  The app reset only occurred for new user accounts.  The error started in 1903 with one of the patches and carried over to 1909.

    They applied a testing-hotfix to a system.

    • Login with a new user account.  App reset message occurred.
    • apply test-hotfix
    • Login with a new user account.  No app reset message
    • Tried a couple other new accounts, all good.

    I don't know when this hotfix is going to get released.  It might be incorporated into a cumulative update.  I'll post back when I know more information.

    Tuesday, March 3, 2020 3:43 PM
  • Any account with those "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\*\UserChoice" "Hash" registry values is going to have that "An App Default Was Reset" message after sysprep.
    • Edited by JS2010 Tuesday, March 3, 2020 3:48 PM
    Tuesday, March 3, 2020 3:45 PM
  • I spoke with the software engineer and they confirmed it is a bug.  The app reset only occurred for new user accounts.  The error started in 1903 with one of the patches and carried over to 1909.

    They applied a testing-hotfix to a system.

    • Login with a new user account.  App reset message occurred.
    • apply test-hotfix
    • Login with a new user account.  No app reset message
    • Tried a couple other new accounts, all good.

    I don't know when this hotfix is going to get released.  It might be incorporated into a cumulative update.  I'll post back when I know more information.

    You may want to let them know that the issue is not just with new user accounts. I ran into this issue when upgrading computers that had used copyprofile from 1809 to 1909 just to test out my upgrade path. 
    Tuesday, March 3, 2020 4:13 PM
  • Are notifications turned off?
    Tuesday, March 3, 2020 4:26 PM
  • They mentioned they were tracking a number of bugs with "migration step" probably had to do with upgrades, CopyProfile and SearchProtocolHost.  

    My current Windows 10 1909 build turns off "Settings" sender notification for all new profiles.

    Tuesday, March 3, 2020 7:42 PM
  • Matt, how are you handling upgrades to 1909? Or are you at all?
    Tuesday, March 3, 2020 8:15 PM
  • Got exactly the same Problem in a other constelation

    Only the follow 5 getting reseted:

    Ms-xbl-3d8b930f, Microsoft-edge-holographic, Microsoft-edge, and a couple for the default
    browser.

    Reealy hat Windows 10 with there App Model and the problems/workaround in enterprise environments, sucks like hell, want to be linux only :-(


    Its the ghost in the machine how dont let me go in vacation :-)

    Thursday, March 5, 2020 1:59 PM
  • In my research I created a .xml from a fresh 1909 machine and found that the things being reset were set to TWINUI.  A quick google search shows this is a issue with corruption/things not working.  Doing .xml pulls are somewhat inconsistent as well between existing machines, and freshly imaged machines.  Even if you turn off the notifications, the defaults are still reset.

    The absolute best I've been able to manage is some things (like pdf, .htm in my example cases) being set, but it doesn't truly keep them on as defaults.  They come up with a How do you want to open this file? prompt with Keep using this app: highlighted.  Not that bad for a single user, but for a shared machine using deepfreeze that creates accounts on the fly when someone logs in, this is brutal.

    I've been testing in and out of VM's and have the same conclusions - you can apply only the defaults you want to change with 1809, every .xml I fed went great.  1909 is the failurepoint.  In my research I've found it's likely:

    1903 introduced a update that foobar'd everything.  That update was rolled into 1909 (as they generally are).  Thereby foobar'ing 1909.

    I get the feeling that TWINUI entries being generated is important, but I'm not quite sure how.

    I've been using a 1909 wim to push as a upgrade via PDQ for my 1909 deployments.  I'm curious if I mod the .xml in the .wim if this might change the behavior, though I doubt it would be helpful, has anyone tried doing this using a DISM /offline command?


    • Edited by Ben Kosar Friday, March 6, 2020 2:17 PM
    Friday, March 6, 2020 2:17 PM
  • I got word from the support engineer the fix will be available in the April's patch Tuesday.  The update fixes both 1903/1909 version of Windows 10.
    Tuesday, March 10, 2020 1:29 PM
  • Matt L_, In light of the need for folks to spin up VDI farms for remote work, any chance you could post the hotfix here.  Microsoft Support is taking it time with our request.
    Monday, March 16, 2020 4:41 PM
  • Hello Matt_L,

    I'm sorry but I don't agree with their analysis: it also affects Windows 10 LTSC 2019 based on a 1809 "kernel" ...
    Please can you report this problem to them and work on a patch for this version as well?

    Thank you.
    Thursday, March 26, 2020 2:27 PM