Windows 10: Windows 10 Update 20210218: 9pmmsr1cgpwg-Microsoft.heifimageextension

My computer installed the update 9pmmsr1cgpwg-Microsoft.heifimageextension this morning. I discovered this after finding that the computer had rebooted itself. Although well protected against virus' and the like, I could find no information about why the reboot happened. Upon investigation, I found no indication in View Update History that anything had been applied to the system. Reviewing the System Event Log, I found three entries that indicate that the Windows Update Client installed 9pmmsr1cgpwg-Microsoft.heifimageextension, which caused the reboot to happen. There is no no indications of an update listed in the Microsoft Update Catalog for W10-20H2 x64. The latest updates prior to this on my system were KB4601319 and KB890830 on 20210210. I understand, after researching HEIF, what the intent of the update is for. However, there is no KB document on the update that I've been able to find and zero documentation on why this was installed through automated processes originating from Microsoft and why the system hasn't updated the update history. I'd very much like an explanation as I am concerned that this may actually be an infection.

:)

 

Microsoft Selects Dolby Audio for Windows 10

it would've been great if microsoft added HEVC decoders, LAV filters along with other codecs with Windows 10, and developing WMP to be better than VLC, KMPlayer and such sorts of media players.

Nevertheless, this is good step for microsoft, by far.

 

Microsoft to make Windows 10 updates mandatory

Microsoft has already said this can be turned off.............................in a statement no less after the graphics driver glitches.

http://www.forbes.com/sites/antonyl...soft-backtracks-on-windows-10-forced-updates/

windows 10 includes an update blocking driver fail safe tool - Gizmodo

 

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