25324.1011 installed slowly.
No immediate problems seen.
Davy.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
25324.1011 installed slowly.
No immediate problems seen.
Davy.
This issue popped up again with Build 25324.1011. Default App set to Microsoft WinRT Storage API.
This prevents the "+ New" button from working correctly in Snipping Tool.
The problem was originally reported with Build 25295.1010, it keeps coming back on systems that were upgraded from previous older Dev Builds that had this issue of assigning the default to Microsoft WinRT Storage API instead of Screen Snipping.
Again, I had to issue this P.S. command to fix the problem, that changed the default of MS-SCREENCLIP back to what it should be.
Get-AppxPackage MicrosoftWindows.Client.Core -AllUsers | Reset-AppxPackage
MicrosoftWindows.Client.Core MicrosoftWindows.Client.Core_1000.25324.1011.0_x64__cw5n1h2txyewy
Same problem on second desktop after Updating to 25324.1011. 🤐🤷♂️
The problem starts after Client.Core is updated to 1000.25324.1011. Had to reset the App again to get the correct default for
MS-SCREENCLIP.
MicrosoftWindows.Client.Core MicrosoftWindows.Client.Core_1000.25324.1011.0_x64__cw5n1h2txyewy
Get-AppxPackage MicrosoftWindows.Client.Core -AllUsers | Reset-AppxPackage
Failing condition:
after issuing the reset command it goes back to this:
On a positive side, the Reset all default apps does not assign back Microsoft WinRT Storage API like it used to do with older builds. 👍
Finally I get change to update from 25314 to 25324 and this old issue is still there.
Once again one of my device take 3 hours to get this update completed. First 50 minutes goes as normal and after restart Working on Updates sutck at 68% for 2 hours.
I have submit many reports to FBH with setupdiag logs, but I haven't seen any response.
It would be nice to know why this fully Win 11 compatible device has this issue and is there any hope that this will be fixed.
BTW: On this same device update from build 23403 to 23419 take about 1 hour.
FBH