Jun 15 2022 08:46 PM
Originally posted on Twitter, June 3rd, https://twitter.com/Treestryder/status/1533173600575954944
To @Pernille-Eskebo @Windows @WindowsUpdate @windowsinsider @MSWindowsITPro
A thread/rant, after being unable to deploy functional PCs since May 10th, when Quality Update KB5013942 broke the @MicrosoftStore .
Being fully sold on the "Autopilot + Azure AD Joined + @MSIntune" dream, we expect updates (and drivers) to be published through Windows Update and applications to be in the Microsoft Store.
Most applications our company requires are not yet in the Store (including Microsoft's). So, we have to re-package them for installation through the Company Portal app. The Company Portal app is installed by the Microsoft Store… that broke May 10th.
I filed a bug report right away using Feedback Hub. https://aka.ms/AAgx0nw Last I looked, there were no updates from Microsoft. Just tried to check and (ironically) Feedback Hub is broken, "We're having trouble connecting."
We have waited patiently for the update to the update (19044.1706 to 19044.1708) listed on the Windows 10 Release History Page. However, I just found our wait was in vain.
Reading the Known Issues section of KB5013942, it says something to the effect, "No big deal. Just install it manually. Or use WSUS. Or use MEMCM". What about those using Windows Update for Business (WUfB) on thousands of PCs, drop-shipping PCs to remote locations?
Many on my team believe Microsoft is not committed to Autopilot + Intune management. As proof, they point to incidents like this, applications not in the Store (including Microsoft's), and major hardware vendors (including Microsoft) not releasing drivers through Windows Update.
Are my expectations unreasonable?
@WindowsUpdate , when the fix to a bad update is "Out of Band", using Intune and Windows Update for Business to manage thousands of PCs, what are we to do? Wait till the next Patch Tuesday and hope for the best?
Jun 15 2022 09:59 PM
Jun 16 2022 09:32 AM
SolutionJun 16 2022 12:42 PM
Jun 16 2022 01:12 PM
Jun 16 2022 06:12 PM - edited Jun 16 2022 06:14 PM
As to putting pressure on OEMs, I have been trying.
For drivers, I encourage my team to only purchase products found in Windows Compatible Products List, or at least their drivers are found in Microsoft Update Catalog. So far, I have only re-packaged a few.
Until the recent announcement that the security model of the original Microsoft Store had been given up on, I have been praising and pressuring under the Twitter hashtags #ShouldBeUWP (all the tweets have this one), #ShouldBeMSIX and #CouldBeAPPX. Now I need a new hashtag.
Jun 16 2022 09:32 AM
Solution