Windows Explorer has stopped working Error in Windows 7

                                                    Windows Explorer has stopped working Error in Windows 7

Problem:

The most annoying error messages in Windows Operating system are "Windows Explorer has stopped working" -  "Windows Installer has stopped working".

Operating system:

Windows vista,Windows 7

Suggested Solutions:

Method1:

    Go to the Start button.

    In the Search box, type "regedit" (without quotes) and press Enter.

    Browse the following registry key: "HKEY_LOCAL_MACHINE\SOFTWARE\ Microsoft\ SQMClient\Windows\DisabledSessions".

    On the right window pane, delete the subkey: "Machine Throttling".

    Reboot your computer.

Method 2:

In Administrator mode, At the command prompt, type "chkdsk /r /f" (without quotes) and press Enter. Restart the System.

Method 3:

 Incompatible Drivers installed while updating the Sound Card,Graphics Card, LAN Drivers etc. So Roll back the driver that you installed recently.It may also happen due to old drivers. Go the official download page for the respective hardware  to get the driver updated.

Method 4 :

    Press the key combination Windows logo key + R to open the Run dialog.

    Type gpedit.msc in the Run dialog and press Enter.

    In the Local Group Policy Editor navigate to

    Computer Configuration → Administrative Templates → System → Internet Communication Management → Internet Communication Settings.

    You would find a setting on the right hand side pane — Turn Off Windows Customer Experience Improvement program

    Double-click on this setting and choose Enabled and then click OK.

    Close the Local Group Policy Editor windows

Bootmgr is missing error in windows 7

Bootmgr is missing error in windows 7

Release

Windows 7

Problem

While booting in to windows 7 showing the error “bootmgr is missing. Press Ctrl+Alt+Del to restart”.

Solution

Method 1:

1.     Please insert the Windows 7 DVD media and restart the computer.

2.     Choose your language settings, and then click "Next" option.

3.     Select the option "Repair your computer".

4.     Select the operating system you want to repair, and then click "Next".

5.    On the System Recovery Options screen, select the option "Startup Repair". Startup Repair might prompt you to make choices as it tries to fix the problem, and if necessary, it might restart your computer as it makes repairs.

Method 2:

1.     Please insert the Windows 7 DVD media and restart the computer

2.     Select the option "Repair computer".

3.     Select "Cancel" to exit the repair wizard.

4.     Select "command prompt" option from the available options

5.     Type your "DVD-DRIVE LETTER" in command prompt, press ENTER.

6.     Let us assume windows 7 is installed in C drive, type "copy bootmgr c:\" without codes, press ENTER.

7.    Type "exit", press ENTER.

8.     Restart computer.

9.  Select "start windows normally".

Method 3:

1. Please insert the Windows 7 DVD media and restart the computer.

2. Choose your language settings, and then click "Next" option.

3. Select the option "Repair your computer".

4. Select the operating system you want to repair, and then click "Next".

5. In the System Recovery Options dialog box, select Command Prompt.

6. Type Bootrec /RebuildBcd , and then press ENTER.

7.Restart the computer

  

STOP 0X0000006B (Parameter1,Parameter2, Parameter3,Parameter4 ):PROCESS1_INITIALIZATIO_ FAILED ERROR

"PROCESS1_INITIALIZATION_FAILED” ERROR

Release

Windows 7 Professional (32B)

Problem:

While booting in Windows 7 the following error showing in blue screen.

STOP 0X0000006B (Parameter1, Parameter2, Parameter3, Parameter4):"PROCESS1_INITIALIZATION_FAILED-WINDOWS 7. This problem prevents the system from starting and all options in the boot menu, safe mode, VGA mode, etc. lead to the same BSOD.

Solution:

This issue occurs because the Bootcat.cache file is corrupted or because the size of the Bootcat.cache file is changed since the last successful start.

On computers running any of the Windows NT family (i.e. Windows NT 4.0, Windows 2000 and Windows Xp, Windows Server 2003), the BSOD is caused by a missing DLL file (usually NTDLL.DLL).
            To fix this, use Windows CD to boot to the recovery console .Then type

"dir ntdll.dll"

 The dir command allows you to see the available files in that  directory. The ntdll.dll file is a file created by Microsoft that has a description of "NT Layer DLL" and is the file that contains NT kernel functions. This file is located in the c:\windows\system32 or c:\winnt\system32 directory and can also be found in the c:\i386 directory.

            If it shows, the file may be corrupted. If you get a "file not found" message, then type

 "dir ntdll.dll/s"

The file may show up usually in c:\windows\system32\dllcache.If that's the case, then type

 "copy dllcache\ntdll.dll "

 and you will then get

"1 file(s) copied"

