-
Patch Lady – 1803 declared Semi-annual
Microsoft today declared 1803 as “ready for business” and is flipping from the Semi-annual targeted (the old CB) to Semi-annual (the old CBB). (*)
What this means:
If you have your Windows 10 pro settings to defer feature updates for Semi-annual channel and have a deferral setting of “0”, you will soon get 1803. I have mine set at 364 days of deferral so that I can choose exactly when I deploy 1803.
Susan’s take: I think it’s still a bit early to roll out 1803 to businesses. I’m still seeing nagging issues. Check with your vendors if they are ready for 1803, and if they aren’t ask they why they haven’t been testing for 1803 already?
As long at 1803 is getting updates twice a month (it’s had two already in the month of June one of which was fixing a big bug for my industry the multi-user QuickBooks problem) I’m not comfortable with rolling out 1803 widely at this time.
Things still unfixed:
1. SMBv1 issues – patch later in June per known issues in 1803 – https://support.microsoft.com/en-us/help/4284835
Some users running Windows 10 version 1803 may receive an error “An invalid argument was supplied” when accessing files or running programs from a shared folder using the SMBv1 protocol. Enable SMBv2 or SMBv3 on both the SMB server and the SMB client, as described in KB2696547.
Microsoft is working on a resolution that will be available later in June
As far as I am aware the partition issue is still unfixed.
3. Watch out for third party vpn programs Barb helped a recent forum user that had kerio VPN software – it got to a certain percent and barfed
Issues that have been fixed
1. Alienware no longer blocked – https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/hybrid-laptops-with-discrete-gpu-connected-to/3518f6b4-c267-4d38-b5b9-d5ea0c16e975
2. Surface SSD’s okay to install since May — https://answers.microsoft.com/en-us/windows/forum/windows_10-windows_install/devices-with-intel-ssd-600p-series-or-intel-ssd/703ab5d8-d93e-4321-b8cc-c70ce22ce2f1
(*) yup screwed up and had them the other way around, now fixed. Thanks Zero2Dash