Some Notes on the Machines

Here is a simple procedure for CMD, it works as long as the queue location was not changed:

net stop spooler
del /F /Q %systemroot%\System32\spool\PRINTERS\*
net start spooler

On SBS 2011, you may see this repeated a lot in event logs:

Session "WBCommandletInBuiltTracing" failed to start with the following error: 0xC0000035

According to Microsoft, this can safely be ignored. However, many times these events will crop up so often as to eat up server performance.

To fix, open an administrative command prompt, CD a la:

cd C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN 

and run

PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures

If you see a message which says SPWriterServiceInstance would not start, and/or if the Sharepoint VSS Writer service is disabled, try this:

stsadm -o registerwsswriter

which should get the VSS writer set up and going, and then run the PSConfig above again.

References:

http://timaddamz.wordpress.com/2013/08/27/sbs-2011-session-wbcommandletinbuilttracing-failed-to-start-with-the-following-error-0xc0000035/

http://social.technet.microsoft.com/Forums/en-US/4092f3fa-7bf8-4194-bc78-9cfcdf6f058b/sharepoint-2010-vss-writer-service-disabled?forum=smallbusinessserver

http://social.technet.microsoft.com/Forums/en-US/94c5f178-f020-4d0f-ba7c-11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepoint-foundation-2010-updates?forum=smallbusinessserver

http://msmvps.com/blogs/bradley/archive/2011/06/30/remember-you-must-run-psconfig-after-sharepoint-sp1-is-installed.aspx

Here are the downloads for XP, 7, and 8.1:

http://msdn.microsoft.com/en-us/windows/hardware/hh852365

Remove old obsolete printer connections here:

HKEY_USERS\<the user's SID>\Printers\Connections

and here:

HKEY_USERS\<the user's SID>\Printers\Settings

and the problem goes away.

It may occur that this location:

%ProgramData%\Microsoft\Windows\WER\ReportQueue

(on most systems, thus:)

C:\ProgramData\Microsoft\Windows\WER\ReportQueue

starts to fill with gigs and gigs of queued reports for Windows Error Reporting. The folder’s contents can be deleted safely. If you want to turn W.E.R. off on a server:

1. Go to Administrative Tools, Server Manager.
2. Go to the Server Manager top level page, the very bottom, make sure you can see the whole Resources and Support section.
3. Click into Configure Windows Error Reporting and turn it altogether off.

For one user, this works:

1. WindowKey+R
2. shell:startup
3. Create your shortcut in the window which comes up.

For all users, place a shortcut in the following location:

C:\Users\All Users\Microsoft\Windows\Start Menu\Programs\Startup

This is one good fix to try when svchost.exe is occupying 100% of one CPU’s capability on XP or 2003.

net stop wuauserv
del /f /s /q %windir%\SoftwareDistribution\*.*
net start wuauserv
wuauclt.exe /detectnow

Another is here:

http://support.microsoft.com/kb/927891

If BITS and/or Windows Update aren’t working, try this:

http://support.microsoft.com/kb/949104

If this is missing, try here:

http://www.microsoft.com/en-us/download/confirmation.aspx?id=5555

Create a shortcut, in the taskbar and on the desktop if desired, to this:

%windir%\explorer.exe shell:::{2559a1f8-21d7-11d4-bdaf-00c04f60b9f0}

The resultant icon will bring up 8’s all-apps screen, which may be a sufficient replacement for the start button.