Microsoft's Windows 10 20H1 release will be first to RTM in December under Azure schedule
20H1 is Microsoft's first version of Windows 10 to be finalized under the Azure development cycle. What you need to know Windows started operating under Azure's development schedule earlier this year. This means feature updates will now be finalized in December and June. Windows 10X will RTM with 20H2 in June 2020. Microsoft's upcoming 20H1 release of Windows 10 will be the company's first version of the OS to be finalized in December, three months earlier than usual, as a result of Windows moving under Azure and adopting the "semester" based development cycle that Azure is already using. Mary-Jo Foley was first to reveal that the Windows dev cycle was being changed up earlier this year, but here's what this all means for Insiders. In the past, Windows 10 feature updates were typically finalized in March and September, but now, these OS releases are expected to be done in December and June instead. This doesn't mean Microsoft is giving feature updates less development time; this is just a result of Microsoft outright shifting the development cycle of Windows 10 updates by two to three months. Each release still gets the usual seven to nine months in development. Microsoft was able to make this change thanks to a decision it made when first moving Windows under Azure. To allow the Azure and Windows development schedules to align, it needed to skip a feature release. Windows 10's 19H2 release is the result of this, being an update that isn't a proper OS release like previous ones before it. This means Windows 10's 20H1 release is just about done. It was marked as feature-complete internally back in August, and Microsoft has been mostly focused on fixing up bugs and polishing the OS for release ever since. This is why Insiders have not seen any substantial new features in 20H1 builds for a couple of months, because the 20H1 release is done. We've got a month or so left of development before Microsoft signs-off on 20H1 in mid-December. Windows 10 20H2 This also means that work on the next Windows 10 feature update after 20H1, known as 20H2 or "Manganese" has already started development internally, and Insiders should begin receiving 20H2 builds in the next couple of weeks. On this new development cycle, 20H2 will RTM in June 2020. This is important, as this release will play a vital role in the availability of Windows 10X on new foldable PCs expected to start shipping in fall 2020. Now that 20H2 can RTM earlier in the year under the new dev schedule, Microsoft can use 20H2 as the shipping version of Windows 10X that's preloaded onto devices like the Surface Neo. This means Windows 10X will RTM in June alongside 20H2, and not with 20H1 as we had initially assumed. Microsoft needs the extra development time to make sure Windows 10X is as good as it can be at launch. Regarding desktop releases, does this mean new feature updates will be made available to the public earlier than previously? Right now, I'm not too sure. As 20H1 will be done in December, Microsoft could start shipping the update to the public as early as January, but none of my sources seem to be clear if that's actually what's happening. Microsoft may decide to keep pushing out new feature updates in the spring and fall, utilizing the Slow and Release Preview ring for extensive testing of the final build before it goes to the public. Either way, Windows is now operating under Azure's development schedule, and that means we can expect to see new feature updates finalized earlier than we've seen in the past. What are your thoughts on these changes? Let us know in the comments. Original article: Windows CentralWindows 10 2004 - MSIX Not Updating -Please check whether the Msixvc support services are installed.
We use MSIX for one of our LOB applications at my organization. We recently updated some machines to Windows 10 2004 to test it before rolling it out to the rest of the company. One problem we have noticed is that repeatedly that if we update an MSIX package on these systems and then issue a second update, the second update always fails. The event viewer logs multiple errors, most just being generic "the msix package failed to install", etc. However, there is one peculiar one. We found it under: Microsoft-Windows-AppXDeploymentServer/Operational Event Id 497 Error 0x80070002: Opening the Msixvc package from location AppName_x64.msixbundle failed. Please check whether the Msixvc support services are installed. In addition, this is logged under AppXDeployment - Operational: Event ID: 302 Failed to start system service: appxsvc with error: 0x8007045B We could not find any documentation on this error anywhere on MSDN. To work around this, we have to restart the machine. Afterwards it is able to update the MSIX package. Is this a known issue with Windows 10 2004? Can anyone here provide more information or can they provide any suggestions on how to stop this from happening? Edit: We also had a user go ahead and update their machine to Windows 10 2004 without notifying us and now they are getting the same problem as well. Edit #2: I also left this in the feedback hub in Windows 10; if there are any additional channels that I should use, please let me know.Getting the May 2020 Update Ready for Release - Build 20H1 now is in the Release Preview Ring
Hello Windows Insiders! We are now getting the Windows 10 May 2020 Update (20H1) ready for release and releasing Build 19041.207 to Windows Insiders in the Release Preview ring. We believe that Build 19041.207 is the final build and we will continue to improve the overall experience of the May 2020 Update on customers’ PCs as part of our normal servicing cadence. Build 19041.207 (KB4550936) includes all of the 20H1 features in addition to the following quality improvements and security updates: This build is cumulative and includes all the fixes released to Windows Insiders in the Slow ring in Build 19041.21 through Build 19041.173. We fixed an issue that causes the Remote Procedure Call (RPC) service (rpcss.exe) to close unexpectedly and the device stops working. Then you must restart the device. We fixed an issue that causes the Device Enrollment Status Page (ESP) on managed devices to stop responding if a policy that requires a restart is installed on the device. We fixed an issue that might prevent the rear camera flash from functioning as expected on devices that have a rear camera. It also includes the latest security updates to the Microsoft Scripting Engine, Windows Kernel, Windows App Platform and Frameworks, Microsoft Graphics Component, Windows Media, Windows Shell, Windows Management, Windows Cloud Infrastructure, Windows Fundamentals, Windows Authentication, Windows Virtualization, Windows Core Networking, Windows Storage and Filesystems, Windows Update Stack, and the Microsoft JET Database Engine. Continue Reading on the Windows Insider Blog
