Application: Open Hardware Monitor
Category: Utilities
Description: From the publisher's website:
The Open Hardware Monitor supports most hardware monitoring chips found on todays mainboards. The CPU temperature can be monitored by reading the core temperature sensors of Intel and AMD processors. The sensors of ATI and Nvidia video cards as well as SMART hard drive temperature can be displayed. The monitored values can be displayed in the main window, in a customizable desktop gadget, or in the system tray. The free Open Hardware Monitor software runs on 32-bit and 64-bit Microsoft Windows XP / Vista / 7 and any x86 based Linux operating systems without installation.
Download Open Hardware Monitor Portable 0.8.0 Dev Test 1 (736KB download / 1.54MB installed)
(MD5: 38a09ae3ffd7c197fde01414f4b5de29)
Note: This application requires administrative rights to work properly.
Note: This application requires .NET 2.0 or higher.
Release Notes:
See all release notes at the SourceForge project page.
I installed, ran, and uninstalled Open Hardware Monitor Portable 0.5.1 Dev Test 1.
For this test, I did a regshot before installing, but I also uninstalled the program before performing the second regshot; I normally do the second regshot without an uninstall. I don't know if that affected the results.
1st RegShot
Run OpenHardwareMonitorPortable_0.5.1_Dev_Test_1_English.paf.exe
Open OpenHardwareMonitor
Save Report to My Documents on C: drive
Close OpenHardwareMonitor
Right-click on icon and uninstall from PA.c platform
2nd RegShot
There are quite a few entries in the Regshot that look unfamiliar to me, and there are some files left in an 'OpenHardwareMonitor' directory on the C drive:
Values added:4
[ComDlg MRUs]
HKU\S-1-5-[...]-1001\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted\P:\PortableApps\OpenHardwareMonitorPortable\OpenHardwareMonitorPortable.exe: 0x00000001
Values modified:17
HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Autorecover MOFs: '%windir%\system32\wbem\cimwin32.mof [lots of files in %windir%\system32\wbem\] C:\WINDOWS\MICROSOFT.NET\FRAMEWORK64\V4.0.30319\MOF\SERVICEMODEL.MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK64\V4.0.30319\MOF\SERVICEMODEL35.MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V4.0.30319\MOF\SERVICEMODEL.MOF C:\WINDOWS\MICROSOFT.NET\FRAMEWORK\V4.0.30319\MOF\SERVICEMODEL35.MOF'
HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Autorecover MOFs: [the same as above, plus:] C:\WINDOWS\SYSTEM32\WBEM\FRAMEWORK\ROOT\OPENHARDWAREMONITOR\OPENHARDWAREMONITOR_SN__VERSION_0.5.1.0.MOF'
HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Autorecover MOFs timestamp: "129969047662310000"
HKLM\SOFTWARE\Microsoft\WBEM\CIMOM\Autorecover MOFs timestamp: "130022515659783000"
[PerfLib Keys]
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-2[...]-1001\RefCount: 0x00000002
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-[...]-1001\RefCount: 0x00000003
[PerfLib Keys]
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-[...]-1001\RefCount: 0x00000002
HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-[...]-1001\RefCount: 0x00000003
HKLM\SYSTEM\ControlSet001\Control\Nsi\{eb[...]bc}\24\ffffffffffffffffffffffffffffff02: 00 00 00 00 F8 25 00 00 E7 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
HKLM\SYSTEM\ControlSet001\Control\Nsi\{eb[...]bc}\24\ff[...]ff02: 00 00 00 00 FC 25 00 00 E9 00 00 00 FF [...] FF
HKLM\SYSTEM\CurrentControlSet\Control\Nsi\{eb[...]bc}\24\ff[...]ff02: 00 00 00 00 F8 25 00 00 E7 00 00 00 FF [...] FF
HKLM\SYSTEM\CurrentControlSet\Control\Nsi\{eb0[...]bc}\24\ff[...]ff02: 00 00 00 00 FC 25 00 00 E9 00 00 00 FF [...] FF
Files added:4
C:\Users\donny\Documents\OpenHardwareMonitor.Report.txt
C:\Windows\System32\wbem\AutoRecover\49133887420AF6FB5735D9982F3A2067.mof
C:\Windows\System32\wbem\Framework\root\OpenHardwareMonitor\OpenHardwareMonitor_SN__Version_0.5.1.0.cs
C:\Windows\System32\wbem\Framework\root\OpenHardwareMonitor\OpenHardwareMonitor_SN__Version_0.5.1.0.mof
Files [attributes?] modified:7
C:\Users\donny\AppData\Local\Microsoft\Windows\UsrClass.dat
C:\Users\donny\AppData\Local\Microsoft\Windows\UsrClass.dat.LOG1
C:\Users\donny\NTUSER.DAT
C:\Users\donny\ntuser.dat.LOG1
C:\Windows\System32\wbem\Repository\INDEX.BTR
C:\Windows\System32\wbem\Repository\MAPPING2.MAP
C:\Windows\System32\wbem\Repository\OBJECTS.DATA
Folders added:3
C:\Windows\System32\wbem\Framework
C:\Windows\System32\wbem\Framework\root
C:\Windows\System32\wbem\Framework\root\OpenHardwareMonitor
Don't think those files are directly from this app. They look more to me like they are from Windows Management Instrumentation which is Microsoft's web-based enterprise management system (thus the acronym wbem everywhere there).
Regarding your RegShotting, PortableApps installers don't make any changes to your local filesystem or registry apart from what other apps or Windows itself records about it (unless you are installing the app to the local filesystem, then of course you will get the app's folders and files as changes).
Taking a first shot before/after installation and a second shot before/after uninstallation will make no difference regarding the changes the app will make.
It is actually better to take the first shot after installing and the second shot before uninstalling, as this limits the possibility for stuff to end up in your log that is not important for portability.
It was the WBEM stuff that was the most interesting/different from what I've seen before.
And, I'm glad to hear that about the install/uninstall process.
Updated to 0.6.0 Dev Test 1. See release notes for details.
Updated to 0.8.0 Dev Test 1. See release notes for details.
So how does Open Hardware Monitor does relating a possible 'official' PortableApps version?
It's such a great and neat little app, and given the fact that it's OpenSource, it should already have it's PortableApps download page, or am I missing something?
Thank you.