Windows 10: Microsoft Windows 10 Pro - Windows Update Problems- 0xc1900101

Your system does not seem to cater for Windows 10 Professional as it does for Windows Home . There seems to be an inerrant problem in the identification of the CPU architecture. Which deploys AMD Chipset code instead of Intel Code On Windows Professional. This could be as simple as a different registry key which holds the CPU version . As a result your Microsoft Update seems to be deploying AMD 64bit code instead of Intel x64bit code. Clearly this results in an error being reported by your installer. As sent to you on your Secure File Exchange 1459216480. This procedure is becoming open ended clearing Software Distribution only to find AMD 64bit code deployed. This problem only exists on Windows 10 Professional as the Windows Home system deploys correctly. Microsoft should provide a deployment to update the registry keys to enable updates to be usefully downloaded for the correct CPU architecture.

:)

 

Microsoft to make Windows 10 updates mandatory

Well, at the moment at least, you can choose to defer upgrades. Under Settings > Windows Updates > Advanced options you need to check the box labeled "Defer upgrades". What does that do? Good question. The answer I've found might illuminate it to a degree.

http://windows.microsoft.com/en-us/windows-10/defer-upgrades-in-windows-10

I hear this only applies to Pro and Enterprise editions. But I can't verify that.

 

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

 

Is it time for Windows 10 already?

Again, for those that want the update reservation and you meet the requirements ---> Upgrade to Windows 10 for Free

And, some info from the FAQ page:

Also, some interesting info from the Specifications page: