Jump to content

Search the Community

Showing results for tags 'windows 10 1903'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Categories

  • Drivers
  • Filesharing
    • BitTorrent
    • eDonkey & Direct Connect (DC)
    • NewsReaders (Usenet)
    • Other P2P Clients & Tools
  • Internet
    • Download Managers & FTP Clients
    • Messengers
    • Web Browsers
    • Other Internet Tools
  • Multimedia
    • Codecs & Converters
    • Image Viewers & Editors
    • Media Players
    • Other Multimedia Software
  • Security
    • Anti-Malware
    • Firewalls
    • Other Security Tools
  • System
    • Benchmarking & System Info
    • Customization
    • Defrag Tools
    • Disc & Registry Cleaners
    • Management Suites
    • Other System Tools
  • Other Apps
    • Burning & Imaging
    • Document Viewers & Editors
    • File Managers & Archivers
    • Miscellaneous Applications
  • Linux Distributions

Categories

  • General News
  • File Sharing News
  • Mobile News
  • Software News
  • Security & Privacy News
  • Technology News

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

  1. Microsoft starts force-upgrading users on Windows 10 1903 to 1909 Microsoft's Windows 10 May 2019 Update has been around for 17 months, and as usual for a spring release, that means that support is going to end in December. Specifically, it gets its last update on Patch Tuesday, which is December 8. That means that it's time for automatic updates, something that frankly should have started a while ago. The way Windows 10 feature updates is that Microsoft only automatically updates your machine if you're on a version that's nearing the end of support, and typically that automatic upgrade period starts about six months out. It didn't for version 1903, and you can probably thank the COVID-19 pandemic for that. Back in April, Microsoft announced that it was extending support for Windows 10 version 1809 until November, and then in June, that automatic upgrade period started for users on that version of Windows. Since 1809 and 1903 end-of-life is now a month apart, one would think that automatic upgrades would have started for 1903 users in July. They did not. In fact, when the Windows 10 October 2020 Update shipped, Microsoft said that it would be available to "seekers" on version 1903 or higher, meaning anyone who manually sought out the update can get it. That's changing today. Microsoft is finally starting to automatically upgrading those on version 1903 to a newer version, but strangely, not the newest one. Microsoft is going to start upgrading version 1903 to version 1909, so it should be a quick and easy upgrade that you probably won't even notice. This also means, of course, that you'll get another force upgrade within a few months, since end-of-life for version 1909 isn't far off either, at least for consumer customers. Microsoft starts force-upgrading users on Windows 10 1903 to 1909
  2. Windows 10 version 1903 is no longer supported after today Today, Windows 10 version 1903 is getting its final cumulative update, as it has reached its end of life. While this date has always been public knowledge, it may come as a surprise to those that weren't paying attention since 1809 support ended just last month. This applies to all SKUs of Windows 10, including Home, Pro, Pro for Workstations, Enterprise, and Education. Spring updates are only supported for 18 months, while fall updates are supported for 18 months for Home and Pro SKUs, and for 30 months for Enterprise and Education. That's why if you're on Windows 10 Enterprise or Education, version 1809 is still supported until May. Microsoft had actually extended support for Windows 10 version 1809 by six months because of the COVID-19 pandemic. That's why support for the two versions ended only a month apart. Windows 10 version 1903 is significant because it was the first Windows 10 feature update that wasn't automatically installed on users' computers. Due to version 1809 being a mess, the Redmond firm said that feature updates would be completely optional unless the version you're running is nearing the end of support. For version 1809, it started upgrading users to version 2004 back in June, but for 1903, Microsoft didn't start migrating users to a newer version until only a month ago. And instead of upgrading users to the newest version, it moved them to the year-old version 1909. If you're still on Windows 10 version 1903, you should be able to get to something newer by checking for updates in Windows Update. If you don't find anything there, you can use Microsoft's own upgrade tool. Windows 10 version 1903 is no longer supported after today
  3. Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows” I just heard about this from Office Watch, but checking around, it’s also described on Tenforums and on the VMWare blog. When you install any of the recent cumulative updates for Win10 1903 (the third cumulative update for September, or any of the three cumulative updates in October, including the most recent one), Windows starts blocking older versions of VMWare. The reason? MS removed VMWare from the Windows Application Compatibility database. Apparently VMWare version 15.5 — the latest version — gets around the block. But if you aren’t willing to pay for the latest version, you’re up the ol’ creek. The solution is so utterly trivial it boggles even my pre-boggled mind. You rename the program that runs VMWare, C:\Program Files (x86)\VMware\VMware Workstation\vmware.exe. The renamed file passes the Application Compatibility block, and you’re free to use the old version. Stupid. Does anybody know if there’s a reason why VMWare versions prior to 15.5 are prohibited from running on post-September-updated versions of Win10 1903? Source: Another dumb block: MS induced “VMware Workstation Pro can’t run on Windows” (AskWoody - Woody Leonhard)
  4. A tiny sop to Win10 1903 users bitten by the KB 4512941 Cortana/SearchUI.exe redlining bug Microsoft has finally acknowledged – by tweet, no less – what many have known since Friday: The “optional, non-security” August patch for Win10 version 1903, KB 4512941, can redline your PC. Thanks, Cortana. Franck V. (CC0) On Friday, Microsoft released KB 4512941, the long-anticipated second August cumulative update for Win10 version 1903 – which is to say, the latest patch for the latest version of Windows. Within a few hours, people were complaining on various online forums that installing the update immediately triggered excessive CPU use. I wrote about that on Friday night. Cortana’s SearchUI.exe routine can send one “core” processing unit through the roof. Various reports place the redlining at anywhere from 40% to 100% utilization of the single core, resulting in a constant drain of 20% or more on the entire PC. In Win10 1903, when you search your computer, you use Cortana. So the native Search function also breaks down. Although the second August cumulative update for 1903 is billed as “optional,” it’s a key update precisely because the first August cumulative update broke Visual Basic, Visual Basic for Applications, and VBScript. Patches in July and August also broke Windows Sandbox, the Preboot Execution Environment and MIT Kerberos – all of which are supposed to be corrected by this second August patch. But if you install the second August patch, KB 4512941, there’s a decent chance your machine will break out in hives. Most damning, Mayank Parnmar at Windows Latest reported on Saturday: It’s important to note that Microsoft actually tested KB4512941 with Windows Insiders in the Release Preview Ring for more than a week before shipping the update to the general public. According to some posts on Feedback Hub, reports of high CPU usage were submitted multiple times by testers earlier this week, but the reports appear to have been ignored because they weren’t upvoted enough. Nobody knows exactly which machines will get hit, but Günter Born has significant evidence that it’s all related to a bad Cortana cache. Says Born: One could now simply say: Ok, I clear the cache and it’s fixed. Unfortunately this won’t help, because the cache will not be rebuilt if it is deleted or a new cache is created. We heard exactly nothing from Microsoft about the bug until Tuesday afternoon – four days after complaints started to appear. The acknowledgment came in a short tweet from the @WindowsUpdate account: We are currently investigating an issue where users are reporting high CPU usage linked to SeachUI.EXE [sic] after installing the optional update on August 30 (KB4512941). We will provide an update in an upcoming release. Even now, on Wednesday morning, five days after the initial complaints, Microsoft hasn’t acknowledged the problem in the KB article, which says: Known issues in this update Microsoft is not currently aware of any issues with this update. Nor has MS mentioned anything in the Release Information Status page, which was designed specifically to highlight bugs like this. So we get a tweet and a promise that the bug will be fixed sometime “in an upcoming release." Be still my beating heart. There’s some talk about solving the redlining problem by setting the Registry key, HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search\BingSearchEnabled to 1. But there’s also considerable evidence that approach doesn’t work in all situations. Meanwhile, we’re stuck between Scylla and Charybdis. You need to get the first August cumulative installed to block DejaBlue, which remains a potent threat although it hasn’t been exploited as yet. You need to get the second August cumulative update installed to fix the bugs created (or perpetuated) in the first cumulative update. But the second cumulative update may hobble your machine. Windows as a Service. Join us for a late summer roast on AskWoody.com. Just don’t tell me that Win10 1903 is ready for prime time, OK? Source: A tiny sop to Win10 1903 users bitten by the KB 4512941 Cortana/SearchUI.exe redlining bug (Computerworld - Woody Leonhard)
  5. Yet another bug in Win10 1903: Upgrade may knock out certain WiFi cards Microsoft just announced that it’s putting a hold on upgrading machines to Win10 version 1903 for “some devices with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards.” Here’s the full announcement: Safeguard on certain devices with some Intel and Broadcom Wi-Fi adapters Microsoft and NEC have found incompatibility issues with Intel Centrino 6205/6235 and Broadcom 802.11ac Wi-Fi cards when running Windows 10, version 1903 on specific models of NEC devices. If these devices are updated to Windows 10, version 1903, they will no longer be able to use any Wi-Fi connections. The Wi-Fi driver may have a yellow exclamation point in device manager. The task tray icon for networking may show the icon for no internet and Network & Internet settings may not show any Wi-Fi networks. To safeguard your update experience, we have applied a compatibility hold on the affected devices from being offered Windows 10, version 1903. Affected platforms: Client: Windows 10, version 1903 Workaround: If you are using an affected device and you have already installed Windows 10, version 1903, you can mitigate the issue disabling then re-enabling the Wi-Fi adapter in Device Manager. You should now be able to use Wi-Fi until your next reboot. Next steps: Microsoft and NEC are working on a resolution and will provide an update in an upcoming release. Note We recommend that you do not attempt to manually update using the Update now button or the Media Creation Tool until this issue has been resolved. I’m trying to remember when the “Update now” button appears. I know about “Download and install now,” but “Update now” doesn’t sound familiar. Source: Yet another bug in Win10 1903: Upgrade may knock out certain WiFi cards (AskWoody - Woody Leonhard)
  6. Microsoft’s latest Patch Tuesday Update(KB4515384) for Windows 10 1903 breaks audio on some PCs It now appears that alongside Windows Search bug and broken Start Menu, the recently released Cumulative Update KB4515384 has another issue, but this time it’s related to audio. Cumulative Update KB4515384 for Windows 10 1903 has a bug that either completely breaks the audio or lower the sound while playing games, according to various Reddit posts. As reported by affected users, the audio issue arose right after installing the latest Cumulative Update. “….my volume was decreased by a mile after the update and since I couldn’t find a fix for it I rolled back to the older driver/update. Now hoping to finally find a solution instead of resorting to rolling back. After finally updating the latest Windows 10 update yesterday, the volume has decreased by a lot and it’s close to no sound. I’ve reinstalled and updated all the necessary sound/headset drivers, both manually and also in Device Manager. I’ve tested and tried uninstalling some audio drivers, and it’s still the same. The volume bar hasn’t changed, it remains at 40% which I’ve always used, but the volume has gone very low.” “The volume works fine on browsers and also YouTube, but not applications and games,” a user wrote on Reddit. Another user corroborated similar story by saying, “….KB4515384 my in-game sound lost all bass notes. It didn’t affect video player, audio player or browser.” While Microsoft is yet to acknowledge the issue and provide a workaround, if you’re facing a similar issue, you can follow a few simple steps that can fix the audio issue. How to fix the audio issues in Windows 10 KB4515384 Update Right-click the Sound icon on taskbar and Sound settings. On Settings page’s Related Settings section, select Sound Control Panel. Right-click the Default device on the Playback tab and select Properties. Go to the Advanced tab and change the setting to 16 bit (DVD quality). Click on OK to apply changes. However, if you’re one of them who loves to listen to high-quality audio and, therefore, don’t want to lower the quality, not even by a few bits, you can simply uninstall the latest Cumulative Update. Source: Microsoft’s latest Patch Tuesday Update(KB4515384) for Windows 10 1903 breaks audio on some PCs (MSPoweruser)
  7. KB4512941 for Windows 10 version 1903 The second cumulative patch for the current version of Windows 10, in this case Windows 10 version 1903, is always late to the party. Microsoft released updates for earlier versions of Windows 10 that it still supports about two weeks ago -- KB4512534 for Windows 10 version 1809 -- to fix a huge number of issues including the Visual Basic issue that was introduced on the August 2019 Patch Day. The update KB4512941 for Windows 10 version 1903 and Windows Server version 1903 is available via Windows Update, Microsoft Update, the Microsoft Update Catalog, and Windows Server Update Services. The update fixes the Visual Basic issue, the long-standing Preboot Execution Environment issue, the Sandbox startup issue, and the issue that caused devices from starting up under certain circumstances if configured to use MIT Kerberos realms. KB4512941 for Windows 10 version 1903 Support page Microsoft Update Catalog The following issues are fixed in the update: Fixed a black screen issue when using Remote Desktop to connect to a PC running Windows 10 version 1903. Fixed a Windows Sandbox start up issue that threw the error "ERROR_FILE_NOT_FOUND (0x80070002)". Number of supported interrupts increased to 512 on devices with x2APIC enabled. Fixed a Trusted Platform Module issue that prevented some devices from being used for Next Generation Credentials. Fixed an issue that caused workstations to stop working when signing in using an updated user prinicipal name. Fixed a Windows Defender Advanced Threat Protection issue that prevented it from collecting forensic data when Registry-based proxy configurations were used. Fixed a Windows Defender Advanced Threat Protection compatibility issue. Fixed a rare issue that affected the driver mssecflt.sys which caused the error message STOP 0x7F: UNEXPECTED_KERNEL_MODE_TRAP. Fixed an issue that could lead to excessive memory usage in Windows Defender Advanced Threat Protection. Detection accuracy of Microsoft Defender ATP Threat & Vulnerability Management. Addressed an issue that prevented the loading of third-party binaries from Universal Windows Platform applications. Fixed an issue that caused devices to have truncated device names when names were assigned to the devices automatically using Autopilot provisioning. Fixed an issue that caused the production description of Windows Server 2019 to be incorrect when using slmgr /dlv. Fixed a reporting issue in Windows Management Instrumentation. Fixed a compound documents copying and pasting issue between applications that hosts the RichEdit control and other apps. Fixed an issue that prevent some games from using Spatial Audio capabilities. Fixed an issue that caused the cursor not to appear when selecting elements using touch. Fixed an issue that caused the names of unsupported applications to appear in Start with default text, ms-resource:AppName/Text, after upgrading. Fixed an issue that prevented the PIN prompt to appear in Internet Explorer. Fixed a DRM files download issue in IE and Microsoft Edge. Improved compatibility and user experience of certain Win32 apps so that they work with Windows Mixed Reality. Addressed an issue with LdapPermissiveModify requests. Fixed the Preboot Execution Environment issue. Fixed the MIT Kerberos issue. Fixed the Visual Basic issue. Microsoft lists no known issue on the update page. Günter Born discovered an issue that causes high CPU load. You can check out his analysis and workaround here. Source: KB4512941 for Windows 10 version 1903 (gHacks - Martin Brinkmann)
  8. Microsoft: Win10 1903 having problems with Bluetooth speakers This one’s odd. According to the just-posted KB 4518538, “Bluetooth speakers don’t work after update 4505903 is installed on Windows 10, version 1903.” After you install update 4505903 on Windows 10, version 1903 on a computer that has an internal speaker installed, you experience one of the following issues: A Bluetooth speaker can’t connect to the computer. A Bluetooth speaker can connect to the computer. However, the speaker output sounds noisy (bad quality). A Bluetooth speaker can connect to the computer. However, the sound is generated by the internal speaker instead of the Bluetooth device. Additionally, in Device Manager, you notice an entry under the Sound, video and game controllers node for Microsoft Bluetooth A2dp Source that shows a yellow bang (exclamation mark) icon. Here’s what’s odd. KB 4505903 is July’s “optional non-security” second monthly cumulative update. I have no idea why the second July update would have a problem that doesn’t occur in the first August cumulative update. (We haven’t yet seen the second August cumulative update for Win10 1903.) UPDATE: @abbodi86 has what sounds like the right diagnosis: The issue is probably caused by some combination, or bad sequence, of patches. It does not seem directly related to the update Source: Microsoft: Win10 1903 having problems with Bluetooth speakers (AskWoody - Woody Leonhard)
  9. Yet another Win10 version 1903 cumulative update video bug: Installing this month’s first cumulative update clobbers some Intel video drivers Mayank Parmar at Windows Latest has connected the dots on another Win10 version 1903 cumulative update KB 4517389 bug. (See the next post for yet another unacknowledged bug.) Per Parmar: If you install Windows 10 KB4517389 (Build 18362.418) on a PC that has Intel display driver version 26.20.100.7157 or possibly other versions, basic features like Start menu, Windows Search or Google Chrome will render incorrectly… At the time of writing this story, more than 60 users have confirmed display issues on Microsoft’s community forum. Users have documented the following bugs: Windows Search and Internet Explorer with ‘X’ across dialog and links Triangled images in Microsoft Word. Chrome rendering a black screen. This one hasn’t been acknowledged by Microsoft, either. Looks to me like the folks running the Release Status Information page are asleep at the wheel. Source: Yet another Win10 version 1903 cumulative update video bug: Installing this month’s first cumulative update clobbers some Intel video drivers (AskWoody - Woody Leonhard) If you like this post, then this post.
  10. Getting the error “unexpected error; quitting” in Win10 version 1903? Blame the latest cumulative update Yet another bug in this month’s first cumulative update for Win10 version 1903, KB 4517389. Our own Mark Busby described the symptoms: After installing KB4517389 on these Windows systems, when opening 16-bit applications an error message is displayed “unexpected error; quitting” … After removing the update the application works fine once more. An anonymous poster on AskWoody pointed to this Answers Forum post, which gives more details: I have a Windows 10 Home 1903 32bit machine. After installing the windows update KB4517389 any programs that were coded in Microsoft Visual Basic 3 no longer run and give the message ‘unexpected error; quitting’ This message appears to be part of VBRUN300.DLL If I uninstall the update the programs work ok again. I have tried running these programs as administrator but this makes no difference. Microsoft hasn’t confirmed the bug – and the only fix appears to be uninstalling the latest patch. Source: Getting the error “unexpected error; quitting” in Win10 version 1903? Blame the latest cumulative update (AskWoody - Woody Leonhard) If you like this post, then this post.
  11. Microsoft acknowledged a new issue leading to intermittent issues when printing or completely breaking the printing capabilities of Windows devices after installing cumulative updates issued during late September. "The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing," says Microsoft in the known issue's description on the Windows Release Health Dashboard. "Some apps may close or error when the print spooler fails and you may receive a remote procedure call error (RPC error) from some printing utility or printing apps," also adds Microsoft. Affected platforms & Client Server Originating update Windows 10, version 1903 ,Windows Server, version 1903 KB4522016 Windows 10, version 1809, Windows Server, version 1809/Windows Server 2019 KB4522015 Windows 10 Enterprise LTSC 2019 N/A Windows 10, version 1803, Windows Server, version 1803 KB4522014 Windows 10, version 1709, Windows Server, version 1709 KB4522012 Windows 10, version 1703, Windows Server 2012 R2 KB4522011 Windows 10 Enterprise LTSC 2016, Windows Server 2012 N/A Windows 10, version 1607, Windows Server 2016 KB4522010 Windows 10 Enterprise LTSC 2015 N/A , Windows 8.1 .Windows Server 2012 R2 KB4516041 Windows 7 SP1. Windows Server 2008 R2 SP1 KB4516048 Workaround for printing issue A workaround is already available for this known issue while Microsoft is still working on a resolution that will be provided to all affected Windows customers as part of an upcoming release. Retrying the print job or restarting the device should allow users to successfully revive their printers according to Microsoft. For some devices, a driver downgrade may also be useful for solving the printing problems. "Retrying to print may allow you to print successfully. If retrying does not allow you to print, you may also need to restart your device," says Redmond. "If your device is using a v4 print driver and a v3 driver is available, you can also try installing the v3 driver as a workaround." [Windows Release Health Update – New Known Issue: Mitigated] The print spooler service may intermittently have issues completing a print job and may result in a print job being canceled or failing. Read more here: https://t.co/NHEQuEjsVX. — Windows Update (@WindowsUpdate) October 1, 2019 Windows 10 1903 in broad deployment, safeguards still on As announced by Microsoft last week, Windows 10 version 1903 is now the broad deployment channel which makes it available to everyone via Windows Update. This means that all users will now be able to see the Windows 10, version 1903 release being offered in Windows Update unless their devices are affected by hardware compatibility blocks. These are the six compatibility holds still active for devices upgradeable to Windows 1903, version 1903 (Microsoft provide mitigation measures for three of the issues behind them): • Safeguard on certain devices with some Intel and Broadcom Wi-Fi adapters • The dGPU may occasionally disappear from device manager on Surface Book 2 devices • Unable to discover or connect to Bluetooth devices (Mitigated) • Intel Audio displays an intcdaud.sys notification (Mitigated) • Cannot launch Camera app (Mitigated) • Intermittent loss of Wi-Fi connectivity Windows 10 users can use the info available in this support article or go through this guided walk-through to troubleshoot update problems. Source
  12. Three known bugs in the latest build of Win10 version 1903 Microsoft is supposed to be keeping us informed of bugs in Win10 versions, and you’d think they’d be particularly on-the-spot about following up on bug reports in the newly christened “ready for broad deployment” version of their flagship product. Harumph. I know of three bugs — all documented on this site — that bedevil both the current release of Win10 version 1903, build 18362.387, and its predecessor, the undistributed 18362.357: 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 colour 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. Those last two may be driver problems — hard to say — but a “ready for broad distribution” build shouldn’t trigger new bugs in longstanding drivers, eh? In all cases, rolling back the latest updates fixes the problem. Source: Three known bugs in the latest build of Win10 version 1903 (AskWoody - Woody Leonhard)
  13. Surprise! Windows 10 version 1903 declared 'ready for broad deployment' With several known and well-documented bugs still cluttering things up, Microsoft late Thursday declared Win10 version 1903 as ready for business deployment. Hard to tell if it’s a declaration of stability, or a pre-1909-release panic attack. Microsoft / Valery Brozhinsky / Fermate / Getty Images It's the closest thing we have to the old "Semi-Annual Channel" and "Current Branch for Business." In the past few hours, Microsoft has given its deployment go-ahead for Windows 10 version 1903, putting it in the CBB/SAC/”ready for broad deployment” branch. The Windows 10 release information page now says: Current status as of September 26, 2019: Windows 10, version 1903 (the May 2019 Update) is designated ready for broad deployment for all users via Windows Update. As devices running the Home, Pro, and Pro for Workstation editions of Windows 10, version 1803 (the April 2018 Update) will reach end of service on November 12, 2019, we are broadly updating these devices, as well as those running earlier versions of Windows 10 that are past end of service, to keep these devices both supported and receiving monthly updates. If you are not offered the Windows 10, version 1903 feature update, please check below for known issues and safeguard holds that may affect your device. We recommend commercial customers running earlier versions of Windows 10 begin broad deployments of Windows 10, version 1903 in their organizations. From where I sit, that's horsefeathers. The first cumulative update for September – lthe atest "non-optional" build of Win10 1903, 18362.356 – has several known problems, including the acknowledged audio level bug. The spectacularly mishandled second cumulative update for September, build 18362.357, introduced several new bugs – and was never distributed through the normal update channels. Win10 version 1903’s third September cumulative update, released yesterday, build 18362.387 – billed as an “optional non-security update” that nonetheless includes a hastily assembled security patch – has at least two well-documented bugs (preventing installation of .NET 3.5 and driving certain HP printers nuts). Microsoft hasn’t yet acknowledged those bugs, but it’d be kind of unseemly to admit to embarrassing problems on the same day that the version is elevated to CBB/SAC/”ready for broad deployment” status. Admins I know are livid about the ridiculous (non) rollout of the CVE-2019-1367 Internet Explorer “0day” patch and its bumbling aftermath. I can’t wait until they stumble into work this morning and discover that Microsoft is telling them (and their managers) that they're ready to roll version 1903 out to the masses. The obvious impetus: Microsoft intends to push out Windows 10 version 1909 shortly, so it needs to tie up loose ends with 1903. This announcement has nothing to do with 1903’s stability, and everything to do with Microsoft’s distribution calendar. If you remember how it used to work, join us on AskWoody. Source: Surprise! Windows 10 version 1903 declared 'ready for broad deployment' (Computerworld - Woody Leonhard)
  14. With a fix for the 'temporary profile' bug still elusive, Win10 1903 and 1909 customers should check Pause Updates Microsoft has not yet acknowledged — much less fixed — the widely publicized bug in its February Patch Tuesday update that causes Win10 1903 and 1909 customers’ desktops to disappear. If you haven’t yet installed KB 4532693, make sure Pause Updates is still protecting you. Thinkstock By now you’ve probably heard about the disappearing-profile bug in this month’s Win10 1903 and 1909 cumulative update. The buggy patch went out on Tuesday, Feb. 11. Reports started rolling in shortly afterward about desktops that were wiped clean, wallpaper replaced, even files that disappeared. I wrote about it on Thursday morning: Many people are in a tizzy — their desktop icons are gone, they can’t log onto their usual Admin account, and their files most definitely aren’t where they left them. Since then we’ve seen many hundreds of complaints and dozens of articles about the mayhem. Ends up that the hapless victims had their Windows profiles swapped out, replaced by a temporary profile. The buggy patch moved their cheese and hid it where all but the most advanced Windows boffin would never find it. Early on, Patch Lady Susan Bradley nailed the cause of the problem: Loss of profile has historically been a race condition between the boot process and something holding files open. I personally have seen antivirus most often do this but it could be other things like antiransomware protection, group policy settings. Microsoft DOES test their patches, they really do. What they can’t do is test for the myriad of unknown ways that we set up our computers. (Techy note: A race condition is a timing issue that arises when two or more independent programs stomp on each other. They’re very difficult to diagnose.) Initial reports pointed the finger at a specific antivirus package as being the one that tangled with the KB 4532693 installer, but then we discovered that not all folks running that AV software were getting bit. Then we had a series of reports about local accounts (users who aren’t signed on with a Microsoft Account) getting the special treatment. Nope, that wasn’t the problem. Microsoft hasn’t officially acknowledged the bug, as best as I can tell, aside from two posts on the Answers forum. On Feb. 12, Lawrence Abrams at BleepingComputer said that a Microsoft rep told him, “We are aware of the issue and are investigating the situation.” On Feb. 17, almost a week after the bug first appeared, Mayank Parmar at Windows Latest said: In a conversation with Microsoft’s support team, multiple employees told us that Microsoft is aware of the issue and are actively investigating the situation. “Microsoft is aware of this known issue and our engineers are working diligently to find a solution for it,” a staff stated. There have been multiple reports of users losing data because of the KB 4532693 patch. I haven’t seen that happen as yet, personally, so remain skeptical. Far more likely is that the data got stuffed into a .BAK or .000 or .003 folder inside the C:\Users folder — the place Windows sticks profiles. If a Windows customer runs a Cleaner program while trying to fix the lost profile bug, the backup may well be gone. Most distressing: Susan Bradley reports on a response to a Microsoft support case, in which a Microsoft technician specifically mentioned Windows Defender as a possible source of conflict: I discussed the case with my tech lead and confirmed this to be a bug — 25270101 … find the Windows Defender Advanced Threat Protection and Microsoft Defender Antivirus services, right-click each of them, select Properties, and change Startup Type to Disabled, selecting OK after each change. Restart your device in normal mode and attempt to sign in with your original profile. It isn’t at all clear if Defender might be part of the two-to-tango race condition. And, of course, neither the Knowledge Base article nor the official Windows Release Status page says a word. Nine days later and the buggy patch is still being shoveled out the Windows Automatic Update chute. Not all is doom and gloom. If you’re using Pause Updates in Win10 1903 or 1909 to block Microsoft’s patches, and your “Resume updates” date is far enough out — today or later — you didn’t get either this buggy patch or the monstrous KB 4524244 UEFI “patch,” which was pulled last week. But if you’re relying on Pause Updates, now would be a very good time to make sure it’s set out to the end of the month or later. Heaven only knows when (if!) Microsoft is going to re-release KB 4532693 and fix the disappearing profile problem. For most of you, pausing updates until March 9 seems like a very good idea. (If you’re running SQL Server, though, you need to get the February patches installed. Sorry.) To adjust your Pause Updates setting, first make sure you’re running either Win10 version 1903 or 1909 (type winver down in the Search box and press Enter). If you are, click Start > Settings > Update & Security. You should see something like the screenshot. Woody Leonhard/IDG If your “Updates will resume on” date is before March 9, click the “Pause updates for 7 more days” link. (March 9 is a lucky number because the next Patch Tuesday is on March 10. Presumably Microsoft will fix this mess prior to that date. Presumably.) In the past, I haven’t recommended that you extend the “Resume updates” date by pressing the “Pause updates for 7 more days” link because Microsoft has long warned that you can only extend updates after you’ve installed the currently available updates: After the pause limit is reached, you'll need to install the latest updates before you can pause updates again. I’m delighted — and surprised — to tell you that, at least in my tests, that limitation no longer applies. It appears to me as if you can go back in and pause updates for seven more days at a clip, even if you already have Pause updates set. That’s remarkably good news. Questions? Observations? Vituperations? We’re all ears on AskWoody. Source: With a fix for the 'temporary profile' bug still elusive, Win10 1903 and 1909 customers should check Pause Updates (Computerworld - Woody Leonhard)
  15. Windows 10 version 1903: some upgrade blocks lifted and new problems Microsoft released the final version of Windows 10 version 1903, the May 2019 Update, at the end of May 2019. The release replaces Windows 10 version 1809 and will be around for longer because Windows 10 19H2, the second feature update of 2019, will just be a cumulative update and not a full feature update. The new feature update for Windows 10 has had its share of issues but was not nearly as buggy as the Windows 10 version 1809 update that Microsoft had to pull for about six weeks because of major issues. Microsoft revealed in June that the new update was available to all administrators who ran manual update checks but failed to highlight that plenty of upgrade blocks were in place that prevented the upgrade to the new version of Windows 10. Some longstanding upgrade blocks have been lifted as of July 11, 2019. The Release Information page for the feature update lists three issues marked as resolved. Systems that were affected by these issues previously are no longer blocked from finding the update via Windows Update. The three issues that are resolved are: Systems with external USB devices and memory cards are no longer blocked from installing Windows 10 version 1903. The Dolby Atmos and Dolby Access issue is resolved. The Dynabook Smartphone link app issue is resolved. Microsoft confirms that the upgrade hold is no longer in place and notes that it may take up to 48 hours before affected devices may find the new feature update when admins run manual checks for updates in Windows Update. This issue is now resolved and the safeguard hold has been removed. Please note, it can take up to 48 hours before you can update to Window 10, version 1903. It may take until July 13, 2019 before the new update is listed on Windows Update. The update is listed as an optional upgrade if the device runs Windows 10 version 1809. If an older version of Windows 10 is installed, it may be installed right away without giving the admin any option. (via Deskmodder) New issues [Poster's note: More info on this bug in an earlier post... https://www.nsaneforums.com/topic/348366-windows-10-kb4507453-cumulative-update-causes-restart-alert-loop/ ] Some Windows 10 version 1903 devices may enter a restart notifications loop after installing the KB4507453 which was released as part of the July 2019 Patch Day. The issue affects some devices only. The notification to restart the device after the installation of the update does not go away after the restart on affected devices. Windows notifies the user that a restart is required, but no matter the times the system is restarted, continues to display the notification. Microsoft has not acknowledged the issue yet. A potential workaround involves using the restart option displayed by the restart prompt to resolve it. (via Günter Born) Some Windows 10 users reported that the SFC /Scannow option was not working properly after the installation of the most recent updates for the operating system. The issue was traced back to the most recent Windows Defender definitions that interfered with the program execution. (via Windows Latest) Last but not least, a new black screen issue reportedly affects Remote Desktop Protocol windows on Windows 10 version 1903. (via Windows Latest) Source: Windows 10 version 1903: some upgrade blocks lifted and new problems (gHacks - Martin Brinkmann)
  16. Systems administrators: You need to know about this Windows 10 1903 patching change Microsoft is changing how WSUS and Configuration Manager will handle patches as of Windows 10 1903. Here's what admins need to know. Credit: Microsoft Administrators who manage Windows updates should know about a change Microsoft has made to how patches will be handled starting with the May 2019/1903 update. The change is connected to work Microsoft is doing underpinnings to the Microsoft update systems infrastructure. I first learned about this change thanks to Configuration Manager architect Bryan Dam who runs the damgoodadmin.com site. Microsoft blogged about the change late in the day on May 23, a couple of days after Windows 10 1903 and Server 1903 began rolling out. Those using System Center Configuration Manager or Windows Server Update Services (WSUS) to patch their systems need to make a one-time change to the settings around getting updates and patches for Windows 10 1903 and Server 1903 or later, as Microsoft noted in its blog post today. Admins/users need to manually configure the settings for 1903 in ConfigMan and WSUS, according to Microsoft, because of work it's doing around the Unified Update Platform (UUP). From Microsoft's post: "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.)" In order to deploy updates to Windows 10 1903 or Server 1903, Configuration Manager version 1902 or later is required, Microsoft's post notes. Admins will not have to select a new option each time a feature update is released for Windows 10, Server and/or Configuration Manager; Microsoft officials said they plan to automatically add this new catory to software update synchronization and existing automatic deployment rules as of the next version of Configuration Manager. Updates for Windows 10 1903 and Windows Server 1903 -- and their future follow-ons -- are being released under new version-specific product categories, as Dam explained in a May 22 blog post. And those using Configuration Manager or WSUS need to know this so they can manually change required settings. The Windows 10 1903 and Server 1903 feature updates were both published under the existing Windows 10 product category. But starting with the first updates for these feature updates, the product categories change to version-specific. As Dam noted in his own blog post this week, if admins don't make these changes manually this time around, "the OS updates for the 1903 versions may not sync/apply/deploy/whatever if the technology you use to apply updates filters by the product category in any way." His advice: "Every ConfigMgr or WSUS administrator on the planet will need to manually enable these new categories if they plan to deploy updates for them," Dam said. There's not a lot of published information that I could find about UUP. But here is one story from last year's Ignite conference about UUP, which said UUP is meant to enable companies to use servicing instead of "media-based" technologies for feature updates. As of Ignite last fall, Microsoft was saying UUP would be in public preview for WSUS and ConfigMan customers before year end. UUP is already the default for customers using Windows Update, the story said. Source
  17. Microsoft released Windows 10 May 2019 update a few weeks ago. It is annoying to see that the tech giant failed to resolve many software issues and other bugs after all this time. Windows 10 users are still reporting new issues on Windows forums every day. On top of that, every new patch brings its own set of problems rather than solving the old ones. Recently, many users who upgraded to Windows 10 v1903 reported that Photoshop and Snagit stopped working on their computers. Adobe Photoshop is a popular image editor tool among users. Snagit is a tool that allows users to record videos and capture screenshots. Thousands of people use both of them on a daily basis on their Windows 10 systems. This situation is pretty frustrating for all of them. The OP failed to find a way to resolve this issue. Unfortunately, we could not find the root cause of the issue neither because the user didn’t provide the forum community with enough details. Is there any workaround to resolve the problem? At the moment, there is no workaround to resolve the problem. The Windows 10 community hopes that Microsoft will acknowledge and investigate the issue. Hopefully, Microsoft will release a patch very soon. Meanwhile, we have listed some quick solutions that might help you out. How to fix Photoshop and Snagit issues on Windows 10 v1903 1. Restore to a previous version If the issue occured after you have installed Windows 10 v1903, a quick solution is to rollback to the previous stable build. Alternatively, you can go for a clean install if there is no restore point created on your system. 2. Install the latest software updates Apparently, the issue is not related to the software and belongs to the update itself. However, if you are experiencing the same problem, you need to ensure that you have installed the latest software updates — just in case. Source
  18. Windows 10 1903: We'll still update PCs with less than 32GB storage, says Microsoft Microsoft clarifies that the new 32GB storage minimum for Windows 10 version 1903 is only for newly built PCs Ahead of the Windows 10 version 1903 release, Microsoft said in an April support document this version would raise the minimum storage capacity to 32GB for 32-bit and 64-bit Windows. The company didn't explain why Windows 10 required more storage but as ZDNet reported at the time, the Windows 10 May 2019 Update, aka 1903, also introduced 'reserved storage', roughly 7GB of disk space to ensure updates don't fail. Microsoft has now clarified in a recent support document aimed at IT pros that this minimum requirement for Windows 10 1903 doesn't apply to PCs that are already in use, only to OEMs manufacturing new PCs. So, Windows 10 users with 32GB PCs can still expect to receive version 1903 at some point in future. "New disk space requirement for Windows 10, version 1903 applies only to OEMs for the manufacture of new PCs. This new requirement does not apply to existing devices," said Microsoft. "PCs that don't meet new device disk space requirements will continue to receive updates and the 1903 update will require about the same amount of free disk space as previous updates." As for why OEMs won't get Windows 10 version 1903 on systems with less than 32GB, Microsoft points to its explanation about reserved storage, which will be enabled automatically on new PCs with Windows 10 1903 pre-installed and for clean installs. "It will not be enabled when updating from a previous version of Windows 10," Microsoft notes. The document also details key Windows 10 update control and quality improvements that Microsoft made in the wake of the disastrous Windows 10 version 1809 rollout, such as the ability for Windows to automatically uninstall certain updates if they trigger a startup failure. "You can now automatically recover from startup failures by removing updates if the startup failure was introduced after the installation of recent driver or quality updates. When a device is unable to start up properly after the recent installation of Quality of driver updates, Windows will now automatically uninstall the updates to get the device back up and running normally," the document states. Microsoft also highlights the new option for Windows 10 Home users to pause updates for 35 days, which again was part of its response to version 1809. Additionally, Windows will now display a coloured dot on the Power button in the Start Menu and Windows icon in the taskbar to indicate there's an update requiring a device restart. Source
  19. Windows 10 1903, Windows Server 1903 to drop password expiration requirements in proposed security guidelines Today on the Microsoft Security Guidance blog, the company has published an explanation of its draft release of its security configuration baseline settings for Windows 10 1903 and Windows Server 1903. This document sets guidelines for Group Policy baseline settings, and with this latest draft there are some significant changes. Among the most noteworthy is a change to no longer set password expiration policies that require “periodic password changes,” a long standing baseline that Microsoft says has become “an ancient and obsolete mitigation of very low value.” The blog post goes on to explain why Microsoft is dropping the password expiration policy, noting first that “we are not proposing changing requirements for minimum password length, history, or complexity:” Periodic password expiration is a defense only against the probability that a password (or hash) will be stolen during its validity interval and will be used by an unauthorized entity. If a password is never stolen, there’s no need to expire it. And if you have evidence that a password has been stolen, you would presumably act immediately rather than wait for expiration to fix the problem. While the baseline guidelines are dropping the outdated expiration policy, the blog post also notes that “we must reiterate that we strongly recommend additional protections even though they cannot be expressed in our baselines,” and notes that Azure AD password protection and multi-factor authenitcaion are much better alternatives. In addition to the news about password expiration, default disabling of built in Guest and Administrator accounts are also being proposed for elimination. Note that removing these settings from the baseline would not mean that we recommend that these accounts be enabled, nor would removing these settings mean that the accounts will be enabled. Removing the settings from the baselines would simply mean that administrators could now choose to enable these accounts as needed. The proposed guidelines are just that, proposed, and interested parties can download the draft and comment via the blog post. Source
  20. Windows 10 says Hello to no passwords with FIDO2 certification Microsoft moves 800 million people closer to a no-password world. Microsoft has passed another milestone on its quest to kill off passwords. The company has now gained official FIDO2 certification for Windows Hello, the Windows 10 biometric authentication system. The certification applies to Windows 10 version 1903, aka the May 2019 Update, which is scheduled to be released to the public in late May and means Windows Hello has been approved as a FIDO2 'authenticator'. Windows Hello offers Windows 10 users access to their devices by using a fingerprint or facial-recognition sensors on the PC as well as PINs. "No one likes passwords (except hackers)," says Yogesh Mehta, group manager for Microsoft's crypto, identity and authentication team in Azure Core OS. "People don't like passwords because we have to remember them. As a result, we often create passwords that are easy to guess – which makes them the first target for hackers trying to access your computer or network at work." Consumers can expect to start seeing FIDO Certified logos on new Windows 10 PCs, and they'll be able to sign in to online accounts using Windows Hello on all PCs upgraded to version 1903 using the FIDO2 standard. The certification is part of an industry-wide push for passwordless sign-in, which includes the WebAuthn or Web Authentication WC3 standard that's supported by Mozilla Firefox, Microsoft Edge, and Google Chrome. The standard also has preview support in Apple Safari while Chrome on Android has been officially FIDO2 certificated. With WebAuthn users can register and authenticate on websites or apps using an 'authenticator' – such as Windows Hello – instead of a password. That authenticator can be a hardware security key that the user has connected to a computer. It can also be a biometric ID acquired from a PC or smartphone biometric sensor. WebAuthn was officially endorsed in March. The Windows 10 1903 FIDO2 certification extends beyond Microsoft's own software. For example, Windows 10 users who prefer Mozilla Firefox will be able to log into their Microsoft Account and other FIDO-supporting sites with Windows Hello. Additionally, users of Microsoft's Chromium-based Edge will be able to do the same soon. Microsoft sites that users should be able to sign into with Windows Hello – be it on Edge, Chrome or Firefox – include Outlook.com, Office 365, Skype, OneDrive, Cortana, Microsoft Edge, Xbox Live on the PC, Mixer, Microsoft Store, Bing, and MSN. While major online services like Dropbox currently support WebAuthn, not everyone's convinced that Microsoft's Windows Hello technology is suitable. UK banking group Lloyds recently announced it had no intention to support Windows Hello for logging into online accounts. Source
  21. Windows 10's 'Sets' feature is gone and not expected to return Sets, Microsoft's Windows-management feature which allowed users to group data, sites and other information in tabs, is gone and not expected to come back in a future release of Windows 10, my contacts say. In 2017, Microsoft officials provided a preview of two new features coming to Windows 10: Timeline and Sets. Timeline made it into Windows 10 as part of the April 2018 Update, but Sets didn't. And it's looking like it never will be included in Windows 10. My sources say Microsoft dropped plans for Sets, a Windows-management featurewhich would have allowed users to group app data, websites and other information in tabs, months ago. Although Microsoft did test Sets last year with some of its Windows Insider testers, the feature generally wasn't well received or understood. For apps like Office to work well with Sets, the Office engineering team was going to have to do a lot of extra work Sets didn't make an reappearance in the Insider test builds leading up to the May 2019 Update/1903, and officials haven't mentioned the Sets feature in months. Over the weekend, Microsoft Senior Program Manager Rich Turner tweeted "The Shell-provided tab experience is no more, but adding tabs is high on our to do list." (That's likely the closest we will get to an "official" comment on the future of the Sets feature.) Turner pointed to a Devblogs.Microsoft.com post originally dated June 29 about tabs coming to the Windows Console. At that point in time, the Console team was planning to use the new Sets feature as the base for adding Tabs in the Windows Console. But since the Windows team has decided against moving forward with Sets, the Console team is now going to have to build Tabs into the Console without using Sets as the foundation, my sources say. When Microsoft first unveiled Sets, officials said the feature might or might not make it into the Windows 10 April 2018 Update. But the goal was to ship that feature at some point as part of a Windows 10 feature update. At first, Sets was going to work only with Universal Windows Platform (UWP) applications. But over time, Microsoft was planning to optimize full Win32 apps like Office to work with the Sets tabs. Microsoft officials also were hoping to help third-party Win32 apps to be optimized to work with Sets over time. When the Microsoft Edge team began work on moving to the Chromium engine last year, they had to make a choice about whether or not to redo the work necessary to integrate with Sets. Doing so could have delayed Chromium-based Edge significantly -- or resulted in Sets integration not coming to the new Edge browser until months after it debuted. So that helped finalize the decision to table Sets, my contacts say. Windows users who still want a feature like Sets can buy the Stardock application called "Groupy," which allows users to group app data, websites and other information in tabs Source
  22. Start10 Start Menu App Gets Support for Windows 10 Version 1903 Light Theme Start10 is one of the applications that provide Windows 10 users with a more customizable Start menu experience, and the latest update prepares it for the upcoming May 2019 Update. The next feature update for Windows 10 will introduce a new light theme, in addition to the dark mode, so icons and other applications need to be updated to align with this new visual facelift. With version 1.7, Start10 officially supports the light theme in Windows 10 May 2019 Update, and as you can see in the screenshots here, its look blends into the OS user interface quite nicely. At this point, Start10 is one of the most advanced third-party Start menu apps on Windows, and it’s no wonder why. The level of customization that it offers is insane, and you can choose between multiple Start menu styles (including Windows 7 and Windows 10), themes, various Start button designs, and so much more. The only problem with Start10 is that it doesn’t come with a freeware license, so you need to pay $4.99 when purchasing it as a stand-alone application.Windows 10 Start menu improvementsMeanwhile, the default Start menu in Windows 10 is also getting its own bunch of improvements with the upcoming May 2019 Update. For example, the Start menu now comes as a separate process for improved performance on Windows 10. “By insulating Start from potential issues impacting other surfaces, Insiders saw measurable improvements in Start reliability. With the new app in place, Start was opening significantly faster. Even better, because Start is such a big part of the overall Windows experience for most users, we saw these reliability improvements contributing to performance improvements for the entire OS,” Microsoft explained. Windows 10 May 2019 Update is projected to launch late next month, and you can try it out by enrolled in the Release Preview ring of the Windows Insider program. Source
  23. Microsoft makes Windows 10 1903 available on MSDN Surprise: Microsoft has made the Windows 10 1903 (May 2019 Update) and Windows Server 1903 bits available for download on MSDN, a month earlier than many were expecting. On April 18, some tech pros began noticing that Microsoft had made its Windows 10 1903/May 2019 Update release available on MSDN for download. If Microsoft hadn't changed its Windows 10 servicing cadence a couple weeks ago, this would be business as usual. But, in early April, Microsoft officials said the plan was to make Windows 10 1903/May Update available to consumers and business users starting in late May, not in mid-April. From Microsoft's April 4 blog post about plans to change the Windows 10 update experience in the name of improved quality: "Our commercial customers can begin their targeted deployments in late May, which will mark the beginning of the 18-month servicing period for Windows 10, version 1903 in the Semi-Annual Channel. We recommend IT administrators start validating the apps, devices and infrastructure used by their organizations at that time to ensure that they work well with this release before broadly deploying. The May 2019 Update will be available in late May through Windows Server Update Services (WSUS), Windows Update for Business, the Volume Licensing Service Center (VLSC) for phased deployment using System Center Configuration Manager or other systems management software." Microsoft's plans for 1903 was to give the "RTM" bits longer to bake in the Windows Insider Release Preview ring, as well as inside Microsoft, its OEM, and ISV partners before making the new bits available to mainstream customers. Microsoft pushed out the Windows 10 1903/May Update bits to Insider testers in Release Preview on April 8. Officials said earlier this month that business customers would be able to start testing the commercially available 1903/May update internally in late May, and that Microsoft would use the late May date when it begins rollout as the start of the 18-month support period for Windows 10 1903. Yet now, on April 18, Windows 10 1903/May Update (Build 18362.30) and its Windows Server 1903 complement both showed up on MSDN for download, as noted by Tero Alhonen and WZor.NET on Twitter. The 1903/May Update bits are not yet available in the Evaluation Center or VLSC. I contacted Microsoft officials to see if this was a mistake on its part or if Microsoft intended to make the coming release available a month or so ahead of schedule for those with MSDN subscriptions. Or maybe Microsoft's (unstated) intention was to get IT pros to start kicking the tires of the near-final Windows 10 1903/May Update in a controlled-pilot kind of way by putting the bits on MSDN? So far, no response form Microsoft on this. Update: It's increasingly looking like this was not a mistake, but intentional. In early April, Microsoft officials never shared when they planned to release the 1903/May Update bits on MSDN. In the past, Microsoft usually released RTM bits to MSDN around the same time they went to VLSC and other "mainstream" business channels. But it looks like Microsoft is going with the literal definition of MSDN -- Microsoft Developer Network -- and not looking at it as a business/IT pro channel. And so 1903's release on MSDN is tied to the SDK release today. Microsoft released the Windows 10 Software Development Kit (SDK) for the May 2019 Updateon April 18 with a "go-live" license and told developers they could start developing on the Windows 10 May 2019 Update now. Source
  24. Microsoft releases KB4505903 for Windows 10 version 1903 Microsoft released the second cumulative update for Windows 10 version 1903, KB4505903, on Friday evening to the public. The company tested the update previously in Insider versions to give it another round of testing before releasing it to the public. KB4505903 was released on Thursday initially but Microsoft pulled it on that day to re-release it on Friday. No word on why it was released and then pulled on Thursday. KB4505903 is a massive update for Windows 10 version 1903 that fixes lots of issues. Note that it is still considered a pre-release update as it is only available when administrators run manual update checks or download it from other sources. KB4505903 for Windows 10 version 1903 Support article Microsoft Update Catalog Here is the list of fixes in that update: Fixed an issue that failed to record a local user's last sign-in time. Fixed an issue that might "sever the domain trust relationship" when you enable Recylce Bin in the domain that established the relationship. Fixed Windows Hello authentication not working after a restart. Time Zone information for Brazil updated. Fixed multiple PDF issues in Microsoft Edge, e.g. fixed printing of documents that contain landscape and portrait-oriented pages. Fixed an issue on systems with 10-bit display panels that would show colours incorrectly when viewing images. Fixed an issue that prevented the changing of the brightness after resuming from Sleep or Hibernation. Fixed an issue that returned an empty font family name for Bahnschrift.ttf. Fixed an issue that caused an extra mouse event to be produced on press and release. Fixed the UI stop responding issues when scrolling in windows that has many child windows. Fixed an issue that caused automatic sign in to be bypassed when holding down the Shift key during startup. Fixed an issue that prevented devices from going into Sleep mode when "certain applications that rely on Bluetooth are open". Fixed an issue that caused the Bluetooth audio quality to be reduced. Fixed an issue that prevented Microsoft Application Virtualization scripting from working. Addressed a OneDrive files on-demand opening issue on systems with User Experience Virtualization enabled. Admins need to set the following value to 1 to apply the patch: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UEV\Agent\Configuration\ApplyExplorerCompatFix Fixed another User Experience Virtualization issue that prevented exclusion paths from working. Fixed an issue that may cause systems with Trusted Platform Modules from working. Fixed an issue that prevented systems from recognizing Microsoft accounts or Azure Active Directory accounts until users signed out and on again. Addressed an issue that prevented the Netlogin service from establishing secure channels. Fixed an issue that prevented the PIN policy from updating for Windows Hello for Business when a PIN existed on the system already. Fixed an issue that prevented the creation of recovery drives. Fixed an issue that prevented an Android emulator based on the virtual machine platform from starting. Fixed an issue that caused users to sign in with a temporary profile in a local user account when it was configured with a mandatory roaming user profile. Fixed an issue that changed the status of Work Folders in File Explorer to 0x80C802A0. Fixed a Remote Desktop Server stop responding issue when someone disconnects who uses drive redirection. Fixed the RASMAN Remote Access Connection Manager service stop working issue. Fixed a connectivity loss issue for applications on a container host. Fixed an issue that prevented connections to a corporate network when using Always On VPN with the IKEv2 protocol. Added limited support for Windows Voice Dictation for Chinese Simplified, English (Australia, Canada, India, United Kingdom), French (France), German (Germany), Italian (Italy), Portuguese (Brazil), and Spanish (Mexico, Spain). Fixed the Windows-Eye screen reader issue. Fixed an issue that prevented App-V applications from opening. Fixed an issue that caused Windows Defender Advanced Threat Protection to lock files so that they cannot be accessed by other process. Fixed an issue that caused Start to stop responding when new users sign in. Updated Windows Ink Workspace by "simplifying the menu and adding direct integration with the Microsoft Whiteboard app for a richer collaboration experience.". Microsoft lists three known issues: Windows Sandbox may fail to start. The Preboot Execution Environment issue is still a thing as well. Devices connected to a domain that is configured to use MIT Kerberos realms may not startup or may continue to restart. Source: Microsoft releases KB4505903 for Windows 10 version 1903 (gHacks - Martin Brinkmann)
  25. Microsoft has placed a compatibility hold on Windows 10 devices that prevents them from upgrading to Windows 10 1903 if they are using older Intel Rapid Storage Technology drivers. This is because certain versions of the software could cause Windows 10 to crash or not operate properly in version 1903. If a Windows 10 user has Intel Rapid Storage Technology (Intel RST) driver versions between 15.1.0.1002 and 15.5.2.1053 installed, Windows 10 will not upgrade to version 1903. Instead, a user with this compatibility hold will see a message stating: "Intel Rapid Storage Technology (Intel RST): The inbox storage driver iastora.sys doesn’t work on these systems and causes stability problems on Windows. Check with your software/driver provider for an updated version that runs on this version of Windows" Windows 10 Setup Message about Intel RST Drivers Microsoft has stated that Intel RST driver versions 15.5.2.1054 or later are compatible and will remove the block and allow the Windows 10 1903 to proceed. For those devices using these drivers, Microsoft recommends that you use version 15.9.6.1044 of the driver even though newer drivers exist. How to resolve the Windows 10 1903 upgrade block To upgrade your driver, you should check your hardware manufacturer web site and see if a newer version is available for your computer model. This is the recommended solution by Intel when upgrading your Intel RST drivers as some manufacturers customize the driver for their particular hardware. If a compatible version does not exist on the manufacturer's site, you can download the latest Intel RST drivers directly from Intel. As previously stated, Microsoft recommends driver version 15.9.6.1044, but the latest one offered by Intel is currently version 17.5.1.1021 and includes includes functionality and security updates. Source
×
×
  • Create New...