Windows 10 version 1903 is no longer supported after today
Just a notice for all Windows 10 users, Windows 10, version 1903 will reach the end of service on December 8, 2020, which is Today. This applies to the following editions of Windows 10 released in May of 2019: Windows 10 Home, version 1903 Windows 10 Pro, version 1903 Windows 10 Pro Education, version 1903 Windows 10 Pro for Workstations, version 1903 Windows 10 Enterprise, version 1903 Windows 10 Education, version 1903 Windows 10 IoT Enterprise, version 1903 These editions will no longer receive security updates after December 8, 2020. Customers who contact Microsoft Support after this date will be directed to update their device to the latest version of Windows 10 to remain supported. https://docs.microsoft.com/en-us/lifecycle/announcements/windows-10-1903-end-of-servicing you can check your Windows 10 version by going to Windows settings => System => About you can check and download newer version of Windows 10 OS either from Windows update or from this website: https://www.microsoft.com/en-us/software-download/windows10
Windows 10 1903 Group Policy Issues after OSD
Hi, We've recently started deploying Windows 10 1903 (First Win 10 version too...) with SCCM 1902 with MDT and group policy appears to apply, according to the logs but then we find certain settings not actually applied, even though a gpresult shows them as being applied. Checking the various reg keys etc. for our policy settings on a client, I have seen that all of our GPO settings get applied and then some but not all get mysteriously removed, for example the Interactive Logon message gets applied but then removed, as in the registry value is removed. Running a gpupdate /force after this has happened, appears to fix the issue. However using the SMSTSPostAction variable to run a script or command to update Group Policy, doesn't work either, the script/command runs (As per log files) but the above does still occur until we run a gpupdate /force (A ordinary gpupdate does nothing, so most of the time reboots etc. do nothing). We have no Group Policy related Group Policy settings (As in the ones that control whether CSEs process during slow links etc. and whether they process even though there are no changes) and we cannot find any other reason for this not to work correctly. I think until we find a fix, using the RunOnce reg key/value maybe the workaround... Would someone at Microsoft be able to confirm whether this is a confirmed issue at Microsoft and whether there is a fix for it please? Or if there is a fix incoming as potentially some of our security related GPOs are not being correctly applied. Many thanks, LukeThree known bugs in the latest build of Win10 version 1903
Microsoft late Thursday declared Win10 version 1903 as ready for business deployment. The latest versions of Win10 1903 block installation of .NET 3.5. You may scoff that it’s an old version of .NET, but at least one large package — part of the ERP package known as SAP — requires .NET 3.5. Per Günter Born: [.NET 3.5] installation fails with the error: Microsoft-Windows-NetFx3-OnDemand-Package: 0x800f0954 The latest versions of Win10 1903 break some HP printers including. According to Tom Rogers on the Patchmanagement list: I installed the updated Sept 2019 Cumulative Update for Win10 x64 [1903] and it broke me printing to a network HP Color LaserJet Pro MFP M180NW… What happens in my case is the screen will flash, I hear the printer start, but then nothing. And then Windows closes any open windows. Almost like Windows Explorer restart. Job is not being held in the queue, printer is not offline (but HP software monitor says it is), this is a network printer I am testing on. The latest versions of Win10 1903 trigger black screens when running RDP. Per an anonymous poster: We have HP z2 g4 mini PCs – Windows 10 Pro 1903 – we have installed the updates above and we still get a black screen on remote desktop. We tried changing the systems we are remoting to to use the MS Basic Display Driver but that did not resolve the issue. Rebooting allows the system to work for an unknown amount of time before it stops working again until the next reboot. And confirmation, again anonymously: I installed KB4517211 (OS Build 18362.387) and still have the RDP black screen on HP EliteDesk 800 G5 SFF and HP 800 G3 Mini desktops. I ran HP SDM on both models to ensure all OEM drivers are current as of 9/27. rolling back the latest updates fixes the problem.
