If Adobe Pro X won’t load, if it is installed as part of CS6, there is a good procedure to get it unstuck:
Category: Application Issues
If Adobe Pro X won't load
article #665, updated 4082 days ago

Which ports are used by LogMeIn?
article #171, updated 4173 days ago
See here:
http://notes.ponderworthy.com/logmein-settings-for-routers-firewalls

Silently Uninstalling Symantec Antivirus 11 and 12
article #451, updated 4656 days ago
For Symantec, rolling one’s own seems usual. I have been doing it using psexec and LabTech command prompt, running the msiexec lines below remotely. One has to get the long code first via regedit. Examples are below under major subversions. But before you do that, make sure there’s no password protection on the client. There are two locations.
First in here:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\SMC
and make sure SmcGuiHasPassword is 0.
Second, in here:
HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\Symantec Endpoint Protection\AV\AdministratorOnly\Security
make sure UseVPUninstallPassword is 0.
And now for some example msiexec lines. The /q is apparently needed just as the /qn, and the last two (very sparsely documented) items appear helpful as well. The GUID (the long code) is the tough part. It comes from:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
searching for “Symantec Endpoint Protection”, and it is possible to have more than one sub-subversion — and therefore more than one GUID — needed within a given LAN, mostly depending on update status.
for 12.1:
MsiExec.exe /X {EFCC6FA1-8F3F-46E6-B7BF-8336CCD3DA67} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL MsiExec.exe /X {BCE5F3B0-8407-42DB-8073-1812F7D2D1E6} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL
for 12.0:
MsiExec.exe /X {895665D9-6614-4930-9D39-3567283DD424} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL MsiExec.exe /X {D350A6A1-044F-4E19-8267-F1C44775CFC2} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL MsiExec.exe /X {A3AEEA68-AC93-4F6F-8D2D-78BBF7E422B8} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL MsiExec.exe /X {84B70C16-7032-41EE-965C-3C8D9D566CBB} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL
for 11.0:
MsiExec.exe /X {26624215-248C-4F88-A415-35301812FB75} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL MsiExec.exe /X {AAE221D5-C3DD-4FE2-A063-C1368FE730A5} /q /qn /norestart REBOOT=ReallySuppress REMOVE=ALL msiexec.exe /X {84B70C16-7032-41EE-965C-3C8D9D566CBB} /q /qn /norestart /REBOOT=ReallySuppress REMOVE=ALL
It can take a while — but it happens very silently.

Excel 2007 and 2010 reports files locked for editing by self
article #436, updated 4727 days ago
If you see this happen, try turning off the Explorer preview pane!

Outlook 2007 [possibly other versions] in Windows 7 not connecting to Exchange
article #432, updated 4742 days ago
If you see this, find OUTLOOK.EXE, go to Properties, and check the Compatibility tab. It may be set to XP SP2 compatibility. Uncheck Compatibility mode if it’s set.
No clues yet as to what is causing this, but I’ve seen it as the only solution needed once, and I have multiple reports similarly.

How to remove security-enhanced mode from Access MDB
article #411, updated 4799 days ago
The below explicitly refers to Access 2000, but at least in theory, it should work for any ADODB type database, which was standard from 2000 through 2003:

Word documents "Save As" with %20 instead of spaces
article #379, updated 4874 days ago
Often Windows Updates will do it. However, sometimes one has to run ‘webfldrs.msi’ and uncheck the last four options:

Recover Office and Windows Keys
article #253, updated 5211 days ago
This tool does very well:

File Signatures
article #248, updated 5226 days ago
Here is an excellent reference of “file signatures”, data bytes at the beginning of files to use for identification. Under Unix these are called “magic numbers”.
http://www.garykessler.net/library/file_sigs.html
Some firewall on-the-fly antivirus systems can use these to decide which files to scan.

StorageCraft ImageManager does not find any backup images
article #239, updated 5237 days ago
If you run into this, stop the ImageManager service, and delete the file “ImageManager.mdb” from the ImageManager program’s folder. (Don’t touch ImageManager.clean.mdb!) Then restart the service. ImageManager.mdb will be rebuilt, and all will be well.