Windows 10: Microsoft confirms a new issue in June patch for Windows 10 version 1803

Earlier this week, Microsoft released new June 2018 patches for all supported versions of Windows 10 operating system, including the newly released Windows 10 April 2018 Update (version 1803). At that time, the company acknowledged only one issue in a patch for Windows 10 April 2018 Update, but the company has recently updated the support page to include one more issue.

Microsoft has acknowledged a new issue in June 2018 patch for Windows 10 April 2018 update, which was released on Tuesday. The updated support page has confirmed a new issue that affects Microsoft Edge.

It’s worth mentioning it’s not a critical bug and it should not be a big deal for most of the users. Microsoft Edge could hit glitches where the browser would stop working “when it initializes the download of a font from a malformed (not RFC compliant) URL”.

Microsoft hasn’t issued any workaround yet, but the company says that they’re
working on a resolution and it would become available later in June. You won’t have to wait until the next Patch Tuesday, as Microsoft plans to release another cumulative update later this month.

Microsoft has already confirmed issues with SMBv1 protocol in Windows 10 April 2018 Update, and it can be addressed if you enable SMBv2 or SMBv3 on both the SMB server and the SMB client. The fix will be shipped later this month as well.

“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,” the company explains.

The June 2018 patch for Windows 10 April 2018 Update delivers a smooth user experience, and there are only two known issues.

The cumulative updates that will be shipped later this month will also include fixes to address other bugs.

The post Microsoft confirms a new issue in June patch for Windows 10 version 1803 appeared first on Windows Latest

Weiterlesen...

 

windows 10 version 1803 welcome screen?

Hello Jim,

The Windows Welcome experience will only be shown after installation of updates and occasionally when you sign in to highlight what's new and suggested by design. For more information about the new features and content of Windows 10 1803, please refer to
these support articles. It also includes a video that summarizes the new content in this release:

• What's new in Windows 10, version 1803 IT Pro content
• What's new in Windows 10, version 1803

Also, make sure that the Windows welcome experience is enabled on your PC. Follow the steps below:

• Open Settings > System > Notifications & actions.
• Under Notifications, toggle the switch On "Show me the Windows welcome experience after updates and occasionally when I sign in to highlight what's new and suggested".

Hope this information helps, feel free to post back if you need further assistance.

 

Microsoft Botches Up UEFI Support for Windows 7 on ASUS Motherboards



Microsoft suggests updating to Windows 10 to patch Windows 7

• 
  
  
• Chris Merriman
• 
  @ChrisTheDJ
• 05 May 2016

• Tweet
• Facebook
• Google plus
• Send to

9 Comments

MICROSOFT HAS confirmed a potentially lappy-borking problem that it won't be fixing, because Windows 7.

Woody Leonhard, the respected Windows columnist, points to a problem involving Asus motherboards, which also appear rebadged in a variety of other manufacturers' machines, and the activation of UEFI Secure Boot for Windows 7 in a patch KB3133977.

Short version: install update, welcome to Borksville, population you.

Both Asus and Microsoft acknowledged the problem. Microsoft entitled the article "BitLocker can't encrypt drives because of service crashes in svchost.exe process in Windows 7 or Windows Server 2008 R2", but we prefer to just call it "Trevor for brevity."

The firm's advice was that it's an optional update, leave well alone, you'll be fine, or alternatively turn secure boot off.

Then Microsoft did a silly, silly thing.

It moved the update from 'optional' to 'recommended' and anyone who reads this site regularly will know what happens when Microsoft does this. That's right boys and girls - it makes it automatically install, unless you've specifically told your machine not to.

So now, if you have one of the affected motherboard and you keep your security updates automatic like wot Microsoft recommends, then your machine will stop working properly.

We should add it's not permanently bricked, but it will take some mucking about in the BIOS to fix and that's a pain even for an experienced computer user.

Microsoft has, by offering a workaround, suggested heavily that it won't be fixing the problem, though we have asked the question, so expect a response in about a fortnight.

But the real kicker is this piece of advice: "Note The Secure Boot feature is supported in Windows 10. To learn more about the security advantages of this feature and about the upgrade path from Windows 7 to Windows 10, go to the following Windows website"

Holy toledo, this company really knows how to rub people up the wrong way.

After all - if the advice is to manually avoid the update or move to a version of the operating system where there's virtually no control over updates, then Microsoft is dealing in massive contradictions.

A more cynical site would suggest that it's yet another example of Microsoft running Windows 7 into the ground and adding built in obsolescence to encourage quicker updates. But we're not that sort of site.

Its the patching to force secure boot that is the problem win 7 does not support secure boot
hence it borks systems and well microsofts answer is Cactus >your Asshole > insert

from the inquirer

 

New win 10 version (1803) and Specter/Meltdown patch

Hi

Windows 10 version 1803 is include Specter/Meltdown patch ?

this is important for me because i don't want install them, this patches will reduce my CPU performance.