Sunday, September 04, 2016

Windows 10 latest build (1607) runs into a problem today (what is the "tmumh service"?


Today, Word seemed to get stuck. This is three days after the newest version of Windows 10 1607. This happened on the HP Envy Windows 10 newest rebuild as of Sept. 1, 2016.

So I tried a restart, and it kept spinning.  I reset the power button and it came up normally, and then did a restart, which worked promptly, and then was able to open Word.

I see a few diagnostics on the Event Log.  Microsoft seems to need to do a fix for this.

"The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
 and APPID
{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
 to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool."

and

"The tmumh service failed to start due to the following error:
The revision level is unknown."

I have no idea what the "tmumh service" is.  Here is a link.  It seems to come from Trend Micro. Maybe this is a Trend Micro problem interfacing with the new Windows 10 build?

No comments: