• Go to START – Run
• type “regedit”

Go to:

• HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\IEXPLORE.EXE\DefaultIcon

If your icon is missing the default icon properties will look like this:

1. C:\Program Files\Internet Explorer\iexplore.exe,-7.

What it should be is…

• C:\Program Files\Internet Explorer\iexplore.exe,-32528

Reboot. Your icon will now be back.

The computer I was looking at today wasn’t so lucky. It turned out that it was much harder to fix. How I fixed it was:

1. Hit “Windows key” + “R”. This will open the run window
2. Type “regedit”
3. Go to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
4. Right Click “Enum” and “change permissions”.
5. Make sure System has full control, everyone has read.
6. In my case this was already done. I went to the advanced section told it to replicate those permission to all sub-folders and files.
7. After doing so all my devices started showing up in device manager. Device manager was no long blank.

Hope this helps.

The reason why you get the “Incorrect MFC Dll version installed on the system,minimum requirement is MFC SP4 Dlls” message is there is some corrupt files that are part of Dell’s wireless system tray. It’s a pig on memory and you don’t really need it. I recommend that you just make sure that you use the built in Windows Wireless manager.

To get rid of the error you have to go into:

1. START – Control Panel – Administrative Tools – Services
2. Find “Dell Wireless WLAN tray Service”
3. Right click the service and select “STOP”.
4. Wait for the service to stop
5. Double click the service.
6. Make sure “STARTUP TYPE” is set to “Disabled”.
7. If there are any “Incorrect MFC Dll version installed on the system,minimum requirement is MFC SP4 Dlls” on the screen close them. It should not re-apear again if you followed the steps correctly.

To switch the machine over to the built in Windows Wireless Manager follow these few steps:

1. Click  “My Computer”
2. In the address  bar type “Desktop” and hit Enter
3. Find “My Network Places” right click it and select “Properties”
4. Fine the Wireless Network Connection icon. Right click it and select “Properties”.
5. Click on the second tab labled “Wireless Networks”.
6. Make sure that “Use Windows to configure my network settings” is checked off.
7. Noww you must click “Add” button to add your wireless network info. You will select the SSID network name and then you must enter your router’s wireless password.

I hate it when Manufacturer’s add their crappy bloatware to their machines!

I hope this helped you get rid of the  “Incorrect MFC Dll version installed on the system,minimum requirement is MFC SP4 Dlls” message!

1. Open up notepad from the start menu. In Windows Vista/Windows 7 you can easily find it by typing notepad in the search box.
2. Paste the info in the box into notepad and save it as “EXE-Fix.reg” on your desktop.
3. Double-Click the EXE-Fix.reg file. Your machine will ask if you want to import the registry info. Say yes.
4. It should say It was imported successfully and click “OK”.

Windows Registry Editor Version 5.00


[HKEY_CLASSES_ROOT\.exe]

@="exefile"

"Content Type"="application/x-msdownload"


[HKEY_CLASSES_ROOT\.exe\PersistentHandler]

@="{098f2470-bae0-11cd-b579-08002b30bfeb}"


[HKEY_CLASSES_ROOT\exefile]

@="Application"

"EditFlags"=hex:38,07,00,00

"TileInfo"="prop:FileDescription;Company;FileVersion"

"InfoTip"="prop:FileDescription;Company;FileVersion;Create;Size"


[HKEY_CLASSES_ROOT\exefile\DefaultIcon]

@="%1"


[HKEY_CLASSES_ROOT\exefile\shell]


[HKEY_CLASSES_ROOT\exefile\shell\open]

"EditFlags"=hex:00,00,00,00


[HKEY_CLASSES_ROOT\exefile\shell\open\command]

@="\"%1\" %*"


[HKEY_CLASSES_ROOT\exefile\shell\runas]


[HKEY_CLASSES_ROOT\exefile\shell\runas\command]

@="\"%1\" %*"


[HKEY_CLASSES_ROOT\exefile\shellex]


[HKEY_CLASSES_ROOT\exefile\shellex\DropHandler]

