Windows 10: Windows 11 - October 2023 Update - Microsoft - Why are your forcing Microsoft Windows Users...

Microsoft - Why are your forcing Microsoft Windows Users to use Google Chrome or Microsoft to use Windows Edge programs online i.e., not on a desktop application with your October 24 2023 update? Google is getting sued for basically bargaining to force people to use their search engine. Now if a Microsoft 365 user wants to login to their account they are forced to use Google Chrome of Microsoft Edge. Both are inferior browsers that hijack peoples privacy. This is exactly the anticompetetive nonsense that Google is getting sued over and Microsoft was sued in the 1990s over. THIS IS GARBA

:)

 

Microsoft Prepares Update for Windows Home Server

Microsoft's Windows Home Server officially launched earlier this month, is already preparing to be updated. Microsoft says that the new update is "part of the ongoing process of continually enhancing the customer experience with Windows Home Server." The update includes a few feature additions for Windows Home Server. Currently, users who login to their server when away from their home network - through an external URL like https://yourname.homeserver.com - are greeted with a security warning. The November 27 update will now provide users with a trusted SSL certificate for their Windows Home Severs. The SSL certification was provided with the help of Windows Live Domains and GoDaddy. Other new features include a "Delete All" button to remove home computer backups. Microsoft has also taken steps to make the Shared Folders and Server Storage aspects of Windows Home Server more robust and user friendly.

Source: DailyTech

 

Microsoft Windows Updates

Microsoft has released several updates for Windows Vista, as well as an update for Windows Media Player 11 in both XP and Vista. Download them bellow or through Windows Update.

Download

 

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