Windows 10: Perfect support for Rob Koch from Microsoft. Why Microsoft is arrogant!

Greetings to all.


this is an exact example of how Microsoft staff are acting here on the support site.


Here is a link to the post: https://answers.microsoft.com/en-us...e-boot-x/3000ea4c-7eef-4dc5-9328-8d8569226903


Mr. Koch.



Why was my post locked?



Your answer to my question was really funny "You don't know what you see and so it's malware". Hahah. You're kidding.



You act as if Microsoft Windows 10 is completely bulletproof and its security is as excellent.



At the same time, we all know what it really is. For more than half a year, Microsoft has been in a vicious circle of patch fixes.



But it's still a very good fast system. And I consider him the best.



However, this is not the case with Microsoft's support.



I hereby ask you to correct it. Or tell me how to solve my problem!



Thank you.

:)

 

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

 

Microsoft Increases Windows Vista & 7 Consumer Support to Ten Years

a nice step by microsoft. still no IE10 for Vista or IE9 for xp

 

Microsoft Throwing Silverlight Under The Bus?

Excellent. Cross that off my list of things to learn. And Microsoft can start focusing on improving their HTML5 support in IE.