@="{86C86720-42A0-1069-A2E8-08002B30309D}"


[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers]


[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\PEAnalyser]

@="{09A63660-16F9-11d0-B1DF-004F56001CA7}"


[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\PifProps]

@="{86F19A00-42A0-1069-A2E9-08002B30309D}"


[HKEY_CLASSES_ROOT\exefile\shellex\PropertySheetHandlers\ShimLayer Property Page]

@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"


[HKEY_CLASSES_ROOT\regfile]

@="Registration Entries"

"EditFlags"=dword:00100000

"BrowserFlags"=dword:00000008


[HKEY_CLASSES_ROOT\regfile\DefaultIcon]

@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

00,5c,00,72,00,65,00,67,00,65,00,64,00,69,00,74,00,2e,00,65,00,78,00,65,00,\

2c,00,31,00,00,00


[HKEY_CLASSES_ROOT\regfile\shell]

@="open"


[HKEY_CLASSES_ROOT\regfile\shell\edit]


[HKEY_CLASSES_ROOT\regfile\shell\edit\command]

@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4e,00,4f,00,\

54,00,45,00,50,00,41,00,44,00,2e,00,45,00,58,00,45,00,20,00,25,00,31,00,00,\

00


[HKEY_CLASSES_ROOT\regfile\shell\open]

@="Mer&ge"


[HKEY_CLASSES_ROOT\regfile\shell\open\command]

@="regedit.exe \"%1\""


[HKEY_CLASSES_ROOT\regfile\shell\print]


[HKEY_CLASSES_ROOT\regfile\shell\print\command]

@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\

00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,4e,00,4f,00,\

54,00,45,00,50,00,41,00,44,00,2e,00,45,00,58,00,45,00,20,00,2f,00,70,00,20,\

00,25,00,31,00,00,00


[HKEY_CLASSES_ROOT\.lnk]

@="lnkfile"


[HKEY_CLASSES_ROOT\.lnk\ShellEx]


[HKEY_CLASSES_ROOT\.lnk\ShellEx\{000214EE-0000-0000-C000-000000000046}]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\.lnk\ShellEx\{000214F9-0000-0000-C000-000000000046}]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\.lnk\ShellEx\{00021500-0000-0000-C000-000000000046}]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\.lnk\ShellEx\{BB2E617C-0920-11d1-9A0B-00C04FC2D6C1}]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\.lnk\ShellNew]

"Command"="rundll32.exe appwiz.cpl,NewLinkHere %1"


[HKEY_CLASSES_ROOT\lnkfile]

@="Shortcut"

"EditFlags"=dword:00000001

"IsShortcut"=""

"NeverShowExt"=""


[HKEY_CLASSES_ROOT\lnkfile\CLSID]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\lnkfile\shellex]


[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers]


[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\Offline Files]

@="{750fdf0e-2a26-11d1-a3ea-080036587f03}"


[HKEY_CLASSES_ROOT\lnkfile\shellex\ContextMenuHandlers\{00021401-0000-0000-C000-000000000046}]


[HKEY_CLASSES_ROOT\lnkfile\shellex\DropHandler]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\lnkfile\shellex\IconHandler]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers]


[HKEY_CLASSES_ROOT\lnkfile\shellex\PropertySheetHandlers\ShimLayer Property Page]

@="{513D916F-2A8E-4F51-AEAB-0CBC76FB1AF8}"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}]

@="Shortcut"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\InProcServer32]

@="shell32.dll"

"ThreadingModel"="Apartment"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\PersistentAddinsRegistered]


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\PersistentAddinsRegistered\{89BCB740-6119-101A-BCB7-00DD010655AF}]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\PersistentHandler]

@="{00021401-0000-0000-C000-000000000046}"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\ProgID]

@="lnkfile"


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\shellex]


[HKEY_CLASSES_ROOT\CLSID\{00021401-0000-0000-C000-000000000046}\shellex\MayChangeDefaultMenu] 

