|
| Archive |
| May, 2010 (1) |
| April, 2010 (4) |
| March, 2010 (2) |
| February, 2010 (8) |
| January, 2010 (2) |
| December, 2009 (3) |
| November, 2009 (2) |
| October, 2009 (4) |
| September, 2009 (4) |
| August, 2009 (1) |
| July, 2009 (9) |
| June, 2009 (8) |
| May, 2009 (6) |
| February, 2009 (1) |
| January, 2009 (1) |
| December, 2008 (1) |
| November, 2008 (1) |
| October, 2008 (1) |
| August, 2008 (3) |
| July, 2008 (6) |
|
|
|
|
Thursday, July 17, 2008 |
|
|
Stop VirusRemover2008 Processes: VirusRemover2008.exe
Find and Delete these VirusRemover2008 Files:
%UserProfile%\Desktop\Viruses.bdt %UserProfile%\Desktop\VirusRemover2008.lnk c:\Program Files\VirusRemover2008 c:\Program Files\VirusRemover2008\Viruses.bdt c:\Program Files\VirusRemover2008\VRM2008.exe c:\Documents and Settings\All Users\Start Menu\Programs\VirusRemover2008 c:\Documents and Settings\All Users\Start Menu\Programs\VirusRemover2008\VirusRemover2008.lnk %UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch\VirusRemover2008.lnk %UserProfile%\Application Data\Mozilla\Firefox\Profiles\s1jqw0bz.default\cookies.sqlite
Remove VirusRemover2008 Registry Values:
5222008A-DD62-49c7-A735-7BD18ECC7350 HKEY_CURRENT_USER\Software\VirusRemover2008 |
|
|
|
|
|
Before trying to do the commands below, this infection adds a lot of policies (taskmanager disabled, registry editor disabled etc..) and also made some modifications in the startmenu. To fix this, download this zipfile to your desktop.
Unzip it. Then RIGHTCLICK the VArestorepolicies.inf and select to Install from the Context menu.
Then, log off or reboot to apply the changes.
Note: Above will set the display in the Startmenu to Windows default. This in case you have modified this previously and already "disabled" some StartMenu items there. It will also delete some policies which you *may have set yourself previously.
You might notice the words VIRUS ALERT! beside the System clock after being infected with one of the Zlob-Media Codec infections.

It's also displayed under the ProductID in your System Properties > General:

In the Registry, the following values are affected and replaced with VIRUS ALERT!
[HKEY_CURRENT_USER\Control Panel\International] "sTimeFormat"="h:mm: VIRUS ALERT!"
Which explains the VIRUS ALERT! words in the clock.
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "ProductId"="VIRUS ALERT!"
Which explains the VIRUS ALERT! in the System Properties.
In both cases, on every computer, above default values are different, because for the clock settings, it depends what the Regional Settings are. To restore the VIRUS ALERT! in the clock settings, Go to start > run and type: intl.cpl Hit enter This opens the Regional Settings properties. Under the tab Regional Options > standards and formats, from the dropdown list, re-select your region again.
 In my case it is set to English (United States), but in your case, it may be different ofcourse. By default the correct region should already be displayed there, but you have to re-select it, or select another Region first and then select your Region again > click apply and OK. This will reset the default data in the Registry for the sTimeFormat, so the VIRUS ALERT! should be gone. (in some cases, you need to log off in order to make the changes) (Extra note: In case you're having problems with above instructions, see the latest part of this post how to restore the policies first.)
For the ProductID - this is somewhat more advanced since every ProductID is different. You need to restore that value in the Registry again with your ProductID. The ProductID will be a 20 long string of numbers and is used when you call Microsoft for support. It may also affect Windows XP Validation, an error in System tray with "Unable to complete genuine Windows validation" and/or you *may receive the error: "0x80080201 Cannot detect product ID (PID)"
The ProductID that was modified here is under the: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "ProductId"="XXXX-XXX-XXXXXXX-XXXXX"
Note, this is not your Product Key used to install Windows!
To retrieve your Product ID and restore it for above key/value, you can find it under next value in the registry as well:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion] "ProductId"="XXXX-XXX-XXXXXXX-XXXXX"
If you're not familiar with the registry, I suggest you use the Microsoft Genuine Advantage Diagnostic (MGADIAG) tool instead to retrieve your Product ID.
Run MGADiag.exe, click Continue and you'll find your Product ID under the Windows Tab.

