KB ID 0000138
Event ID 7022
The McAfee Framework Service service hung on starting.
The Framework service starts before the network is up.
1. Start > run > Regedit {enter}.
2. Navigate to HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesMcAfeeFramework.
3. In the right hand window locate DependOnService > Double click it.
4. Add the following to the bottom of the list, “Netman” without the quotes.
NA
KB ID 0000176 Dtd 03/02/10
Event ID 1023
Source : .NET Runtime Description : .net Runtime version 2.0.50727.3603 – Fatal Execution Error (7a09795e) (80131506).
Symtoms:
1. As above. seen on .net version 2.0.50727.3603 Note: you version number may be different.
2. Backup Exec Server Service may be stuck / hung in the “starting” state.
3. .net 2 cannot be removed or service packed.
1. Download this, then apply the relevant 32 or 64 bit hot fix.
2. Reboot the affected machine.
NA
KB ID 0000401
I did a VMware VI3 to vSphere (4.1 U1) upgrade today. While bringing all the guest machines across, suddenly I could no longer browse the datastore, I only had one more guest to “Add to the inventory”, and all the mission critical machines were already migrated. I tried rebooting the virtual center, I tried restarting the ESXi host machines, still it sat saying “Searching Datastore……”.
1. I found the solution by accident. I was adding virtual machines to the new VSphere inventory, so I went in search of a method of doing it from the console, I was just about to:
Command to add a VMware guest to the inventory
[box]vmware-cmd -s register {full path to virtual machine}MACHINE_NAME.vmx[/box]
But, while looking in the folder with the guest files, I saw thousands of log files, I guess the VI client is struggling to parse them all, and display them. A quick internet search and I found out I can safely delete the log files.
2. Log into the ESX/ESXi servers console, for ESXi servers (version 4.0 and below) see here, for newer versions you can simply enable SSH access from Troubleshooting Mode Options > Enable Remote Tech support (SSH).
3. Log on as root and issue the following command to find the symlink path to your shared storage:
[box]ls -l /vmfs/volumes/[/box]
4. Now you know your symlink, you can change to the folder that contains the affected guest OS.
[box]cd /vmfs/volumes/{your symlink}/{your vm folder}[/box]
5. To get rid of all the log files, simply issue the following command.
[box]rm -f vmware-*.log[/box]
6. Now retry and you should see the folder contents when you “Browse Datastore”.
NA
KB ID 0000364
Saw this a while ago, and just thought it was a “One Off”. Then on a visit to a client yesterday I saw it on both machines I was working on.
This might scare you, but you need to kill the update, don’t panic at this stage SP3 is already on.
Update 05/04/11: Before continuing please read the feedback below. Ive never personally seen any adverse effects from doing this and I’ve rolled out a few thousand service packs.
1. Right click your task bar and select “Task Manager”.
2. On the applications tab > Select the Software Update Installation Wizard > Click End Task > Accept any warnings etc.
3. Reboot the PC > SP3 installation will recover and finish, ignore any errors or warnings just let it boot up and you will be at SP3, at this point finish the good work by going to windows update and getting all the post SP3 updates.
Feedback from Patrick Wright (05/04/11)
I am sending you a message concerning your advice on the Windows XP SP3 install “hanging” at “Performing Cleanup…”. The advice you give is to end the installation task at this point and reboot the computer.
The truth of the matter is that during the “Performing Cleanup…” step, there is indeed quite a bit of activity and updating going on. I’ve had this step take as long as 6 hours on slower machines on our network but it finishes successfully.
For testing purposes, I tried your solution on three training machines that were still running SP2 and ran into numerous issues after rebooting with getting several programs to install that require a minimum of SP3–Adobe Standard/Professional 10 is only one example and will refuse to install on all three of the test machines that I tried your suggested fix on. It appears that even though Windows shows in system properties to be upgraded to SP3, it is not completely finished if you stopped the install prematurely by ending that task.
I strongly advise to consider changing your solution to simply wait out the “Performing Cleanup…” task until it finishes. It can take a while. I’ve found one way to help the process along is to set the process for the updater to “high priority” in task manager. This resulted in drastically faster install times when the installer seemed to “hang” at that part of the install.
NA
KB ID 0000640
I installed a classroom full of PC’s today, after setting them all updating, and rebooting, I went to lunch, and came back to find them all displaying this,
Stage 3 of 3 Preparing to configure Windows. Don't turn off your computer.
I went and did another room, came back, and there was no change.
It turns out this is a known problem if you are installing KB2533552, to get round the problem simply press CTRL+ALT+DELETE, and you will be presented with the login page.
Microsoft recommend you install the above update separately.
Note: It will affect both Windows 7 and Server 2008 R2.
NA
KB ID 0000657
Saw this today on a Windows 2008 R2 Server, post reboot it just hung like this.
1. At first I thought this was the problem, but a CTRL+AL+DELETE didn’t work.
2. A Google search prompted me to connect to the ‘services’ from another server to see if the Windows Modules Installer Service was stuck stopping or starting, but that was OK as well.
3. It was the client’s Virtual Center server so I could afford to be a bit reckless (I could build them a new one and have it up and running, with no user downtime in about an hour). So I powered it off, rebooted and pressed F8, to see if it would boot into safe mode, then this happened.
Failure configuring Windows updates. Reverting changes. Do not turn off your computer.
It then rebooted, and hung at the original screen, I was pondering my next move, when the screen changed to the one above , and it rebooted again. I was concerned that now It was in a reboot loop.
4. After a few more reboots it changed to applying settings, then gave me the logon screen.
5. I then ran a manual Windows update, and it rebooted fine.
NA
KB ID 0000751
This is quite a common problem, in MOST cases the problem is caused by a print driver that Windows does not like.
But my printers are delivered via login script or group policy?
If that is the case then you need to exempt both your user and the computer from this method of printer deployment while you are troubleshooting.
1. As we cant be sure what printer/driver is causing the problem, we need to remove them ALL > Devices and Printers > Select each one in turn, and remove (Note: Keep one for the next step, but remember to delete that also when you have completed the next step).
2. Select your last printer > Print Server properties > Drivers > Remove them ALL.
3. Launch ‘appwiz.cpl’ and ensure there is no printing software installed, if there is uninstall it.
4. Launch ‘services.msc’ > Locate the Print Spooler service and ensure it is set to log on as ‘Local System’.
Note: As shown, from here you can manually start the service, but for now we will leave it as it is.
5. Open Windows Explorer and navigate to;
[box]
C:WindowsSystem32SpooldriversW32X86[/box]
Delete the contents of this folder.
6. If your machine is Windows x64 bit also navigate to;
[box]
C:WindowsSystem32Spooldriversx64[/box]
Delete the contents of this folder.
7. Navigate to;
[box]
C:WindowsSystem32SpoolPRINTERS[/box]
Delete the contents of this folder.
8. Start > In the search/run box type ‘regedit’ > navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Environment > Windows NT x86
[/box]
Here there should be two sub keys called Drivers and Print Processors, if there are any more delete them.
Warning: You might want to right click and ‘Export’ the keys in case anything explodes, you can simply double click the ‘exported’ file to merge it back in.
9. If your machine is running x64 bit Windows navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Environment > Windows x64
[/box]
How to Tell if Windows is 32 or 64 bit
Here there should be two sub keys called Drivers and Print Processors, if there are any more delete them.
Warning: You might want to right click and ‘Export’ the keys in case anything explodes, you can simply double click the ‘exported’ file to merge it back in.
10. Now navigate to;
[box]
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control > Print > Monitors
[/box]
Here delete ALL Keys Except,
AppleTalk Printing Devices (This may not be present)
BJ Language Monitor (This may not be present)
PJL Language Monitor (This may not be present)
Local Port
LPR Port (This may not be present)
Microsoft Document Imaging Writer Monitor (This may not be present)
Microsoft Shared Fax Monitor
Standard TCP/IP Port
USB Monitor
WSD Port
11. At this point, physically unplug all printers from the PC, (make sure no scripts or group policies are going to attempt to reinstall the printers). Then reboot the machine.
12. When the reboot is complete, make sure the Print Spooler service stays up without error.
13. Get the latest drivers for your printer(s) and reinstall them one by one, (I would say after each printer install, let the system run until you trust it, before installing the next printer).
If this problem only manifests itself when printing from IE, then go to Internet options > Advanced > Reset.
12. If that does not rectify the problem, make sure you are running the latest version of Adobe flash (or for troubleshooting remove the current version).
NA
