Messages

1

General Computer Support / Re: The Trusted Platform Module (TPM) firmware has a known security problem Error

« on: November 19, 2017, 05:37:37 pm »

Thanks for the suggestions.  I, too, generally ignore the DCOM errors, but I'm in pursuit of faster startup.  (Currently about 2.5 minutes from power-up to Win 10 lock screen, then another 1.5 - 2.5 mins of spinning circles to desktop and spinning mouse pointer on desktop until I can run an application.)  And I've run out of the "simple fixes" like turning of the AppExperience scanner, indexing and unnecessary application installed startup routines.  Yeah, I should just enjoy powering on, going to get my coffee, logging in and going to get my snail-mail THEN coming back to a machine finally ready to get my email (perks of being retired).  But with "too much time on my hands" I get off on tangents looking for perfection .

Anyway, after posting I revisited HP support drivers / software site and found an update to Intel Management Engine firmware I had not yet gotten.  I first did a repair re-install of the latest IME Driver before installing the new IME firmware, and that got rid of the TPM errors and the original DCOM startup error.  Now I have 5 new DCOM errors relating to two DCOM CLSID / APPIDs. Hopefully I can deal with those using the MS TechNet solution (haven't checked yet).  The last one I could not do that with because neither the CSLID/APPID registry key nor the DCOMcnfg entry for the offending APPID existed.

But I'm happy that at least the TPM error has disappeared.  That one concerned me whereas the DCOM 10016 errors just irritate me. 

2

General Computer Support / The Trusted Platform Module (TPM) firmware has a known security problem Error

« on: November 18, 2017, 05:54:37 pm »

Windows 10 "Fall Creators Update", build 16299 on HPz840 workstation.  This event showed up after the "Creators Update" and its first patch from Windows Update.

-------------------------------------------
Event log:
Log Name:      System
Source:        Microsoft-Windows-TPM-WMI
Date:          11/18/2017 5:11:01 PM
Event ID:      1794
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      TIGER
Description:
The Trusted Platform Module (TPM) firmware on this PC has a known security problem. Please contact your PC manufacturer to find out if an update is available. For more information please go to https://go.microsoft.com/fwlink/?linkid=852572

-----------------------------------------------------------

I installed the latest BIOS (UEFI) and Intel chip set drivers as well as Intel Management Engine drivers and this event did not go away.  I ran Tweaking.com starting with all the pre-repair steps, booting each time into safe mode.  That SEEMED to cure the problem including a slew of DCOM permission problems (event 10016) that occured during shutdown.  However, it also caused a new DCOM error during startup for two components like this:
-----------------------------------------------------
Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          11/18/2017 5:10:03 PM
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          LOCAL SERVICE
Computer:      TIGER
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{10DA4F3C-CC99-4190-BE4D-58330754E882}
 and APPID
{7DDEFEA6-98EE-4F13-A25B-EC83D9BC5541}
 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.
----------------------------------------------------------------

I ran the "preset: Permissions Only" repair thinking it would clean those errors up.  And it did for those components, but lead to the permissions event for the component as posted above and the TPM error returned.

Any ideas on how to solve these two issues once an for all?

NOTE: Neither HP nor Microsoft websites offer any solutions.

Thanks for any help that can be offered.

NOTE2:  I ponied up for the "Pro" version of Tweaking, so if there is in the Advance Repairs or Tools tab that can help with repair or diagnosis, those options are available to me.

3

Feedback & Suggestions / Re: What Have You Done to My Machine?!?!

« on: September 14, 2016, 06:43:31 pm »

(Somewhat cooler now...) The directory exists with a sub-dir named after my machine's network ID, but with nothing else in it. (Its a zero size sub-dir).

Where was the restore point supposed to go?

It appears the main problem with rebooting was the GFX card's slow (3-day long) death throws to where it stuck in an endless reboot cycle when it got to the Win logo screen.  BIOS loading messages to the screen before OS load degraded to mush and vertical corduroy - the final clue.  I've been running for about 4 hours on an outdated (NVIDIA QuardFX 1800) card and all seems well - at least I can now wade through the raft of errors and warnings left in the Event Log since the scrambling occurred.  Most of them seem to be due to dismantling of HomeGroup, weird permissions and start settings on associated services, attempts to logon to some domain (never been part of one - just the default "WORKGROUP" for my small 5 machine home / office network), and trashing of some permissions and startup settings for McAfee services (virus, firewall, spam policing, etc.)  There are still a handful of error messages I didn't have before the scrambling that I have no idea how to fix. (EX: "Error   9/14/2016 5:08:38 PM   NETLOGON   3095   None (Task Category)   This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration."  or "Warning   9/14/2016 5:08:38 PM   TaskScheduler   414   Task Misconfiguration   Task Scheduler service found a misconfiguration in the NT TASK\Microsoft\Windows\Workplace Join\Automatic-Workplace-Join definition. Additional Data: Error Value: %SystemRoot%\System32\AutoWorkplace.exe." etc.)

I would still dearly love to know how the reg backup, the restore point (supposedly) done by Tweaking.com - Windows Repair, and the restore point I made right before running .... Repair... (plus ones created by system installers / updaters) were all removed from the system apparently as part of the repair process.

4

Feedback & Suggestions / Re: What Have You Done to My Machine?!?!

« on: September 13, 2016, 10:26:01 pm »

The program DID NOT do either a registry backup or create a restore point in response to selecting those buttons on one of the tabs.  When I clicked them the UI flashed and that was it.  I thought, "wow, that's fast."  But after the scrambling (aka "repair") step, when I went to use the restore point, I got the system panel that told me there were NO restore points to restore to.  This includes the one I made myself right before running Tweaking.com - Windows Repair.  Then I tried the restore registry button - guess what - no saved registry to restore from.

So I went manually searching for where you might have saved the backed up registry.  Couldn't find it anywhere.  So, no, your program did neither such thing except perhaps to some temporary / imaginary location that ceases to exist as soon as the scambling (aka "repair") has been "accomplished".  And there is no record of them having been made in any of the log files left behind after I uninstalled this ..... GRRRrrr!

(Log files attached).

5

Feedback & Suggestions / What Have You Done to My Machine?!?!

« on: September 13, 2016, 12:43:17 am »

I ran Tweaking to repair a system which sfc and standard dism, chkdsk etc found no problems with but which kept randomly rebooting of turning off all output to the monitor.  Now, I can't set default programs, (among other settings that I can no longer change either in the new Windows 10 settings or traditional control panel - I click a choice but nothing happens, and my choices are ignored.  It appears you somehow set permissions to all these settings so that I, as Administrator cannot set them.

Further, the advent of a random restarts / black screens comes quicker and in larger number after the so-called "repair".

I'd love to look at the event log, services app, dcomcnfig etc. but attempting to run any of those apps crashes the machine almost immediately.  And yes, I started from step on, and did all the optional steps before repair.  What a wast of 6 hours.

BTW, I tried to restore both the registry and to the restore point I created before I ran this sorry utility, and guess what - THE SYSTEM TELLS ME THERE ARE NO BACKUPS OR RESTORE POINTS TO USE TO GET BACK TO WHERE I WAS BEFORE THIS PIECE OF POOP SCRAMBLED MY OS!!

Thanks!  Now I have no choice but to wipe the HD and start rebuilding from scratch - a process that will likely take two months to complete.