How to Delete Undeleteable File

Many times when trying to remove an unwanted program, especially a piece of adware or spyware, you may run across a file that is undeletable by any normal method. When you try to remove it you'll receive the error message shown below telling you "access denied" and explaining the file may be in use. You may also receive one of the following messages.

Cannot delete file: Access is deniedThere has been a sharing violation.The source or destination file may be in use.The file is in use by another program or user.Make sure the disk is not full or write-protected and that the file is not currently in use.

So if the file is in use, how do you delete it?I'll show you several ways of removing these types of files and even some freeware programs that help you remove these pesky undeletable files.

Windows XP
In Windows XP, there are a couple ways to remove an undeleteable file, a manual way, and a couple automated ways using some freeware programs.

1. Click on Start, Search, All Files and Folders
2. Type the name of the undeletable file in the box shown
3. Make sure the Look In box shows the correct drive letter
4. Click Search and let the computer find the file
5. Once the file is located, right-click on it and choose properties, make a note of the file location. Usually this is something similar to

c:\windows\system32\undeleteablefilesname.exe

6. Close the search box
7. Click on Start, Run, and type CMD and Press Enter to open a Command Prompt window
8. Leave the Command Prompt window open, but proceed to close all other open programs
9. Click on Start, Run and type TASKMGR.EXE and press Enter to start Task Manager
10. Click on the Processes tab, click on the process named Explorer.exe and click on End Process.
11. Minimize Task Manager but leave it open
12. Go back to the Command Prompt window and change to the directory where the file is located. To do this, use the CD command. You can follow the example below.

Example: to change to the Windows\System32 directory you would enter the following command and Press Enter

cd \windows\system32

13. Now use the DEL command to delete the offending file. Type DEL where is the file you wish to delete. Example: del undeletable.exe
14. Use ALT-TAB to go back to Task Manager
15. In Task Manager, click File, New Task and enter EXPLORER.EXE to restart the Windows shell.
16. Close Task Manager

Listed below are the Programs to automatically delete a file that you may can use.

Remove on Reboot Shell Extension
This is a nice extension that loads into the right click menu. All you have to do is right-click on a file and choose "Remove on Next Reboot" and the file will be deleted the next time the computer restarts. Although it probably should only be used by more advanced computer users since it may be TOO easy to delete files using this program.

Pocket Killbox
A simple .exe file that you can use to delete undeleteable files, although the program will also delete temporary files, edit the HOSTS file, and more. A definite must have program when you are fighting an annoying spyware or adware program that won't remove.

Unlocker
Unlocker is another program that runs from the right click menu. Its simple and very effective. The website even has a side by side comparision of other programs that accomplish this task.
Using one of the three tools shown above, you should be able to remove those annoying undeleteable files once and for all.

Windows Update Problem?

Many users of Windows XP, Windows 2000 and Windows Server 2003 have had problems when trying to access the Windows Update site.
BTW, this error is not the only error message one might receive while trying to scan, download or install Hotfixes from the Windows Update site. Here is my current list of other Windows Update error codes and their respective solutions:

0x8007007E Error - Possible solutions
When you try to use Microsoft Internet Explorer to update Windows from the Microsoft Windows Update Web site you may receive the following error message:
Error 0x8007007e
To resolve this problem, follow these steps:

1. Click Start, click Run, type :
regsvr32 Inseng.dll

in the Open box, and then click OK. When you receive the RegSvr32 confirmation that the DllRegisterServer function succeeded, click OK.

2. Do the same with the following files:
regsvr32 Oleaut32.dll
regsvr32 Ole32.dll
regsvr32 Urlmon.dll
regsvr32 Mssip32.dll