Another example would be software coded in .NET. Most of the .NET coded software seems to be portable because it doesn’t require installation but since .NET Framework doesn’t come pre-installed in Windows XP, we can’t say that it’s portable. Perhaps when Windows Vista or 7 has totally replaced XP, then we can call software coded in .NET portable.

Last week I tried to run Remove Restriction Tool on one of a customer’s computer that has been infected by a computer virus but it gave an error. I couldn’t figure out what was wrong but I can only suspect that maybe one of the DLL files that was required to run RRT has corrupted but I didn’t know which one. Many years ago I had a tool that was able to check what DLL or OCX files is needed to run the executable file but I’ve lost it since I didn’t have a blog at that time to record it down. I searched around and found a similar tool called Dependency Walker.

Dependency Walker is a free utility that scans any 32-bit or 64-bit Windows module (exe, dll, ocx, sys, etc.) and builds a hierarchical tree diagram of all dependent modules. For each module found, it lists all the functions that are exported by that module, and which of those functions are actually being called by other modules. Another view displays the minimum set of required files, along with detailed information about each file including a full path to the file, base address, version numbers, machine type, debug information, and more.

All you need to do is run depends.exe and then load an executable (EXE) file that you want to check what file is required to run it. Within a few seconds Dependency Walker will show you the required files. As you can see on the image above, I loaded RRT.exe (Remove Restriction Tool) unto Dependency Walker and it shows me that KERNEL32.DLL and MSVBVM60.DLL is required. Every Windows has kernel32.dll file so we don’t need to worry on the availability of that file. As for msvbvm60.dll, I can place a working copy of that DLL file at the same folder as where the RRT.exe is and it will automatically load the DLL file if it can’t find one in system32 folder.

Depending on your background, you may find different sections of the newly published Microsoft Security Intelligence Report (SIR) to be of more interest.  In today’s post, we would like to highlight the section on infection rates based on the operating system (OS) version and the service pack level.  Microsoft has consistently observed that machines with newer OS and with more recent service packs are less likely to be infected by malware.  The graph below shows the number of computers having malware removed per 1,000 executions of the MSRT on that OS/SP during the second half of 2008 (2H08).

In the SIR, you will find the the following conclusions based on this data:

• The infection rate for Windows Vista is significantly lower than that of its predecessor, Windows XP, in all configurations.
• Comparing the latest service packs for each version, the infection rate of Windows Vista SP1 is 60.6 percent less than that of Windows XP SP3.
• Comparing the RTM versions of these operating systems, the infection rate of the RTM version of Windows Vista is 89.1 percent less than that of the RTM version of Windows XP.
• The infection rate of Windows Server 2008 RTM is 52.6 percent less than that of its predecessor, Windows Server 2003 SP2.
• The higher the service pack level, the lower the rate of infection. This trend can be observed consistently across client and server operating systems.

There are two reasons for this:

1. Service packs include all previously released security updates. They can also include additional security features, mitigations, or changes to default settings to protect users.
2. Users who install service packs generally maintain their computers better than users who do not install service packs and may also be more cautious in the way they browse the Internet, open attachments, and engage in other activities that can open computers to attack.

Server versions of Windows typically display a lower infection rate on average than client versions. Servers tend to have a lower effective attack surface than computers running client operating systems as they are more likely to be used under controlled conditions by trained administrators and to be protected by one or more layers of security. In particular, Windows Server 2003 its successors are hardened against attack in a number of ways, reflecting this difference in usage.

Continue http://blogs.technet.com/mmpc/archive/2009/04/21/malware-distribution-across-operating-systems.aspx

Preliminary tasks: Download the Windows 7 Beta and Burn It to a DVD

Assuming you’ve already downloaded a fresh copy of Windows 7, you’ll need to burn it to a DVD in order to do a fresh installation. To handle this task, grab a copy of my favorite CD and DVD burning tool called “ImgBurn”, burn the ISO to a DVD, and move right along to step 1.

Step 1: Partition Your Hard Drive

Before you go installing Windows 7, the first thing you need to do is create a new partition on your hard drive to hold the new installation of Windows. Partitioning your hard drive will vary depending on whether you’re running XP or Vista—namely because Vista has a partition tool baked in, XP does not.

