Windows 10: Microsoft pushes and pulls wrong Windows 10 update

On October 22, Microsoft started rolling out an optional cumulative update for Windows 10 version 1903 with fixes for critical bugs. In addition to the optional cumulative update, Microsoft also shipped a standalone package KB4523786 to make quality improvements to Windows Autopilot configured devices.

Windows Autopilot is commonly used by businesses and enterprises to set up and pre-configure new devices in their organizations. Businesses also use Windows Autopilot to reconfigure, recover and reset devices in the organization, and KB4523786 comes with several fixes for such devices.

A number of users have reported that Microsoft accidentally delivered KB4523786 to PCs with Windows 10 Home and Pro. If you see ‘Cumulative update for Autopilot in Windows 10 version 1903: October 22, 2019’ on Windows Update page when you check for updates, you should avoid it.

Windows 10 doesn’t immediately restart after downloading the patch. Instead, it will offer you to restart the PC and schedule the restart. In this case, you can click on pause updates for 7 days and patch will not appear again when Windows checks for updates next time.



KB4523786 is supposed to be a cumulative update for Autopilot-configured devices and not for normal installations of Windows 10. In a tweet, Microsoft’s Intune team has confirmed that the update was released accidentally and it has been pulled:

“Sorry for your experience! An Intune Autopilot update, which was targeted as part of the out of box experience for new devices, was incorrectly offered to customers running Windows Home edition during a regularly scheduled Windows update scan,” a Microsoft representative stated.

“Once we became aware of the issue, we stopped distribution of the update. If you have already installed the update, it will not affect you. If not, there is further action required”.

You can open Windows Update > View Update history to check if the update has been applied on your PC.

It’s worth noting that users haven’t reported any problems after installing KB4523786, but if you have it installed and you are experiencing unexpected problems, simply click on ‘Uninstall updates’ option and remove the patch.

The post Microsoft pushes and pulls wrong Windows 10 update appeared first on Windows Latest

Weiterlesen...

 

Microsoft to push automatic Windows 10 upgrades in 2016

"Microsoft has announced that Windows 10 will be automatically rolled out next year to all users of its older operating systems who have selected to receive updates.

Until now, users of Windows 7 and 8 have needed to register to upgrade to Windows 10. But that's about to change: soon the OS will be listed as an 'Optional Update' and -- from 2016 -- a 'recommended' update that will automatically install itself, if users have opted to receive updates in that way.*Shadedshun :shadedshu:

You can opt out of automatic updates to avoid this, but Microsoftsays that "we strongly discourage this in today’s connected world because of the constant risk of internet threats". You can also change your Windows Update settings to install critical updates but not recommended ones. Although it's still going to be possible to avoid installation, Microsoft seems quite determined for everyone to be using Windows 10 in near future.


The roll-out of reserved updates was initially staggered but, according to Microsoft, now Windows "will automatically kick off the upgrade process once you have made a reservation".

As an intermediate stage, Microsoft says that it will "soon" publish Windows 10 as an optional update, not installed by default, but accessible to all users."

http://www.wired.co.uk/news/archive...rade-to-be-rolled-out-automatically-next-year

 

Microsoft Windows 10 Fall Creators Update Available Today

Oh dear they're still pushing that. I STILL don't like the metro tiles and stuff!

 

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