Updated:11:53 AM EDT Oct 14


this is ggmania.com subsite Some bugs in Win 10 (1803) fixed, others persist - TechAmok

Some bugs in Win 10 (1803) fixed, others persist - [briefly]
05:20 PM EDT - Jul,01 2018 - post a comment

Computerworld continues their critical analysis of Windows 10: while Microsoft released a patch this week (KB 4284848) fixing two major bugs related to the SMBv1 protocol and Edge browser, they advise that Windows 10 1803 is still riddled with old problems. These include Intel NIC and VLAN issues, Chrome conflicts, and lack of home network connectivity.

Microsoft may think that Win10 (1803) is ready for widespread deployment, but there are a few folks who would take issue with that stance.

Yesterday, Microsoft finally released a fix for two big bugs that have dogged Win10 1803 since its inception. In theory, patch KB 4284848 fixes these acknowledged bugs:

  • Some users running Windows 10 version 1803 may receive the error "An invalid argument was supplied" when accessing files or running programs from a shared folder using the SMBv1 protocol.
  • Microsoft Edge may stop working when it initializes the download of a font from a malformed (not RFC compliant) URL.

In practice, life isn't so simple. WSUS (the Windows Update Server software) isn't "seeing" KB 4284848, as of late Wednesday afternoon -  which may be a good thing.

Old problems remain in abundance. There are many reports of munged Intel NICs and VLAN problems after installing 1803. Josh Mayfield (whom you may recall from GWX days) reports that you're forced to set up a PIN during fresh installs. The ancient problem with restore partitions getting assigned drive letters on install remains. Chrome continues its indigestion with 1803, although Microsoft claims the latest patch cures all ills. None of this is acknowledged anywhere I can see.

One problem that has been acknowledged - but only by a Microsoft Agent on an Answers Forum post - says that installing 1803 can clobber your peer-to-peer network. That certainly matches my experience. With earlier versions of Win10, I'd fire up the Homegroup Troubleshooter and that usually solved the problem. Unfortunately, Microsoft discontinued Homegroups in version 1803.



Add your comment (free registrationrequired)

Short overview of recent news articles

Oct,14 2018 Facebook Wants to Put Video Cameras in Your Private Spaces
Oct,14 2018 Apple Plans to Give Away Original Content for Free to Device Owners
Oct,14 2018 Netflix cancels Marvel's Iron Fist
Oct,14 2018 Jonathan Trailer #1 (2018)
Oct,13 2018 Intel Core i9 9900K vs AMD Ryzen 7 2700X
Oct,12 2018 Samsung Says Foldable Phone to Act Like Tablet
Oct,12 2018 Facebook Says Hackers Accessed Users' Personal Data
Oct,12 2018 Maria Doroshina - Fit Russian Blonde Beauty
Oct,12 2018 2018 Most Popular Women Tennis Players
Oct,12 2018 AMD Radeon Adrenalin 18.10.1 Drivers
Oct,12 2018 NVIDIA GeForce 416.34 WHQL Game Ready Drivers
Oct,11 2018 Could You Answer Elon Musk's Tricky Interview Question?
Oct,11 2018 Samsung Galaxy A9 Adopts 4-Camera Configuration
Oct,11 2018 Fortnite for Android No Longer Requires An Invitation
Oct,11 2018 Samsung reported to be dropping 3.5mm jack with Galaxy S11 and Note
Oct,10 2018 Asus Confirms Plans to Sell ROG Phone In the US for $899
Oct,10 2018 Haunted - Official Trailer [HD] | Netflix
Oct,10 2018 Pet Sematary Trailer #1 (2019)
>> News Archive <<

TechAmok - Privacy Policy        loading time:0.01secs