Windows 10: Microsoft acknowledges that Windows 10 has a internet problem

We recently reported that a recent Windows 10 update (KB4541335) was causing installation issues and crashing people’s computer. While Microsoft has yet to acknowledge problems with Windows 10 optional cumulative update, the company recently confirmed a new bug in the OS that causes internet issues.

Microsoft says the bug is hitting some systems and it affects Windows 10 November 2019 Update or May 2019 Update. As per the software giant, internet connection could stop working on some PCs with a limited or no internet connection status in the notification area.

Devices with a manual or auto-configured proxy such as VPNs are most likely to experience Windows 10’s limited internet connection problem. According to Microsoft, the issue is linked to Windows 10’s February 27 cumulative update KB4535996 and it might happen when you are connected to a VPN or disconnected from a VPN connection.

Unfortunately, apps that use WinHTTP or WinInet are plagued with another bug that could prevent such apps from accessing internet content. Microsoft is currently aware of the issue affecting Microsoft Teams, Office, Outlook, Office 365, Internet Explorer and even some versions of Edge.

It’s unclear how widespread issues with Windows 10 update are and we couldn’t find any online threads discussing it actively. Additionally, since the update KB4535996 is optional, it’s possible that many people have already skipped it due to other issues.

The good news is that Microsoft has already started working on a hotfix for Windows 10 users, but it could take at least two weeks until it lands.

The tech giant is currently planning to publish an out-of-band patch in early April and it’ll be bundled with a future Windows 10 Patch Tuesday release as well.

If you see limited or no internet connection error when VPN is connected or disconnected, you can restart your device multiple times and your internet should be back, as Microsoft noted.

This is just a temporary fix and you might get the same error again after a few days, but since no proper workarounds are available, restarting your device is the best solution for now.

To permanently fix the bug, you can also reinstall Windows 10 and skip February patch if it shows up when you check for updates.

The post Microsoft acknowledges that Windows 10 has a internet problem appeared first on Windows Latest

Weiterlesen...

 

Microsoft Internet Explorer renamed to Windows Internet Explorer ?




Since version 7 of the world`s most popular web browser - Microsoft Internet Explorer was silently renamed to Windows Internet Explorer.Such a step from Microsoft is not a surprise since Internet Explorer is part of the Windows operation system for a long time.Obviously Microsoft corp. wants to state that Internet Explorer is already considered as a part of Windows and not as an external browser (remember the IE and WMP law issues last year!?).

 

Microsoft Selects Dolby Audio for Windows 10

it would've been great if microsoft added HEVC decoders, LAV filters along with other codecs with Windows 10, and developing WMP to be better than VLC, KMPlayer and such sorts of media players.

Nevertheless, this is good step for microsoft, by far.

 

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