There you can find your Product ID. Now you have to restore that value in the registry again. To do this, go to start > run and type: regedit This will open your Registry Editor. (Extra note: In case you're having problems with above instructions, see the latest part of this post how to restore the policies first.)
Now browse to the following key by expanding the folders (keys) HKEY_LOCAL_MACHINE > SOFTWARE > Microsoft > Windows NT > CurrentVersion On the right, you should find: ProductId In your case, you'll see VIRUS ALERT! next to it. Doubleclick the value to open it and edit the string as you see in the screenshot below:

Where you see VIRUS ALERT! in the "edit string Window", delete the VIRUS ALERT! in there and replace it with your Product ID key you retrieved previously: XXXX-XXX-XXXXXXX-XXXXX The X stands for random numbers/letters Click the OK button after you edited the ProductID value in the Edit string Window to apply the changes.
Note2: Above instructions only remove the VIRUS ALERT! in the clock and System properties and the restrictive policies+registry modifications being set. This doesn't clean the infection itself if still present. As long as the infection is still present and active, it will replace above values (with VIRUS ALERT!)+policies again. |
|
|
|
|
Saturday, July 12, 2008 |
|
|
Check to see if update KB946983 is installed. There is a common issue with this patch that causes problems similar to what you are describing.
In Add/Remove programs, make sure the "show updates" box is ticked, and look for Security Update for Outlook 2007 (KB946983) (usually under Microsoft Office 2007. Remove it and try again.
| |
| |
I have noticed this patch causing a problem with new user profile setup. Remove the patch, setup the user and Outlook, then re-apply the patch and it should work fine from there. |
|
|
|
|
|
1) Go into the CMD prompt. 2) Then type cd \windows\inf and make sure we are in that directory. 3) Then type ren oem*.inf oem*.old, it will go back to the command prompt and may give an error (Do not worry about it) 4) Then type ren oem*.pnf oem*.old1, it will go back to the command prompt and may give an error (Do not worry about it) 5) Then goto start - run - type c:\windows\inf and you will see the files in the folder. 6) Then find the file by name INFCACHE.1 and take a backup of it to desktop (by copying it to desktop) and delete the INFCACHE.1 from c:\windows\inf. 7) Close all windows and reboot the computer to safe mode and start the installation of SP2 |
|
|
|
|
Wednesday, July 09, 2008 |
|
|
I recently had an encounter with Quickbooks PRO 2008 running on Windows Vista Service Pack 1. My laptop locked up with Quickbooks open and when I restarted, I could no longer access my company data file. When I opened Quickbooks, it acted like it was opening and then gave a Windows error message that "Quickbooks has stopped working" and gave me the option to send the report to Microsoft and options to either close or close and restart Quickbooks. I searched and searched for a solution to no avail. Intuit's site had one article that basically said "we know of this problem but have no solution." I cleared the last company file from the registry and was able to open Quickbooks and create a new file without problem which isolated the problem to the company data file. After searching all over for a solution I remembered I had a dual-boot of XP on my laptop with Quickbooks 2008 installed. I booted to XP, opened Quickbooks and the company file opened without error. I closed the file and then booted back to Vista, opened Quickbooks, and the file opened fine! It appears that when the company file was not properly closed, it caused an un-resolved problem with Quickbooks on Vista; once I opened the file on another instance of Quickbooks and closed it properly, the problem in Vista went away. | |
| |
In my opinion, just another example of the flakiness of the Vista operating system and the lack of industry support to resolve the issues. |
|
|
|
|
|
|