This situation can occur if BitWare for Windows is installed. The current versions of BitWare are 3.30 and 7.0, which are not fully compatible with the versions of Windows that are listed in the 'Applies to' section of this article. To check to see if BitWare is running, look for instances of Bwagent.exe or Bwprnmon.exe in Task Manager.
Spoolsv.exe has generated errors and will be closed by Windows. You will need to restart the program. An error log is being created. Printer operation cannot continue due to lack of resources.
RESOLUTION
WARNING : If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Use Registry Editor at your own risk.
Uninstalling the BitWare software is the best course of action, but is not available for all versions.
If uninstalling is not available, you can delete all registry entries and drivers that refer to BitWare manually:
1.Start Registry Editor (Regedt32.exe).
2.Locate references to BitWare in the following keys in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-2
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Monitors
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Print\Printers
3.On the Edit menu, click Delete for each BitWare subtree.
4.Quit Registry Editor.
5.Delete all BitWare drivers from the %SystemRoot%\System32\Spool\Drivers\W32x86 folder.
6.Restart Windows.
Showing posts with label Miceosoft Operating System Support. Show all posts
Showing posts with label Miceosoft Operating System Support. Show all posts
Windows Vista Boot Configuration Data
This post provide technical support for Windows Vista and later versions of Windows, boot options are stored in the Boot Configuration Data (BCD) store on BIOS-based and EFI-based computers.
BCD replaces the traditional Boot.ini text file in BIOS-based systems. Storing boot parameters in a text file, however simple, was considered to be too vulnerable to malicious attacks to justify its use. On EFI-based computers, where boot options are stored in NVRAM, you use the same BCD methods to edit boot options as you would use on a BIOS-based computer, instead of accessing NVRAM directly using Windows APIs or specialized tools.
BCD provides a common, firmware-independent boot option interface for all computers running Windows Vista. It is more secure than previous boot option storage configurations, because it permits secure lockdown of the BCD store and lets Administrators assign rights for managing boot options. BCD is available at run time and during all phases of setup. You can even call BCD during power state transitions and use it to define the boot process for resuming after hibernation.
You can manage BCD remotely and manage BCD when the system boots from media other than the media on which the BCD store resides. This feature is extremely important for debugging and troubleshooting, especially when a BCD store must be restored while running Startup Repair from a CD, from USB-based storage media, or even remotely.
Most importantly, BCD is easy to use. The BCD store, with its familiar object-and-element architecture, is easy to use. It uses GUIDs to precisely identify boot-related applications.
This new data format for BCD uses a new set of boot options. Most of the Windows boot options that were used in previous versions of Windows, such as /debug, /maxmem, and /pae, have been preserved; however, in some cases, the names of the options might have changed to better suite their function. For more information about these boot options, see BCD Boot Options Reference.
Related Search:
Microsoft Windows Vista Support
Install standard VGA compatible driver
How to use System Restore in Windows Vista
System Requirement for Windows Vista
BCD replaces the traditional Boot.ini text file in BIOS-based systems. Storing boot parameters in a text file, however simple, was considered to be too vulnerable to malicious attacks to justify its use. On EFI-based computers, where boot options are stored in NVRAM, you use the same BCD methods to edit boot options as you would use on a BIOS-based computer, instead of accessing NVRAM directly using Windows APIs or specialized tools.
BCD provides a common, firmware-independent boot option interface for all computers running Windows Vista. It is more secure than previous boot option storage configurations, because it permits secure lockdown of the BCD store and lets Administrators assign rights for managing boot options. BCD is available at run time and during all phases of setup. You can even call BCD during power state transitions and use it to define the boot process for resuming after hibernation.
You can manage BCD remotely and manage BCD when the system boots from media other than the media on which the BCD store resides. This feature is extremely important for debugging and troubleshooting, especially when a BCD store must be restored while running Startup Repair from a CD, from USB-based storage media, or even remotely.
Most importantly, BCD is easy to use. The BCD store, with its familiar object-and-element architecture, is easy to use. It uses GUIDs to precisely identify boot-related applications.
This new data format for BCD uses a new set of boot options. Most of the Windows boot options that were used in previous versions of Windows, such as /debug, /maxmem, and /pae, have been preserved; however, in some cases, the names of the options might have changed to better suite their function. For more information about these boot options, see BCD Boot Options Reference.
Related Search:
Microsoft Windows Vista Support
Install standard VGA compatible driver
How to use System Restore in Windows Vista
System Requirement for Windows Vista
Subscribe to:
Posts (Atom)