Monday, July 9, 2012

Computer stops responding when it is resumed from standby mode

Operating system
Windows Server 2003
When we resume the computer from standby mode, the computer may stop responding. Sometimes it may also see the "Applying Personal Settings" message box for up to an hour before the desktop appears.
Typically, when you resume a Windows Server 2003-based computer from standby, the computer is locked. Therefore, you must log on to the computer before you can access the desktop. However, when this problem occurs, the computer is not locked, and the Windows Server 2003 logon screen does not appear.
We found the following event messages may be logged in the application event log on the domain controller after restart the Windows Server 2003-based computer:
Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Access is denied. ). Group Policy processing aborted. For more information, see Help and Support Center at

Description: Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=domain,DC=com. The file must be present at the location <\\domain\sysvol\domain\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (The network path was not found. ).

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Description: Windows cannot query for the list of Group Policy objects. A message that describes the reason for this was previously logged by the policy engine. For more information, see Help and Support Center at
When we turn on user environment (Userenv) logging, domain Distributed File System (DFS) services may not work after the computer resumes from standby. Additionally, you may receive messages that resemble the following messages in the %SystemRoot%\Debug\UserMode\Userenv.log file.
According to Microsoft this problem may occur if the Winlogon process tries to process group policies before other components are running. However, there are several other scenarios that may cause this problem. Make sure that the following components are started and that they are configured correctly Netlogon and DFS services are started.
  • Domain controllers have the read and apply rights to the Domain Controllers Policy.
  • NTFS file system permissions and share permissions are set correctly on the Sysvol share.
  • DNS entries are correct for the domain controllers.
Method 1:
Microsoft released one Fix Microsoft Fix it 50615 for the above problem. The download link available from the below
Method 2:
Update latest Service Pack for the server operating system.
Method 3:
Open the registry editor and locate the below path
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Create the DWORD value If the WaitForNetwork, if the value is not exists. Set the value to 1.
Close the registry editor and restart the computer

Error message 0x80070057 when backup files in windows

Operating system
Windows 7
When we trying to backup files using the windows inbuilt backup utility called Windows Backup, the backup process fails and showing the below error
An internal error has occurred: The parameter is incorrect: (0x80070057).
Method 1:
Microsoft released the Fixit Microsoft Fix it 50719 for the above issue. The same will be available from the below link
Method 2:
Change the decimal symbol setting
This problem can occur if the decimal symbol is not set to '.' (dot). This is common in languages and locales other than English (United States), such as German (Germany).
To change the decimal symbol setting, follow these steps:
  1. Open Control Panel, click Clock, Language, and Region, and then click Region and Language.
  2. Click the Formats tab, and then click Additional settings.
  3. In the Decimal symbol field, type . (dot), and then click OK two times.
  4. Restart the computer.
Method 3:
Open the registry editor by typing the regedit.exe command and locate the below path.
Create a DWORD value CopyFileBufferedSynchronousIo and modify the value to 1.Close the registry editor and reboot the computer.

Less Disk Space issue in windows vista due to increase size in WINSXS folder

Operating system:

Windows Vista SP1&SP2


1.Check Pchealth folder exceeding its size.
2.Checked program files and users folders.
But in windows folder, there is a folder named  WINSXS showing couple of GB size.

SxS means Side-by-side technology and it is a solution integrated in recent Windows versions by Microsoft in a attempt to reduce DLL hell. The problem with this solution is that the system keeps all versions of installed components in order to be able to serve them to asking application. As a downside, you will notice that this folder grows up very quickly and this can quickly became a very serious issue for your computers

Common sizes for the WinSxS folder:

- Windows 2003 : WinSXS = 25 MB / 05 GB (total Windows)
- Windows 2008 : WinSXS = 05 GB / 10 GB (total Windows)

The only safe way to reduce the size of the WinSxS folder on the disk is to remove the packages that installed the original components. This can be achieved by uninstalling superseded versions of packages.

On Windows Vista, Service Pack 1 contains VSP1CLN.EXE. Running VSP1CLN.EXE will make the Service Pack package permanent and not removable.

The tool is automatically installed as part of the SP1 upgrade, and you can find it under %windir%\system32\vsp1cln.​exe.

On Windows Vista, after Windows SP2 you can use COMPCLN.EXE to clean up WinSxS folder. This tool is installed as part of the SP2 upgrade, and you’ll find it under \%windir%\system32\compcln.​exe.

As with vsp1cln.exe, executing compcln.exe will make SP2 not removable.

Other third part solutions to reduce WinSxS size are:




if your problem is with %windir%\winsxs\ManifestCache\ growing too much, you can refer to this procedure to remove the files under the %windir%\winsxs\ManifestCache\ and to release some disk space that the WinSXS folder is taking:

Net stop trustedinstaller
Takeown /f %windir%\winsxs\ManifestCache\​*
Icacls %windir%\winsxs\ManifestCache\​* /GRANT administrators:F
Del /q %windir%\winsxs\ManifestCache\​*

Server hanging at Applying Computer Settings stage of the logon process

Operating system

Windows server 2008,
Windows 7,
Windows Vista


When we start a computer it stops responding and appears to hang at the "Applying User Settings" or "Applying Computer Settings" stage of the logon process.


As per the Microsoft articles this issue typically occurs after install a server certificate and then configure Secure Sockets Layer (SSL) on the computer. For example, we install a SSL server certificate in Internet Information Services (IIS) 7.0 and then enable HTTPS on your website to use the certificate.

This issue occurs because of a deadlock in the Service Control Manager database. The Service Control Manager tries to start the HTTP.sys service and then puts a lock in place in the Service Control Manager database. Then, HTTP.sys makes a call that requires Cryptographic Services during startup. Then, a request is sent to start Cryptographic Services. However, a lock is already in place in the Service Control Manager database. Therefore, a deadlock occurs.


Microsoft released a Hot fix for this issue it is available from the below link

Method 2

To resolve this issue, create a DependOnService registry key to modify the behavior of HTTP.sys. This makes HTTP.sys depend on crytosvc service to be started first.

Open the registry editor by typing the command regedit.exe with administrative privilges.

Locate and then click the following registry subkey:


On the Edit menu, point to New, and then click Multi-string Value. Type DependOnService, and then press ENTER. Modify the value by typing the CRYPTSVC, and then click OK. Exit Registry Editor.

Restart the computer.

Method 3:

Microsoft Fixit team released the fix
Microsoft Fix it 50564 for solving this issue.

Procedure to clearing the ConfigMgr (SCCM) client local cache (CCM cache) -Resolving Disk space isssue

Essentially the client cache is a temporary download location for software, applications and software updates that are deployed to a clie...