If the file is missing completely, then with the Windows CD in your CD drive, type

 "copy [d:]\i386\ntdll.dll " , where [d:] is the letter assigned to your CD drive

 Now, reboot the machine.

            On computers running any of the Windows Vista family (i.e. all editions of Windows Vista and Windows 7; all editions of Windows Server 2008). The BSOD is caused by a disposable file by the name of "bootcat.cache" located usually in "c:\windows\system32\codeintegrity" which has been corrupted.

If it is an intermittent problem, this can be solve by manually deleting bootcache.cat from C:\Windows\system32\CodeIntegrity

As per Microsoft, there is no hotfix available for this problem. They recommends to update Service Pack 1. We can use the following link to download the Service Pack.

Windows 7 Service Pack 1

http://windows.microsoft.com/installwindows7sp1 (http://windows.microsoft.com/installwindows7sp1)

Windows 2008 R2 Service Pack 1

http://go.microsoft.com/fwlink/?LinkID=199583

 If Windows is stuck in a repair and restart loop, insert Windows CD and select command prompt option. Then type,

“del c:\Windows\system32\CodeIntegrity\bootcat.cache”

Then reboot the pc.

Boot.ini tab is missing in MSCONFIG

Boot.ini tab is missing in MSCONFIG

Release

Windows XP SP2

Problem

When we start MSCONFIG.EXE the BOOT.INI tab which usually appears, may be missing

Solution

This problem may simply be a file permissions issue. To check this you can verify that by typing C:\Boot.ini in Start, Run dialog. If you get Access Denied or similar error, that explains the problem. Otherwise checkout the registry entries.

Open Regedit and locate the following path

    “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\MSConfig” .In the right-pane, delete the value named Boot.ini  (if found).Close Registry Editor and restart the windows explorer.try to open msconfig

Mapped Drive Connection to Network Share May Be Lost

Mapped Drive Connection to Network Share May Be Lost

Release

Windows 7,Windows 2008 server enterprise

Problem

 The mapped drive may be disconnected after a regular interval of inactivity, and Windows Explorer may display a red "X" on the icon of the mapped drive. However, if you try to access or browse the mapped drive, it reconnects quickly.

Solution

This behavior occurs because the systems can drop idle connections after a specified time-out period (by default, 15 minutes) to prevent wasting server resources on unused sessions. The connection can be re-established very quickly, if required.

Method1:

1.Open registry editor and locate the following path

  

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\parameters

 2. In the right pane, click the autodisconnect value, and then on the Edit menu, click Modify. If the autodisconnect value does not exist, follow these steps:

        On the Edit menu, point to New, and then click REG_DWORD.

        Type autodisconnect, and then press ENTER.

        On the Edit menu, click Modify.

         Click Hexadecimal.

   3. In the Value data box, type ffffffff, and then click OK. Close the registry editor and restart the PC

-----------------------------------------------------------------------------------------------------------------------

Error The current printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 or Windows 2000 kernel mode drivers

Error The current printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 or Windows 2000 kernel mode drivers

Release

Windows 2003 server SP2,Windows XP

Problem

When you install printer drivers , you may receive the following error message and cannot install printer.

“Unable to Install Printer. The printer driver is not compatible with a policy enabled on your computer that blocks Windows NT 4.0 drivers. If you want to use this driver, contact your system administrator about disabling this policy”

Solution

This behavior occurs because Windows does not support Kernel mode print drivers by default.

For windows XP

Open the group policy editor by typing gpedit.msc on RUN prompt and locate the path

Under Local Computer Policy, double-click Computer Configuration. Double-click Administrative Templates, and then double-click Printers.Right-click Disallow installation of printers using kernel mode drivers, and then click properties.On the Setting tab, click Disabled, and then click OK.

If you enable this the installation of kernel-mode printer drivers will be prevented.

For updating group policy use gpupadte /force command in command prompt

For windows 2003 server

Open the group policy editor by typing gpedit.msc on RUN prompt and locate the path

Under Local Computer Policy, double-click Computer Configuration. Double-click Administrative Templates, and then double-click Printers.Right-click Disallow installation of printers using kernel mode drivers.

or

Default Domain Controller Policy / Computer Configuration / Administrative Templates / Printers / Disallow installation of printers using kernel-mode drivers. And then click properties.On the Setting tab, click Disabled, and then click OK.

For updating group policy use gpupadte /force command in command prompt

Windows Cannot Set a Default Printer

Windows Cannot Set a Default Printer

Release

Windows 2000,Windows XP, Windows Vista, Windows 7

Problem

When we try to set a default printer, after changing the default printer in the printer’s control panel it reverts back to the previous default printer.

Solution

To fix this problem we need to change device value in registry.

    Open registry editor and locate the path

“HKEY_CURRENT_USER/ SOFTWARE/ MICROSOFT/ WINDOWS NT/ CURRENT VERSION/ WINDOWS”

  On the right pane Change entry for Device that has winspool,Ne00; delete whatever printer there is in the entry and just leave winspool,Ne00.Close the registry editor and restart the windows explorer.

****************