Hello All,
No, definitely NOT !!!
To make it short, the initial problem was that applying the Microsoft Monthly Rollup Update for 2018-MAR ( KB4088875 )
caused my AMD machine to get stuck on the reboot after installation !
This was a HUGE FLAW from Microsoft's side, and later on this issue of the flawed MS updates was widely discussed on many web sites !
It looks like ALL the Monthly updates for JAN-MAR 2018 ( which unsuccessfully attempted to correct the Meltdown security issue )
were buggy and caused many machines to be bricked or to crash, including AMD machines for which this security "fix" should NOT have been applied
in the first place !
So, I had to force a reboot of my machine through PowerOff/PowerOn, then perform several CHKDSK-s, until I got my machine working again.
At this point, my machine worked normally and there were NO WARNINGS OR ERRORS OF ANY KIND in the EventViewer System log !
I only remarked that the subsequent updates released by MS for Windows 7 64 bit machines DID NOT appear on my AMD machine,
but they DID appear on other (Intel) machines having the same OS.
For this issue I opened my other thread on this forum
Windows 7 Pro 64 (AMD) does NOT receive last updates KB4088881, KB4100480
Ultimately, MS released a new Monthly update for 2018-APR ( KB4093118 ),
which did arrive on the Intel machines the next day after its first release (on Apr 11)
and finally it also appeared on my AMD machine, but only 2 days later ( on Apr 13), after Microsoft probably modified it in some way,
as its current release date on the MS catalog is Apr 12.
When this last update attempted to be installed and DID NOT succeed, then the Events 136-137 started to appear in the EventViewer log.
Meanwhile, before this last update arrived, I also performed some backups on my machine,
and I have also seen many web sites where a backup is considered a possible culprit for the appearance of these events.
But anyway, at this moment, these events whose meaning is that the "Default Transaction Resource Manager" is NOT working
are probably those which prevent the last update to install and also prevent other actions, like performing a System Restore.
It is not clear whether these events were caused by:
1. applying the MAR-2018 update, which caused the machine to be blocked on reboot
2. performing an image backup
3. attempting to install the APR-2018 update ( the first OS update after the problematic MAR-2018 update )
Anyway, the events only started to appear AFTER all these actions.
The AutoKMS is NOT running any more, so the whole issue is purely OS-related, and more specifically Windows Update-related,
it has nothing to do with any other software that runs on my machine.
I hold Microsoft 100% responsible for all this buggy situation that they caused totally irresponsibly and unprofessionally to so many users !
Thanks a lot & Best Regards,
Iudith