Partition Your Hard Drive in XP

To partition your hard drive in Windows XP, you’ll need to download some sort of third-party partitioning software. I prefer to the GParted live CD, a free, open source boot CD that can handle all kinds of partitioning duties.

To use it, just download the GParted Live CD, burn it to a CD, then reboot your computer (booting from the disc). You’ll boot right into the partitioning tool.

1. Resize your current OS drive to free up enough space for a Windows 7 partition (the minimum system requirements ask for 16GB).

2. Create a new partition from the newly freed space.

3. Apply your changes.

Partition Your Hard Drive in Vista

The folks at Redmond were kind enough to include a disk partitioning tool in Vista if you know where to look. So go to:

Control Panel

• System and Maintainence (skip this one if you’re in Classic view)
• administrative Tools
• Computer Management.

Once you launch the Computer Management tool, click on Disk Management under the Storage heading in the sidebar. It’s partitioning time.

Step 2: Install Windows 7

Now that you’ve done all the heavy lifting, it’s time for the easy part: Installing Windows 7 on your new partition. So insert your Windows 7 disc and reboot your computer (you’ll need to have enabled booting from your DVD drive in your system BIOS, but most PCs will have this enabled by default).

Once the DVD boots up it’s a simple matter of following along with the fairly simple installation wizard. When you’re choosing installation type, be sure to select Custom (advanced) and choose the partition you set up above.

DISCLAIMER

Be careful here. Choosing the wrong partition could mean wiping your other Windows installation altogether, so make sure you pick the new partition you just created.

After you select the partition, go grab yourself a drink and let the installer do its work. Windows will run through some installation bits, restart a few times in the process. Eventually you’ll be prompted to set up your account, enter your license key, and set up Windows.

If you’ve ruled out the Windows Firewall (Make sure that Windows File Sharing has a checkbox in there for allowed), and everything else looks correct, but it still isn’t working, try the following:

As we need the NTRights program, and it doesn’t come with XP, download and install the administration tools from one of these locations.  Don’t worry about the name, the Kit works fine on XP also:

Windows Server 2003 Resource Kit Tools (Microsoft)
http://www.computersolutions.cn/blog/wp-content/uploads/2009/03/rktools.exe (Locally)

Once installed, please do the following:

• Click Start, Run (or Press Windows R)
• Type cmd and click OK
• In the DOS window (the black screen that just appeared), type the following:
  • net user guest /active:yes
  • ntrights +r SeNetworkLogonRight -u Guest
  • ntrights +r SeNetworkLogonRight -u Everyone
  • ntrights -r SeDenyNetworkLogonRight -u Guest
  • ntrights -r SeDenyNetworkLogonRight -u Everyone
• Reboot, and try again.  It should work.

There are two main things that you have to do to schedual Powershell scripts.

1. Allow Interactive Commands using set-executionpolicy command.
2. Put Powershell script in a ".ps1" file. You can use any text editor to make this.

The first thing you need to do is make sure that Powershell is set to execute Powershell scripts, instead of only allowing interactive commands to be run in the Powershell environment.

Type the following at the Powershell command prompt:

set-executionpolicy RemoteSigned

This will allow the system to run Powershell scripts that are created locally (Remote Powershell scripts that may be downloaded must be signed).

Once this is done, you can create your Powershell script using notepad. Just make sure you name the file with an extension of .ps1 . Now to run the script outside of its Powershell environment you type a command similar to the following:

powershell -command "& 'MyScript.ps1' "

Just put the above command into a .bat or .cmd file and schedule it like you would normally schedule a script to be run with Windows task scheduler.

I came accross this when working on a customers machine.

The first thing you will want to do is download the latest version of Dail-a-fix. Run the windows update and MSI fixer. Next you should open a command prompt by hitting: START – run – "cmd". In the command box window type:

regsvr32 wuaeng.dll

This will re-register this service.

EXTRA NOTE – An inplace repair install of XP will not correct this issue.