Windows 10: Microsoft Windows Security Refund

Is Microsoft Windows closing down the security service that comes with it? That's what the robocall from 562-239-4557 message said and requested I return the call for a refund. I called and a man with an apparently Indian accent said they wanted me to go to my computer and they would tell me how to collect my refund money. I said I'd prefer he explain it to me before I go to my computer. He said when I bought my computer, I paid for Microsoft Windows 10 security system, and that the security system will stop in two days so they are offering to refund the money. I said I would contact Microsoft and deal with them directly. The guy said, "then why are you wasting my time?" and cut me off. Then I read the comments here at the Microsoft web site. I will report this to the authorities. Be careful everyone!

:)

 

Microsoft Security Bulletin for September 2007

Microsoft released yesterday the September Security Bulletin for Windows operating system, as part of its monthly security cycle. This bulletin summary lists one critical and three important updates. For more information, see Microsoft Security Bulletin Summary for September 2007.

Source: Microsoft

 

Refund for an application bought on Microsoft Store

Hi,

Most apps, games, movies, TV shows, and books purchased in the Microsoft Store on Windows 10 or Xbox One are non-refundable unless the offer or applicable law states that you’re eligible for a refund. Should you have other questions and clarifications,
we suggest that you contact our
Microsoft Support team.

For detailed information about the return and refund policy, see
Microsoft Terms of Sale.

Let us know 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