Windows 10: Sign in Microsoft Defender Windows 11 ASUS.

I can not Sign in to Microsoft Defender on Windows 11 ASUS. 0x800706d9 ac930e25-2ee4-0002-13c2-9dace42edb01

:)

 

Windows Defender Released

Microsoft has released the final version of its Windows Defender anti-spyware utility. Windows Defender is a product of the Microsoft acquisition of GIANT Software. Previously known as Windows AntiSpyware, after a two years beta period it's now available for Windows XP and Windows Server 2003 under the name Windows Defender. Windows Defender incorporates Real-Time Protection to monitor systems for spyware activity, automated spyware removal with scheduled scans, full integration with Internet Explorer 7.0 and automatic spyware definition updates from Microsoft. Windows Defender is available freely to all customers running a genuine copy of Windows. Microsoft has also announced that customers will each be allowed to report two support incidents for free with Windows XP and Windows Server 2003.

Source: DailyTech

 

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

 

What the hell, windows defender?

So, a while back I disabled windows defender via gpedit. Come to find out it's running again, and telling me my miner is a "severe" threat, despite still being disabled in gpedit. There's a few new entries related to windows defender in gpedit that didn't used to be there before. I'm guessing this happened during the big spring update. UAC keeps becoming re-enabled somehow, as well. For now I have a shitty registry key that's supposed to disable windows defender instead, hopefully it works.

Damn, Microsoft. They were pushing users to upgrade to 10 so hard, even resorting to plain trickery to get it on as many machines as possible. Now not only is it doing hardcore data mining in the background, but it's changing settings all on its own to whatever Microsoft wants. One step closer to pushing me to Ubuntu or something. I'd already be there if I didn't think it would be an arduous task learning how to computer all over again while simultaneously breaking a lot of games, which is mostly what I use this computer for...

Bill Gates needs to go back to Microsoft just so he can kick all the guys responsible for w10 squarely in the nuts. /rant