![Windows Windows](/uploads/1/2/4/3/124393461/489936487.jpg)
Windows Sandbox is a new security feature that Microsoft plans to introduce in Windows 10 version 1903. It works similarly to third-party sandboxing solutions and uses Microsoft Hypervisor and hardware virtualization at its core. The sandbox requires Windows 10 Pro or Enterprise. Windows Sandbox may fail to start with 'ERRORFILENOTFOUND (0x80070002)' on devices in which the operating system language is changed during the update process when installing Windows 10, version 1903. Microsoft is working on a resolution and will provide an update in an upcoming release.
Microsoft has updated the official system requirements for Windows 10 version 1903. You might want to know if your PC is capable of running the latest operating system from Redmond.RECOMMENDED:Windows 10 system requirements which Microsoft officially stated initially were not changed for a long time.
However, for the upcoming Windows 10 version 1903, also known as May 2019 Update, system requirements have been raised by Microsoft. Windows 10 Version 1903 System RequirementsWindows 10 version 1903 will require a PC which fits the following specifications:. Processor: 1 gigahertz (GHz) or faster processor or SoC. RAM: 1 gigabyte (GB) for 32-bit or 2 GB for 64-bit.
Hard disk space: 32 GB for both 64-bit and 32-bit OS. Graphics card: DirectX 9 or later. Display resolution: 800 x 600, a minimum diagonal display size for the primary display of 7-inches or larger.The key in the list is the new storage size requirement. For Windows 10 version 1809 and prior, it was 16 GB for 32-bit OS 20 GB for 64-bit OS.
![Windows 10 1903 update assistant Windows 10 1903 update assistant](/uploads/1/2/4/3/124393461/757489446.jpg)
This week, we announced the release of Windows 10, version 1903 and Windows Server, version 1903. As you look to deploy these feature updates in your organization, I want to tell you about some changes we are making to the way Windows Server Update Services (WSUS) and System Center Configuration Manager download feature and quality updates. Deploying updates using System Center Configuration ManagerIn order to deploy feature and quality updates to devices running Windows 10, version 1903 or Windows Server, version 1903 (and later), you will need to ensure that you are running the current branch of System Center Configuration Manager, which is. Then, in the Configuration Manager console, enable the Software Update point to download updates for Windows 10, version 1903 and later and/or Windows Server, version 1903 and later.Note: Once you make this change, updates will be available for version 1903 and later versions of the Windows 10 and Windows Server operating systems.Figure 1. Selecting Windows 10, version 1903 and later in Configuration Manager, version 1902.Figure 2. Selecting Windows Server, version 1903 and later in Configuration Manager, version 1902. Deploying updates using Windows Server Updates ServicesIf you are using Windows Server Update Services (WSUS) to deploy updates to devices running Windows 10, version 1903 or Windows Server, version 1903 (and later), you will need to select a new product category to sync and download updates.
To make this change in WSUS, open the Update Services administrator console, select Options Products and Classifications, and, in the Products tab, select Windows 10, version 1903 and later and/or Windows Server, version 1903 and later.Note: Once you make this change, updates will be available for version 1903 and later versions of the Windows 10 and Windows Server operating systems.Figure 3. Selecting Windows 10, version 1903 and later in the WSUS console.Figure 4. Selecting Windows Server, version 1903 and later in the WSUS console. Frequently asked questionsWill a new product category be created for each future release of Windows 10 or Windows Server?No.
We plan to service future releases of Windows 10 and Windows Server with the Windows 10, version 1903 and later and Windows Server, version 1903 and later product categories.Why does this category need to be manually configured in Configuration Manager, version 1902 and WSUS?With Windows 10, version 1903, we are introducing new product categories to enable future support for the Unified Update Platform (UUP) for on-premises management solutions, which provides improved delivery technologies for Windows updates. A configuration change is, therefore, required for environments running the latest public release of Configuration Manager, as well as for environments using WSUS (without Configuration Manager) for updates. (Note: UUP for on-premises management solutions is not yet available. We will have future news regarding UUP, including a public preview, at a later date.)I am using Configuration Manager, version 1810.
Can I deploy updates to Windows 10, version 1903 or Windows Server, version 1903?No. In order to deploy updates to Windows 10, version 1903 or or Windows Server, version 1903 devices, Configuration Manager, version 1902 or later is required. We recommend that you update to the current branch as soon as possible to ensure that your Windows 10, version 1903 devices receive the targeted quality updates.Will I have to select a new option each time Windows 10, Windows Server, or Configuration Manager is updated?No.
We plan to automatically add this new category to software update point (SUP) synchronization configurations and existing automatic deployment rules (ADRs) upon upgrade to the next version of Configuration Manager in environments in which Windows 10 updates are currently being synchronized. Tools and resourcesFor help with configuring and deploying updates for Windows 10, please see the following resources:.And, for the latest updates on new releases, tools, and resources, stay tuned to this blog and follow us on Twitter. So, do i understand this right? Previously it was enough to just select Windows 10 (without any other version or anything) to get all past, current and future updates (including feature updates if Upgrades category is selected).
This is still enough to get the 1903 feature update itself (i already see it synced in my test WSUS box in Upgrades view). But after one upgrades machines to 1903, future CU, Security and other updates will only be synced if Windows 10 1903 and later branch is selected? I know you are reasoning this with UUP changes. But i wonder what other benefits it could have. Say now, when general Windows 10 branch is selected, i get updates for all supported versions, though we only use the latest one. So i have to decline a lot of updates. Maybe in future we can avoid this by only selecting branches with versions we use?
Say i would have 1903 and 1909 branches selected, so WSUS will only sync security and CU updates for these versions? Or will we have to select the general Windows 10 branch anyway and thus will get all not relevant updates with it?
Why will future versions not require this I actually like this idea more so you have better control. Its annoying to see updates for 1703, 1607, 1803 if they are builds I have never deployed in my environment then have to time consolingly deny them every single month. That fact that WSUS has not received a UI facelift in so long to better manage this stuff is disappointing especially if you don't tie it to SCCM. Same thing with freaking Itanium updates where is there no way to disable them or auto deny them if I dont have any of that hardware so every month I have to go deny them so they dont show in the unapproved interface.
We still need to control so WUFB in the clound is not a good choice but WSUS needs improvement after a lot of stagnation Make this simpler on us please. Hi,I tried to upgrade the 1803 to 1903 SAC Windows 10 enterprise edition, I download and install both feature and security update via 'Windows update' directly, and then i use the update tool directly from below Microsoft URL, after a 30 mins, the SAC build number updated to 1903,I just wonder is above upgrade process is correct and expected, is there any easy or automatic way to do it?BTW, I found offline device cannot run above update tool. So how we manage the offline device?Actually, my key question is how we manage it in enterprise situation? Is above SCCM deploy including Build number upgrade? Or just deployment the features update pack?ThanksDonovan LEE.