3. Start Internet Explorer, and then update Windows from the Windows Update Web site (http://windowsupdate.microsoft.com).

If you still experience the problem, remove the Windows Update Setup Files folder.
1. To do so, locate the following folder:
2. Drive:\Windows Update Setup Files
3. Right-click the Windows Update Setup Files folder, click Delete, and then click Yes.
4. Install the latest version of Internet Explorer.

Windows Update Problems - Error 0x800A138F

Windows Update has encountered an error and cannot display the requested page.0x800A138F

The 0x800A138F error is actually a general error message, and many people get it when they visit Windows Update. But after the the MSBlast virus was unleashed a few months ago, Microsoft changed a few things at the main update website. This worm was expected to attack windowsupdate.com on the 16th of August 2003 by using a distributed denial of service attack (DDOS). To prevent this attack Microsoft made a few changes on the WU site. One of them was to use Akamai for additional bandwidth and this connectivity is exclusively using HTTPS (SSL) for the downloading of the update catalogue. It is since then that an escalation in the number of 0x800A138F error messages was reported.

As stated in the previous paragraph, the 0x800A138F error is in fact a general error message. To get a clearer picture of the real error message you'd need to go to the "Windows Update Log" and look for any "Errors". This gives a clearer indication as to the exact nature of the problem.

The windows update log is in the following places:
C:\Windows\Windows Update.log (XP/2003/Win98/Me)
or
C:\WINNT\Windows Update.log (Windows 2000)

Besides the changes in the WU site, many users of Windows 2000 reported similar problems in accessing the WU site. After installing to SP3, when trying to use Windows Update. Windows Update works fine scanning for updates, but when you choose to download and install them the page displays the 0x800A138F error message.

I've searched all over the Internet for solutions to these problems and came up with the following list of possible solutions. These solutions are not arranged by any specific order, although I do recommend trying each one from top to bottom till you reach the one that helped the most.

0x800A138F Error - Solution #1:
The number one reason for this error is related to your computer's date and/or time settings. If the date on your computer isn't correct, it may prevent you from connecting to secure sites. To fix the problem make sure your computer time and date are correct, and go to Windows Update and try again.
If you're on a network that has Active Directory configured you should try the following command:

w32tm /config /update /syncfromflags:DOMHIER

If will force your computer to update the time from the PDC Emulator in the domain.

Solution #2:
If that didn't work, the next solution might:
1. Delete c:\program files\windowsupdate
2. Delete the %systemroot%\system32\windowsupdate (this is a hidden directory)
3. Try windows update again.

Solution #3:
If the previous solutions didn't work for you, you might need to clear the problematic WU files from your computer. Some of these files are hidden files, please enable "Show Hidden Files and Folders" from your Folder options.

To delete Windows Update files:

1. Double click on My Computer, double click on C:\
2. Open the "WUTEMP" folder and delete the contents of the folder (If any files exist).
3. Double click the Program Files folder, then the 'Windows Update' folder. We will then need to delete all files & folders within this directory except the "V4" folder.
4. To do so, highlight the "V4" folder, then click Edit from the menu bar at top of the window and choose Invert Selection. If you cannot locate the "V4" folder, please skip this step, and then continue to delete the rest of the files by choosing Select All instead of Invert Selection.
5. Once all of the other files are highlighted, simply hit the Delete key on your keyboard to delete these files.
6. Next we need to delete all the files & folders within the V4 directory except the "iuhist.xml" file. To do so, perform the same steps as above by highlighting the "iuhist.xml" file, then clicking Edit from the menu bar at top of the window and choose Invert Selection.
7. Once these other files are highlighted, again hit the Delete key on your keyboard to delete the files.

Next delete all the contents of the WUTemp folder (if it exists, if not skip this step).

Next Unregister old control:

Go to Start > run
1.Type: regsvr32 /u C:\WINNT\System32\IUCTL.dll
2. You should get a unregistered successfully message.

Find your old site controls:
1. Go to Start > Search
2. Type "IUCTL.DLL" (Without Quotes)
3. Click on the Search button.
4. When the search result is displayed, delete delete any trace of the file IUCTL.DLL.
5. Next Search for the "IUEngine.dll" file.
6. Delete any trace of the file IUENGINE.DLL.
7. Reboot and try to access Windows Update again.

How To Launching remote desktop from the command line in Windows XP Pro

Remote desktop allows you to configure and connect to another computer running Windows XP Pro. Here's what you need to know about the remote desktop connection dialog box, including a few parameters you're most likely to encounter.

The Windows XP remote desktop connection dialog box provides you with everything that you need to configure and connect to another computer running Windows XP Pro. You can use the Save As button on the Connection Settings panel to save all your connection settings as an RDP file. Then, you can launch and connect to a remote computer simply by double-clicking the RDP file.

You can also script a remote desktop connection, as Windows XP's remote desktop connection has an executable file that can accept command line parameters and be run from a batch file. The remote desktop connection executable file is MSTSC.EXE, and the following are some of the most common parameters

• /v:--specifies the name of the computer to connect to.
• /f--starts the connection in a full screen.
• /w:<width>--specifies the width of the remote desktop screen.
• /h:<height>--specifies the height of the remote desktop screen.

For example, to remotely connect to a computer named Gampang in a 640 x 480 remote desktop screen, you would use the following command:

• mstsc /v: Gampang /w:640 /h:480

You can type this command line in the Run dialog box, as well as use it in a batch file.

Note: This tip applies only to Windows XP Professional.

10 hings you must know before you buy an 802.11n wireless device

If you've spent any time in your local tech shop, you are sure to have seen a rash of Pre-N and Draft-N wireless products. Before you get caught up in a rush of new product frenzy and plunk your money down, take a few minutes and look at exactly what you are buying.

1 - MIMO
One of the big advantages of 802.11n is MIMO. MIMO is short for Multiple Input / Multiple Output. MIMO breaks the data transmission down to multiple parts that are sent separately to the client, where they are reassembled. One of the requirements for this then is multiple antennas to send and receive the data. This system has the advantage of extending the range of wireless, along with increasing the capacity that can be carried by the signal. MIMO is implemented in almost all Draft N and Pre N specs. The use of MIMO in these devices has, for the most part, greatly extended the range of these devices. Unfortunately, there are still debates ongoing about the finalization of MIMO itself, as the 802.11n spec is not ratified yet.

2 - Standard not fully ratified
IEEE has not fully ratified the standards for 802.11n. This means that the technical details of 802.11n have not been decided upon. The original draft for 802.11n was voted on earlier this year and soundly rejected, receiving only 46 percent of the needed 75 percent of votes to be accepted. Draft 2.0 of the spec is scheduled be debated and approved in March of 2007. Items adhering to this spec can be labeled as Phase 1 Draft N. These items will be compatible with each other (unlike many current pre-n and draft n components). The final ratified standard will probably be ratified in early 2008. Of course, if no Draft 2.0 can be agreed upon in March 2007, this will push the schedule for all of this back.

3 - Equipment cannot guarantee N compatibility
As the final spec of 802.11n is not fully ratified, it is impossible to guarantee that any equipment sold as Pre-N or Draft-N will be compatible with the final spec. Many manufactures on banking on the assumption that compatibility can be achieved by firmware updates to their equipment. Currently the only vendor offering a full replacement warranty should there equipment not be compatible with the final spec is Asus. You can view information on their WL-500W router here, and you can view the details of their guarantee here.

4 - Huge speed increases over 802.11g
The final 802.11n will undoubtedly boast a great speed increase over 802.11g. This boost will almost assuredly make wireless faster than 100mb Ethernet. Currently most Pre-N and Draft-N equipment are already showing great speed increases. The speed they operate though varies based on manufacturer and equipment. The advertised speeds vary from 100mb to 200mb. If you truly need greater speed, be very careful in your shopping to make sure you are getting the fastest speed possible.

5 - Backward compatibility with previous wireless standards
While IEEE has announced that any final spec for 802.11n will include backward compatibility for 802.11b and 802.11g this specification is not finalized. With this being the case, there can be no guarantee of backward compatibility for current Pre-N and Draft-N gear. While most of the products currently on the market offer backward compatibility, how they implement it varies from vendor to vendor. Due to this, there can be (and have been reported) many instances where gear labeled as backward compatible, have not been fully backwardly compatible with equipment from other vendors.

6 - Draft-N and Pre-N gear may not be compatible with Draft-N and Pre-N gear from other vendors
Currently in the Draft 1.0 of the 802.11n spec, there is nothing to guarantee compatibility among equipment. If you choose to use Pre-N or Draft-N gear you will need to buy all of your equipment from a single vendor. While interoperability may be promised, there is no way to guarantee this. The Draft 2.0 spec of 802.11n will include interoperability standards for the release of Phase 1 Draft-N gear.

7 - Testing has shown MIMO systems not based on Draft-N standards can be significantly faster than systems based on Draft-N
Real world testing has shown that highest possible speeds using MIMO can be achieved by not sticking to the Draft-N specifications. What this means is that if you are truly searching for the fastest possible wireless connection, do not force your search to just N class products, but products that use MIMO.

8 - Draft-N gear is driven by marketing
It has been several years since any new development was made in consumer grade Wi-Fi. This has lead to a certain degree of stagnation within the market. The advent of Pre-N gear has given companies something to latch onto in an attempt to offer their customers something new. While there are undoubtedly benefits (in speed and range) to using this new gear, you are also putting yourself in line for potential problems. You really need to weigh your actual needs before jumping on the bandwagon of a "not ready for prime-time" technology.

9 - Potential to interfere with existing Wi-Fi
One of the issues with MIMO is that it uses a wide spectrum (40MHz) to send its data. Currently only three (1, 6, and 11) of the available channels in the current 2.4 GHz band are considered to be non-overlapping at this spectrum. However, under a powerful signal they can overlap. What this means to you is that if you have multiple wireless networks running, your Pre-N gear will need to be on one of these 3 channels, possibly necessitating a change in your current wireless networks. Also, you will want to plan for the overlap if possible, by moving your current networks to channels not sequential to 1, 6, and 11.

10 - Issues with media streaming devices
One issue that has been reported with Draft-N and Pre-N gear is that it appears it have some issues with various media streaming devices. This is an extremely perplexing issue, as of the goals of 802.11n was the ability to stream high definition media wirelessly. Whether this is due to issues in the Draft 1.0 specs, or if it's an issue with the current generation of media streaming devices remains to be seen, but at the moment a wired connection remains your best bet for streaming.

PHISHING EMAIL MESSAGE - Sample Picture!!!

How did my homepage get set to About:Blank?

The About:Blank homepage hijacker is a variation of a more advanced Cool Web Search hijacker. There are several variants of the About:Blank hijacker and all of them are difficult to remove manually. This hijacker is also referred to as the HomeOldSP hijacker because of the changes to the registry that can be seen using HijackThis such as

R1 - HKCU\Software\Microsoft\Internet Explorer\Main,HomeOldSP = about:blank

This is very similar in characteristics to the random dll hijacker also known as HomeSearch Hijacker that came out around the same time. The key to the hijack is a hidden dll file that is connected to a BHO (Browser Hijack Object). This hidden dll file shows up in the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\\AppInit_DLLs

Unfortunately removing this About:Blank hijacker can be difficult. Its a very persistent problem that can return quickly if it is not removed carefully.

Look for the Key named AppInit_DLLs, the value in this key is the hidden dll file that is causing your problems. Write down the name of this file and think of it as the hidden.dll file

Secondly, use the Windows Recovery Console in Windows XP to rename the file.

• Restart the computer in Recovery Console mode using the Windows XP or Windows 2000 CD or by the option show below
• Type cd \windows\system32 and press Enter
• Type the following line to remove the read-only characteristic, replacing hidden.dll with the name of the dll file found with RegLite
  

ATTRIB -R hidden.dll

• Rename the hidden.dll file by typing the following command (replacing the word hidden.dll with the actual filename)

RENAME hidden.dll badfile.dll

• Type Exit and press Enter to Reboot Windows