Symptom:

You recently install a Windows Server 2008 R2 and patched SP1. The server (typically HP server) has multiple Intel CPUs, e.g. two Intel (R) Xeon(R) CPU 5160 3.00GHz.

You then enable the Hyper-V role, it required a reboot. But after reboot, the system didn't boot up, it just stayed in black screen.

Root cause:

Although the CPUs are identical, the revision or stepping are different. If one is revision 'CD' (stepping is 6) and the other is revision 'B9' (stepping is B), the system is not booting up with Hyper-V enabled.

Resolution:

Replace the CPU and make sure all CPU are identical with same revision and stepping.

More information:

To check CPU information, run WBEMTEST and enter the query "Select * from Win32_Processor" (without the quotes) and click on the Apply button.

Reference:

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/b5e5e655-1828-4e92-872f-136e4b479de5

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/2c51bdd7-d0a9-42d6-ac5f-d0a3be1318b2

http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/a8fdebf4-a41a-424d-8aa9-43b387d334ec/

Recently some customers reported an compatiblity issue between IE9 and Forefront TMG2010.

After install IE9, Microsoft Forefront Thread Management Gateway management tools cannot work anymore, it gives error message like “member not found”, “refresh failed”.

And going back to IE8 the problem was resolved. This seems localized IE9 is installed. Gernam and Russian language were reported being affected.

We are investigating this issue, the current workaround is:

Recently we have some cases that the customers reported the rendering issues with Facebook after upgrading to IE9 RTM.

In every case Facebook had been added to the Compatibility View list due to issues during the Beta or RC or IE8. Facebook does not want to be on the CV list, and we don’t want them on the CV list.

To get back to a great rendering experience, please do the following:

ALT + Tools :: Compatibility View Settings
Remove Facebook.com from the list
OK

That should put Facebook back in IE9 mode.

I would like to share some tips on searching with IE9.

1) Pressing Ctrl+E moved the caret to the address bar following a “? “.  Entering a search term and pressing Enter passed the search criteria to the search provider you specified (the default is Bing of course).

You have to make sure the following option is enabled:

Internet Options | General | Search, checking “Search in the address bar”

You can manage the search provider by going to:

Internet Options | General | Search, clicking "Find more search providers..." to add more.

2) Sometimes System administrators may have legitimate reasons to block search in the address bar. In this case, you can still get it through the custom SearchURL feature (which requires that you manually modify your registry).  For example, if you set
[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchUrl\b]
@="http://www.bing.com/search?q=%s"
then you can query Bing by typing “b <query>” into the address bar.  This still works with “Search in the address bar” disabled.

And you can also search in the explorer address bar:

And in the taskbar:

More information:

You can also set more SearchURL, for example:

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchUrl\MSKB]
@="http://support.microsoft.com/?kbid=%s"

[HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\SearchUrl\MSN]
@="http://search.msn.com/results.asp?q=%s"

New Update: Hotfix was just released to resolve this issue. http://support.microsoft.com/kb/2530309

Symptom:

Some customers reported GPP is not applying IE9, prior to Upgrading the browser to IE9.0 it was working OK with IE 8.0.

Enabled Logging for Group Policy Preferences and found the below:
--------------------------------------------------------------------------------------
Non-Working Scenario :
------------------------------------------------------------------------------------------------------------------------------
2011-03-29 09:56:37.131 [pid=0x3a0,tid=0xb18] {683F7AD7-E782-4232-8A6D-F22431F12DB5}
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Starting class <IE8> - Internet Explorer 8.
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Starting filter [AND FilterFile].
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Adding child elements to RSOP.
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Set user security context.
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] C:\Program Files\Internet Explorer\iexplore.exe
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] apmGetFileVersionEx
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] apmCompareVersionTokens [SUCCEEDED(S_FALSE)]
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Set system security context.
2011-03-29 09:56:37.147 [pid=0x3a0,tid=0xb18] Failed hidden filter [FilterFile].
2011-03-29 09:56:37.163 [pid=0x3a0,tid=0xb18] Filters not passed.
2011-03-29 09:56:37.163 [pid=0x3a0,tid=0xb18] Completed class <IE8> - Internet Explorer 8.
2011-03-29 09:56:37.163 [pid=0x3a0,tid=0xb18] Completed class <InternetSettings>.
------------------------------------------------------------------------------------------------------------------------------

When you try to edit a GPP Policy on the Domain Controller you only see an option for IE 5 / 6 / 7 and 8. 

Cause:

Windows Server 2008 R2 GPP Internet Explorer preference items does not support IE 9.  The problem is clear in the debug log as the filter did not pass.  The problem is viewable from the XML file

The released version of Internet Explorer 9 is not 9.0.0.0.

The trick is editing the xml and set "max Version=9.1.0.0", anyway, it is not supported.

More information:

http://technet.microsoft.com/en-au/library/gg699429.aspx

Reference:

http://social.technet.microsoft.com/Forums/pl-PL/winserverGP/thread/2b07b081-554e-4848-b533-0632d19e1a7a

http://social.technet.microsoft.com/Forums/en/winserverGP/thread/361b3bc2-251d-4d45-adad-2ec75996646c

http://social.technet.microsoft.com/Forums/de/gruppenrichtliniende/thread/83237a92-68a4-4bb7-9e79-0112ef6e0a6f

You might encounter an issue during the installation of SP1 for Win7/R2 where the installer exits with: 0x800f0a12. Usually it means the installer can’t access the system partition of your computer’s hard disk to update files.

This is due to the automount policy for your machine being set to disable. To resolve this, use the following steps:

1. Run DISKPART

2. automount enable

3. Restart

4. Install SP1

If the system partition isn't being mounted during startup, you can use "mountvol /E" in Command Prompt (Need administrator priviledge) to re-enable automatic mounting of all volumes.

And ensure that the System Reserved partition is marked active (you can do this in Disk Management or DISKPART).

Also you can try:

1. Turn off your computer and physically disconnect any external disks or drives that aren’t required for starting Windows.

2. Turn on your computer, and then try installing SP1 again.

Reference:

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/f955a5ff-3838-4e02-9d44-e698e1ae0346/

http://social.technet.microsoft.com/Forums/en-US/w7itproSP/thread/965ec430-bddf-4a0d-9cfe-a80500fb6fcf/

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/69ddc500-84e5-4b57-baa3-d51c5249f840/

http://ctp.social.technet.microsoft.com/Forums/kk-KZ/w7itproSP/thread/d7e1de83-2285-4a29-abcf-a4fcf5f471d4

http://ctp.social.technet.microsoft.com/Forums/kk-KZ/w7itproSP/thread/3a82e162-a5de-4702-a632-11305603b223

http://int.social.technet.microsoft.com/Forums/en/w7itproSP/thread/9083e953-f06c-4041-8977-115235359e23

http://windows.microsoft.com/en-US/windows7/windows-7-windows-server-2008-r2-service-pack-1-sp1-installation-error-0x800F0A12

http://blogs.technet.com/b/joscon/archive/2011/02/17/windows-7-2008-r2-service-pack-1-fails-with-0x800f0a12.aspx

Often 0x7F or 0x1000007F stop codes trap code 8 are due to overflowing a fixed size kernel stack space resource.

We have heard numerous reports of systems experiencing a BSOD after applying this update, and we have been able to confirm this issue results from kernel stack exhaustion. KB 2393802 leaves less stack space available in the Windows kernel for other kernel modules to use.

The majority of affected systems are running Windows XP SP3 (Windows XP leaves approximately 12,000 bytes of shared stack space for kernel modules to share.), but there is a potential for this issue to occur on all platforms.

Resolution:

Obtain updated drivers to resolve this issue:

Intel http://wer.microsoft.com/responses/resredir.aspx?sid=3320
AMD http://wer.microsoft.com/responses/resredir.aspx?sid=3319

We also have seen some similar cases that were not related to the specific video drivers; however the basic problem is the same.

For example, the filter driver pgpwded.sys from Symantec: http://www.symantec.com/connect/forums/pgp-wde-blue-screen-after-kb2393802

Reference:

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/5f27ee0e-d6bf-4dfa-afa0-49cec67b2ec7

Symptom:

Some people reported got an error message when he using his computer: Display driver stopped responding and has recovered.

Sometimes, when this error message comes out, the computer will get hang for some minutes and then BSOD or reboots.


Resolution:

It appears to be a graphic card driver issue, anyway.
Vista and Win7 use a feature called TDR. TDR baically gives the GPU 2 seconds to process what it is doing and display it on your monitor. If it fails to do so in 2 seconds you get the cool flash on the screen and the dreaded error message. In some cases, the situation get relief by giving TDR more time by setting registry value
1. Open REGEDIT
2. Using Windows 7, go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\GraphicsDrivers
3. Once there you will most likely have to create a new DWORD (32bit users) or QWORD (64bit users). Name it TdrDelay.
4. Once created, change the value to 8. This will allow the GPU 8 seconds to respond instead of 2 seconds.
More registry key explanations are here:
http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

Some customers fix the issue through they own ways, Below are the ways they use:
1. Go to BIOS and set the CPU from 200hz to 180hz.
2. Upgrade nforce motherboard driver.
3. Upgrade NVIDIA driver to latest beta build.
4. Change graphics card and maybe power supply.

Reference:

http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/0cd5ec8b-df03-4560-952b-8c7d10e67241

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/96c0c0f2-9772-424e-9632-fc7315905eb5

http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/display-driver-stopped-responding-and-has/4e8ed22d-fe52-4321-b83c-3ecd6650f91d

A lot of customers complained the following:
When they open up the Task Scheduler, they get a message that says:
The selected task "{0}" no longer exists. To see the current tasks, click Refresh.

 The mechamism task scheduler uses: it has a copy of tasks in registry and a copy of them in task files on disk. If somehow the tasked stored in registry and on disk are not in sync, users will encounter such issues as reported.

Tasks are stored in C:\Windows\System32\Tasks

In Registry, related branches are located in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks

Tasks tree is stored in:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree\Microsoft

So the general troubleshooting steps are starting from checking these locations to see if anything is broken or inconsistent.

Reference:

 http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/69afe198-3f97-406a-8d91-6a17504fb5b5

http://social.technet.microsoft.com/Forums/en-IE/w7itproinstall/thread/273368d4-ed12-4107-9d52-34759f2b53aa

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/1f677dd3-bdb7-4650-9164-d8e2c66b7708

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/d584f7e4-4e4c-45e8-8bce-39414914d674

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/a9e485d3-06ba-4038-a9b8-1b58e73ea4dd

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/360fde7c-ec4e-41f2-ae74-8949218e7a06

http://social.technet.microsoft.com/Forums/en/w7itprosecurity/thread/8e779ed1-7200-482e-a3a4-1e0ba8bf17cc

http://social.technet.microsoft.com/Forums/en/w7itproperf/thread/94bb210a-b291-41ad-a745-d4a9d8cc77dc

http://social.technet.microsoft.com/Forums/en/w7itprogeneral/thread/344f6815-0878-43ab-8997-33790b889541

http://social.technet.microsoft.com/Forums/pl-PL/w7itproperf/thread/43712af2-5731-4177-9d45-31d9b5b3240d

Symptom:

When you are installing Windows 7 or Windows Server 2008 R2 SP1, you may encounter the installatin failure with error 0x80004005 (E-FAIL).

And you can find the errors in the CBS.log, like below:

Failed. Attempted to uninstall a version of a non-driver component that is not installed, version: 0X600011db04001, component: x86_microsoft-windows-a..tigations.resources_31bf3856ad364e35_6.1.7600.16385_en-us_1992d6abf12a4412, owner: Microsoft-Windows-WindowsFoundation-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385.Windows Foundation Language Pack [HRESULT = 0x80004005 - E_FAIL]

Or

2011-02-21 18:56:58, Error CSI 000006e1 (F) Done with generic command 60 (0x0000003c); CreateProcess returned 0, CPAW returned S_OK
Process exit code 41001 (0x0000a029) resulted in success? FALSE
Process output: [l:73 [73]"Trying to install vpcnfltr .....failed. Error code: 0x8004a029. [gle=0x80004005]

Error code: 0x8004a029 is NETCFG_E_MAX_FILTER_LIMIT

Resolution:

Generally, the error is because of system corruptions.

Please follow the below steps to resolve it:

1. Run CheckSUR(KB947821).

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

2. Run sfc/scannow to fix the possible errors.

3. If you find 0x8004a029 in the CBS.log, it is because you have more than 13 filter drivers installed.

Option 1
Windows 7 is hard coded to allow 14 filter drivers, but the following registry sets the limit to 8 by default. You can adjust the amount up to 14 or delete this key and it will be set to max of 14.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters

Option 2
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\

Delete Something that you don't need (Export First) - You can delete for example Virtual WiFi Filter Driver

4. If you encounter this error on a MacBook, probably it is an known issue (http://discussions.info.apple.com/thread.jspa?threadID=2762246&start=0&tstart=0).

Just uninstalled the HFS+ driver, then SP1 ran from Windows Update and it installed fine.

5. The last option is to Perform an inplace upgrade of Windows

Reference:

=========

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/2b4a26e0-ee31-4bfa-a8bc-82b0af24af1d

http://social.technet.microsoft.com/Forums/el-GR/w7itproinstall/thread/3cd82850-717d-45af-bd67-54823a9b5846

http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/2538adfa-0872-4400-8a20-12abdde248df

http://social.technet.microsoft.com/Forums/en-MY/w7itproSP/thread/b3efd2f5-3b00-41c1-89ce-f48618e29e4c

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/3a2e8c69-ec05-43d9-9ae4-836630b55f82

http://answers.microsoft.com/en-us/windows/forum/windows_other-windows_update/sp1-wont-install-error-code-80004005/3c78e4fc-68ce-467d-851e-8f30f0e93bfd

http://social.technet.microsoft.com/Forums/en-US/w7itproSP/thread/971838ad-39c0-4e16-9ea2-1dcb8a885ca1

Edit: KB2530477 was published, you can reference it for more details.

Symptom:

When installing Windows 7 Service Pack 1 (SP1), you could possibly encounter errors 0x800f0a13, 0x80070003 or 0x800f0826.

The CBS logs is like below:

2011-02-23 08:32:18, Info CBS SPI: System falls between the SRCleanMin and SRPreserveMin bounds. All VSS snapshots will be deleted
2011-02-23 08:32:18, Error CBS SPI: (PerformSPInstallation:709)Failed SPC Lite UI hr=0x800f0a13
2011-02-23 08:32:18, Error CBS SPI: (wmain:1105)Failed to perform SP installation hr=0x800f0a13

Or

2010-11-07 13:09:52, Info CBS DriverUpdateUninstallUpdates failed [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2010-11-07 13:09:52, Error CBS Doqe: Failed uninstalling driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2010-11-07 13:09:52, Info CBS Perf: Doqe: Uninstall ended.
2010-11-07 13:09:52, Info CBS Failed uninstalling driver updates [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2010-11-07 13:09:52, Error CBS Shtd: Failed while processing non-critical driver operations queue. [HRESULT = 0x80070003 - ERROR_PATH_NOT_FOUND]
2010-11-07 13:09:52, Info CBS Shtd: Rolling back KTM, because drivers failed.

This is similar to the issue that we posted 4 monthes ago:

http://blogs.technet.com/b/asiasupp/archive/2010/11/23/win7-sp1-rc-install-failed-error-path-not-found-if-missing-certain-built-in-rtm-driver.aspx

Solution:

In most of cases, this issue is because the 3rd party driver clean software ( like DriverCleanerDotNet or Driver Sweeper utility from Phyxion ) was installed, and it made some changes to the system image.

Please follow the below steps to resolve it:

1. Run CheckSUR(KB947821).

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

2. Follow the steps from Phyxion on properly restoring the drivers: http://forum.phyxion.net/viewtopic.php?id=17

3.   Mount your Windows installation media to a folder

Extract and replace the %SystemRoot%\System32\DriverStore\FileRepository with the following folders:
atiilhag.inf_amd64_*
atiriol6.inf_amd64_*
nv_lh.inf_amd64_*

Extract and replace the %SystemRoot%\winsxs with the following folders (x64):
amd64_atiilhag.inf.resources_*
amd64_atiilhag.inf_*
amd64_atiriol6.inf_*
amd64_nv_lh.inf.resources_*
amd64_nv_lh.inf_*

Extract and replace %SystemRoot%\winsxs\Manifests with the following files:
amd64_atiilhag.inf-languagepack_*.manifest
amd64_atiilhag.inf.resources_*.manifest
amd64_atiilhag.inf_*.manifest
amd64_atiriol6.inf_*.manifest
amd64_nv_lh.inf-languagepack_*.manifest
amd64_nv_lh.inf.resources_*.manifest
amd64_nv_lh.inf_*.manifest

Note: these are the 64-bit version of the files. For the 32-bit version look for the x86 files. You also need to replace the permisions on above mentioned files and folders to be able to replace them.

4. Perform an inplace upgrade of Windows

Some customers reported the issues of power management.

Symptom:

Prior to the SP1 installation the system properly went into sleep mode and properly woke up. But, after installing Windows 7 SP1 you may be not able to properly put the system into sleep mode.

You have to press the power button to force the system restart, and it will show an error that the machine was not shut down properly.

Resolution:

Please try the following methods:

1. Install the following hotfix:

A crash memory dump file is not created, or hibernation does not work, when you use a SCSIport miniport driver as the startup device driver in Windows 7 or in Windows Server 2008 R2

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

2. If the above hotfix didn't resolve the issue, try:

• Open "Power options" in the control panel.
• Change the active power plan by clicking the "Change plan settings".
• Then click "Change the advanced power settings".
• Scroll down the "Sleep" option and expand it.
• Change the option "Allow hyprid sleep" to off.
• Click "OK".

*note*: Someone said the issue was also fixed by switching "Internet Explorer" ->"JavaScript Timer Frequency" to "Maximum Power Savings".

Reference:

========

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/822d20b5-862d-4d62-b4aa-b13a83975709/

http://social.technet.microsoft.com/Forums/en-US/w7itproperf/thread/f3339d0f-d115-42c4-b5c7-7b4897315956

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/e6afead7-d70a-472f-8f18-26bca208b571/

http://social.technet.microsoft.com/Forums/en-US/w7itprogeneral/thread/69b8c603-c3a5-4d12-a6f7-24c8d88d59da/

http://social.technet.microsoft.com/Forums/kk-KZ/w7itproSP/thread/d1ce698f-7c4e-4c12-acf4-eaf1aeb7e542

http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/2cadc5dd-0236-4b12-9f18-c862478c5b5e

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/sp1-disables-sleep-function/cb5397b4-e312-4883-9963-a7271734991e

This is an strange issue that we found recently.

Symptom:

========

You have several Tasks scheduled. They all run fine until every Sunday at a specific time. The tasks after that time are no longer triggered, nor are there any errors given in the event logs. The Task scheduler service is still running, however no further tasks are triggered.

Cause:

=======

The problem occured after updated Windows Live Essentials 2011 by Windows Update.

Solution:

=========

The problem just occured after the SOXE task ran. After customers disable the SOXE task, ALL of others tasks start to run properly.

Reference:

============

http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/31349b83-c87d-425c-9059-eae7192fb850

http://social.msdn.microsoft.com/Forums/en/winserver2008appcompatabilityandcertification/thread/6fa3c7fa-511b-498d-9b37-1201e1ff2e59

http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/28adff3f-7d08-4301-8337-50454679578a?prof=required

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/2faa4450-bcdf-46d4-934c-1f086a216ae7

Symptom:

=========

On a computer with Windows 7 SP1 installed, you develop and build your application that is using ADO for database access, you find the application doesn't run on the Windows XP, Windows Vista, Windows 7 without SP1. But it runs well on Windows 7 with SP1.

Cause:

=========

There is a by design change in ADO in Windows 7 SP1 that interfaces have new GUIDs.

The reason of this change is mentioned in KB983246(http://support.microsoft.com/kb/983246):

"Some ADO APIs are platform dependent in ADO 2.7 and later versions. On 64-bit versions of Windows, these ADO APIs process arguments by using a 64-bit data type (such as the LONGLONG data type). However, applications that use these APIs still use the LONG data type. Therefore, you receive a "Type Mismatch" error message when you try to run the macro."

The interfaces with new GUIDs (in Windows 7 SP1) don't have such issue.

This change causes a break that if your application is re-compiled on Windows 7 SP1 and it uses early binding to ADO, it probably doesn't work on down-level OSes, such as Windows 7 RTM, Vista, etc. Please note that this break only happens when the application is re-compiled. Existing applications should run on Windows 7 SP1 without any problems.

Solution:

========

If you have to re-compile your application on SP1, there are several solutions:

1. Request a package of KB983246 and install it on your customers' machines. Re-compiled application should work after the package is installed.
2. Re-write your application to use later binding to ADO, or use interfaces with name xxx_deprecated.
3. Keep an old version of ADO typelib (i.e., msado28.tlb) (copy from Windows 7 RTM), then compile your application with the old typelib, instead of the one in your system.

• Open Regedit and locate the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\TypeLib\{2A75196C-D9EB-4129-B803-931327F72D5C}
• Right click, Permissions, Advanced, Owner, Change owner to Administrators, Click OK, OK
• Run C:\Windows\Microsoft.NET\Framework\v4.0.30319\regtlibv12 -u "%CommonProgramFiles(x86)%\system\ado\msado28.tlb"
• Copy msado28.tlb from Win7 RTM/Win2008R2 RTM to your local machine, note the folder for the next step.
• Run C:\Windows\Microsoft.NET\Framework\v4.0.30319\regtlibv12 "{path}\msado28.tlb"

Edit: please refer to the knowledge base article kb2517589

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

To recover the no-boot situation, you need to do system restore or revert to Windows 7 RTM:

1. Apply System Restore from the Windows Recovery Environment (WinRE)

At boot-up, Hit F8 --> Repair --> System Recovery Options Window --> System Restore

2. If the system restore failed, you can use the following command to revert to Windows 7 RTM running state:

In the WinRE, run the command prompt and run the following command:

DISM /image:C:\ /cleanup-image /revertpendingactions

3. You can also perform an inplace upgrade of Windows using your DVD media.

Symptom:

========

When you are installing Windows 7 or Windows Server 2008 R2 SP1, the system is required to reboot. During the rebooting and applyting the updates (Applying update operation xxxxxx of xxxxxx), you may encounter the 0xC000009A error and hang. So you can not log into  the WIndows any more.

A typical error is like below:

Error C000009A applying update operation 115991 of 316581 (\Registry\...)

Cause:

=======

The error 0xC000009A is STATUS_INSUFFICIENT_RESOURCES. The error may be due to too many language pack being installed on the system.

Solution:

=======

Following the below steps to remove language pack before installing SP1:

1. Click Start and openControl Panel.

2. Open "Region and Language"

3. Selec "Keyboards and Languages" tab.

4.  Click "Install/Uninstall Languages"

5. Uninstall display languages except English.

Then you should be able to install SP1. After SP1 is installed successfully, you can re-apply the language pack.

More information:

==============

To recover the no-boot situation, you need to do system restore or revert to Windows 7 RTM:

1. Apply System Restore from the Windows Recovery Environment (WinRE)

    At boot-up, Hit F8 --> Repair --> System Recovery Options Window --> System Restore

2. If the system restore failed, you can use the following command to revert to Windows 7 RTM running state:

In the WinRE, run the command prompt and run the following command:

   DISM /image:C:\ /cleanup-image /revertpendingactions

Reference:

==========

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/b69a067c-487d-43a2-b748-44dd6a402522

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/5d46d261-fa59-425d-825f-d25f14be0802

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/5d46d261-fa59-425d-825f-d25f14be0802

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/cad66cc7-9912-4cbe-898f-ad8ff9344308

05/26 Edit: A hotfix was released to fix this error, please install it. http://support.microsoft.com/kb/2534366

Symptom:

=========

When you install Windows 7 or Windows Server 2008 R2 SP1 you may receive error 0x800f081f or 0x8024200D.

When you check the CBS log(C:\Windows\Logs\CBS\cbs.log), you will find the errors like below:

2011-03-03 21:38:06, Error CBS Exec: Failed to pre-stage package: Package_for_KB976933~31bf3856ad364e35~amd64~cs-CZ~6.1.7601.17514, file: TsUsbGD.sys, source: \\?\C:\Windows\Servicing\Packages\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\TsUsbGD.sys, sandbox: (null) [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2011-03-03 21:38:06, Info CBS Failed to gather all required files. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

Solution:

=======

Please use the following methods to resolve the issue:

1. Run  System Update Readiness Tool (KB947821). It should resolve the error in most of cases.

2. This may be due to a pre-release version of the RSAT tools being installed on the system. To alleviate this failure, do the following:

• Uninstall the pre-release RSAT tools
• Reboot the system
• Install the release version of the RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en)
• Reinstall SP1.

Please see details at the blog http://blogs.technet.com/b/asiasupp/archive/2011/02/18/remote-administration-pack-cannot-install-on-windows-7-service-pack-1.aspx

3. Run a remove package command for offending package identified in the CBS log or in the system event log.

For example, you may find the following event in the system event log:

 The example command is like below:

dism /online /remove-package /packagename:Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514

Reference:

==========

http://social.technet.microsoft.com/Forums/en-US/winserversetup/thread/59b95d2e-2ba9-4879-93c8-3e75d8da6e6a/

http://social.technet.microsoft.com/Forums/pt-BR/winvistapt/thread/dd35d043-1ad6-4de5-842d-0bd0798d0956

http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/593d9393-41f9-493a-92e1-34ef9f0b02bc/

http://social.technet.microsoft.com/Forums/en-CA/w7itproSP/thread/b9987c7c-ffe0-4497-b87b-b3e789a5fd16

http://blogs.technet.com/b/asiasupp/archive/2011/02/18/remote-administration-pack-cannot-install-on-windows-7-service-pack-1.aspx

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

This is a known issue. Windows 7 does not apply customized power plan policy created by Group Policy Management Editor.


Repro steps: (w and w/o SP1)

==========

1. Open group policy management editor=>computer configuration=>preferences=>control panel settings=>power options

2. Create new power plan, in ACTION column, choose “Create” option

3. In next column choose either of the build in plan, choose “High performance” as an example.

4. Check the “set as the active power plan”

5. Customize power plan settings

6. Click ok the finish policy setting.

7. In windows 7, restart computer to apply computer policy.

8. Open power option, you will find the “High performance” box is not checked. But customized settings such as idle time are applied.



Note: this problem also exists in user configuration.


Solution:

=========

In the new power plan properties, there is four options in ACTION column “create” ”update” ”replace” ”delete”, choose the “update” option instead of “create”, then problem will not occur.

Do not choose "Create" or "Replace”, instead, choose "Update" then it works fine.

Read the following article. At the end the behavior of Replace/Update/Delete/Active is explained:

Managing Power with Group Policy: Part 3 of 3

http://blogs.technet.com/askds/archive/2008/03/21/managing-power-with-group-policy-part-3-of-3.aspx


Reference:

=========

http://social.technet.microsoft.com/Forums/en/winserverGP/thread/97da91af-8c54-4cc0-ae90-3911ca3ed7aa

http://social.technet.microsoft.com/Forums/en/winserverGP/thread/5a267578-3ff9-4f51-b267-dbebce43609d

http://social.technet.microsoft.com/Forums/en/winserverGP/thread/258c0519-4d1f-4809-b152-5a408995b5b7

Some users reported the update failed installation (through Windows Update or WSUS). For example, 2419640 and 967723.

Symptom:

=========

The installation will fail with error 0x80070490 or 0x800b0100 or 0x80080005

Sometimes, the event log shows an event id 4375 Servicing:

Windows Servicing failed to complete the process of setting package KB967723 (Security Update) into Installed(Installed) state

followed by event id 20 WindowsUpdateClient:

Installation Failure: Windows failed to install the following update with error 0x80070490: Security Update for Windows Server 2008 x64 Edition (KB967723).

But manually install this hotfix is success.

Solution:

=========

1. Try manually install this hotfix.

2. Follow KB 958044 to resolve "0x80070490" error

958044 You receive a "0x80070490" error code when you use Windows Update or Microsoft Update Web sites to install updates

http://support.microsoft.com/default.aspx?scid=kb;EN-US;958044

There are also blogs out there on this that have you going through the registry deleting references to the update:

http://blogs.msdn.com/andrekl/archive/2008/09/29/how-to-overcome-error-0x80070490-when-installing-updates-in-windows-vista-server-2008.aspx

3. Follow KB 956702 and 2006291 to resolve "0x800B0100" error

956702 Error message when you try to use the Windows Update or Microsoft Update Web sites to install updates: "0x800B0100"

http://support.microsoft.com/kb/956702/en-us

2006291 Error message When You Bring up the Server Manager Console and click on Add / View Roles: "0x800B0100"

http://support.microsoft.com/kb/2006291/en-us

4. Follow the below steps to resolve "0x80080005" error:

Do these steps from an elevated CMD prompt:

net stop wuauserv
cd %systemroot%\SoftwareDistribution
ren SoftwareDistribution SoftwareDistribution.old
net start wuauserv

Download update manually, and attempt to install form download.

If still fails, run:

sfc /scannow from an elevated command prompt as well.

Reboot and try manual update again

Reference:

==========

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/cea67410-fba5-424a-a8c4-aa3e2e5696b3

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/b633418b-29fc-4f35-b4c9-1d2d2ce489fe

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/e1c987ec-92bd-4dbd-95f8-ad17b284ac79/

http://social.technet.microsoft.com/Forums/en-IE/winservergen/thread/147b0c61-3d04-4cd4-8ea8-c805139cb57e

http://social.technet.microsoft.com/Forums/zh-CN/2219/thread/0a1e8139-0b82-4bd1-9167-5de7600a1a60

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/2b5f072e-2c50-4af7-9b79-c5c1e28ad701

http://social.technet.microsoft.com/Forums/en/winservergen/thread/a3de69a3-2bdb-4502-ac50-45546b126e1f

http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/84a56448-ab56-4241-9699-01aa41b725f9/

http://social.technet.microsoft.com/Forums/en-US/itprovistasp/thread/4138878a-64c1-4196-ae43-e7b7286cbdf3/

http://social.technet.microsoft.com/Forums/en-US/winserverManagement/thread/0940a7db-a121-48e2-89c4-5fe5ff15f669/

http://social.technet.microsoft.com/Forums/en/winserverwsus/thread/2bb45bac-b9b4-4548-ac60-cf1b1a94cf58

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2general/thread/1fdec54d-c24c-40d4-995a-1485ad771201

http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/0b7b72bb-559c-4009-9833-0ea9fdd0ec6c

http://social.technet.microsoft.com/Forums/en/winservermanager/thread/1a3ac88b-e67e-432f-9e9b-42def16091d5

http://social.technet.microsoft.com/Forums/en/winservermanager/thread/93594476-1057-427a-bb28-8830860555b9

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/fd3c43fc-3f91-4a9c-adca-4494fdf53f54

A lot of threads found

Symptom1:

Unable to open the Microsoft Management Console, MMC fails with the message:

“MMC could not create the snap-in”.

MMC could not create the snap-in. The snap-in might not have been installed correctly.

Name: Server Manger

CSLID: FX:{18ea3f92-d6aa-41d9-a205-2023400c8fbb}

Some customers reported after install .NET update, the issue appeared, i.e http://support.microsoft.com/kb/2416473

KB 2486109(http://support.microsoft.com/kb/2486109) was published for this issue.

This problem occurs if the .Net Framework 3.0 feature is not enabled and an update for .net framework 3.5SP1 is installed (which could be through the windows update or through a deployment tool).

If the above steps can not resolve it, use this method:

1. Navigated to the following directory:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG

2. Renamed machine.config to machine.config.old

3. Copy the same file from the working server.

Forum links:

==========

http://social.technet.microsoft.com/Forums/en/winservermanager/thread/6e77f9d0-e86d-4a35-abed-504cf217fc96

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/b88b12ed-aa1d-428f-a99e-20bb7212e095

http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/7b9867d2-c8b6-447f-8256-699a309733aa

http://social.technet.microsoft.com/Forums/en/winservermanager/thread/ca91c974-7b35-4f6e-94f0-39ad50e9a562

http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/07feb5ce-a757-45f8-972e-43c343d946fb

http://social.technet.microsoft.com/Forums/en-US/winserverwsus/thread/f4ff48b7-cc59-4206-84cc-30c17d4d8149

http://social.technet.microsoft.com/Forums/en/w7itproSP/thread/0673911a-685e-41d8-9d6e-d0caa0ae7071

http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2rds/thread/6752d55e-f4de-4e67-bfbf-ec00d998e8c2

http://social.technet.microsoft.com/Forums/en-CA/winservermanager/thread/746919bc-97a8-4ee3-b9ba-97a4be2d9cc7

http://social.technet.microsoft.com/Forums/en-CA/winservermanager/thread/f60807d3-dfac-42ba-9e9e-f42350ef2f65

A lot of threads found

Symptom 2:

After installing security update http://support.microsoft.com/kb/2449742, the  MMC console opens but when you try to do anything inside you may get error "Microsoft Management Console has stopped working".

The following events are logged:

Event Type: Error
Event Source: Application Error
Event Category: (100)
Event ID: 1000
Date: 14/04/2011
Time: 08:32:53
User: N/A
Computer: cherami.mydomain.local
Description:
Faulting application w3wp.exe, version 7.0.6002.18005, faulting module 49e03238, version mscorwks.dll, fault address 0x2.0.50727.5653.

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1023
Date: 14/04/2011
Time: 08:32:53
User: N/A
Computer: cherami.mydomain.local
Description:
.NET Runtime version 2.0.50727.5653 - Fatal Execution Engine Error (000007FEF21B6D36) (80131506)

Solution:

• If you never installed MS11-028 or have uninstalled it, you should install KB979744-v2 from here or here and then install MS11-028
• If you still have MS11-028 installed, and your Exchange Management tools are currently broken, you should install KB979744-v2 from here or here
•  

Edit: Please refer to http://support.microsoft.com/kb/2540222 for the resolution.

In a Windows 64bit system, after you install IE9 64-bit, you will get two IE in the start menu. One is 32-bit, the other is 64-bit.

Some customers reported that they can not open the 64-bit version of IE9, well, there is no problem to open the 32-bit version of IE9 . They said there is no problem to open 64-bit version of IE8 before the upgrade.

The symptom may be the window opens, hangs for a few seconds, and closes itself.

Solution:

Use the following steps to resolve this problem:

1. Change the option of accelerated graphics:

·Close all windows of Internet Explorer

·ClickStart

·Type Internet Options

·Press Enter on your keyboard

·Click the Advanced tab

·Check the Use software rendering instead of GPU rendering* box

·Click OK

2. If the above steps didn't work, use the following solution:

- Open registry editor (regedit)

- Go to HKCU\Software\Microsoft\Internet Explorer\Main

- Add a Dword called TabProcGrowth and set its value to 0.

Reference:

http://answers.microsoft.com/en-us/ie/forum/ie9beta-windows_7/ie9-rc-64-bit-wont-open/e09260c2-e19d-41ac-a728-b8d5ca8b6b1b?page=5

http://answers.microsoft.com/en-us/ie/forum/ie9beta-windows_7/win7-64-bit-has-both-32-bit-and-64-bit-ie8/16dbeddd-412d-400b-bef9-e0a7986b6dd2?page=1

ActiveX Filtering is a new feature introduced in IE9. ActiveX Filtering allows you to browse the Web without running any ActiveX controls.

You can read more about it in the link http://ie.microsoft.com/testdrive/Browser/ActiveXFiltering/About.html.

ActiveX Filtering is disabled by default. You can turn it on via the Tools Menu: Tools ->Safety->ActiveX Filtering

Well, we found a few cases that when you activate ActiveX Filtering and try to play a flash video in a website, you get a notification that I must update Adobe Flash. Uninstall and reinstall Adobe Flash doesn't resolve the problem.

But when you de-select ActiveX Filtering, the videos play normally.

Solution:

=======

(1)Those Flash/Silverlight error messages appear if the correspondent ActiveX plugins are filtered on the site you visit. Turn off ActiveX Filtering for the site and all will be good. 

(2) Add the website to the trusted sites. The idea now is to add the sites that you want to play Flash or Java contents on to the trusted sites.

Then make one small configuration change by clicking custom level button in the Tool->Internet options->Security tab, scroll down until you find the entry Allow ActiveX Filtering under ActiveX controls and plug-ins. All you need to do is to change the parameter to disable and click the ok button to save the new setting.

 (3) View these webpages in Internet Explorer 9 Compatibility View.

Compatibility View forces IE to render the webpage in the IE8 document mode which does not contain the IE9 changes to the rendering engine.

To add a website to Compatibility View when you cannot get to that website, follow these steps:

1. Start Internet Explorer
2. Press the ALT key on your keyboard to access the Menu
3. Click Tools and then click Compatibility View Settings
4. Type the address of the website into the Add this website: text box
5. Click the Add button to add the site to the Compatibility View list and then close the Compatibility View Settings window
6. Browse back to the website again to see if the issue is resolved

Reference:

=========

The threads we found in the forum:

http://answers.microsoft.com/en-us/ie/forum/ie9beta-windows_7/internet-explorer-9-rc-silverlight-and-adobe-flash/055d2f0b-8679-460d-bc04-06ff4d58f700

http://answers.microsoft.com/en-us/ie/forum/ie8-windows_other/problems-with-activex-filtering-in-ie9-rc/075a6be4-b5af-4773-a498-ba4f08313f1f

IE9 RC released a few days ago. So we will start posting a series of IE 9 known issues and best practices.

This article describes an issue about Internet Explorer 9 and Netflix in Windows 7 Media Center.

Symptom:

After you install Windows Internet Explorer 9 Release Candidate (RC) on a computer that is running Windows 7, the Netflix application in Windows Media Center may encounter an error when it initiates video playback.

The error is something like "script error".

Resolution:

To resolve this problem, follow these steps (Details in http://support.microsoft.com/kb/2512239):

1. Click Start menu, type Regedit.exe in the Search programs and files box, and then press ENTER. Click Yes in the UAC prompt dialog box.
2. Locate and then click the following registry subkey:
   HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_USE_LEGACY_JSCRIPT
   
   Note Create the FEATURE_USE_LEGACY_JSCRIPT subkey if it does not exist.
3. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
4. Type ehexthost.exe, and then press ENTER.
5. Right-click ehexthost.exe, and then click Modify.
6. In the Value data box, type 1, and then click OK.
7. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
8. Type ehexthost32.exe, and then press ENTER.
9. Right-click ehexthost32.exe, and then click Modify.
10. In the Value data box, type 1, and then click OK.
11. Exit Registry Editor.

Reference:

http://social.answers.microsoft.com/Forums/en-US/InternetExplorer/thread/21878302-e98e-4539-9bae-a00a360d9da6
http://social.technet.microsoft.com/Forums/en-US/w7itpromedia/thread/2533baba-52af-4ed4-83cb-5b5be91b5b61
http://social.technet.microsoft.com/Forums/en-US/w7itpromedia/thread/3ebcc418-a462-448d-b90b-fb130e33436f
http://social.technet.microsoft.com/Forums/lt-LT/w7itpromedia/thread/3ebcc418-a462-448d-b90b-fb130e33436f

Here are several issues with Remote Server Administration Tools and Windows 7 SP1.

(1) You can not install RSAT on Windows 7 SP1 (http://support.microsoft.com/kb/2517239/en-us).

After installing windows7 service pack 1, remote server administration update tool cannot install on the machine.

The error massage is “this update is not applicable to your computer”.

here is the repro steps if you are interested to test
1.    On a Windows 7 machine, install SP1.
2.    Try to install Remote Server Administration Tools (RSAT).
3.    The error message “this update is not applicable to your computer” will appear.


Workaround:

Uninstall SP1, install RSAT and then apply SP1 again.

Reference:

RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en)

http://social.technet.microsoft.com/Forums/en/w7itproappcompat/thread/ef1b47e4-85f0-4124-b065-f80461c9e250

http://social.technet.microsoft.com/Forums/en/w7itproSP/thread/0d763f12-30f8-4d13-8534-315d5c34dd0d

http://social.technet.microsoft.com/Forums/en-US/w7itproSP/thread/12d1e8a5-7e43-4ba6-82aa-20b6884128e5

http://social.technet.microsoft.com/Forums/bg-BG/w7itproSP/thread/9d448ef8-ff9a-4917-8476-fd81073b88f7

(2) 0x800f081f when you install Win7 SP1.

When you attempt to install the standalone package for Service Pack 1 for Windows 7/2008 R2, you might get the following error:

0x800f081f  <--This maps to CBS_E_SOURCE_MISSING

You'll be prompted to run the CheckSUR utility and running that utility will not resolve the issue. 

This may be due to a pre-release version of the RSAT tools being installed on the system.  To alleviate this failure, do the following:

1.  Uninstall the pre-release RSAT tools

2.  Reboot the system

3.  Install the release version of the RSAT tools (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7d2f6ad7-656b-4313-a005-4e344e43997d&displaylang=en)

4.  Reinstall SP1.

 Edit:

The Remote Server Administration Toolkit update to support Windows 7 Service Pack 1 has released. Come and get it:

www.microsoft.com/.../details.aspx

Last week, a large amount of customers complained they were getting the following pop up message almost in every single website using IE:

xd_proxy[1].css

Then a notepad opens up with the following information:

.app_content_51546247891 a.uiLinkSubtle { display: none; }
.app_content_51546247891 a.UIImageBlock_ICON_Image { display: none; }

#bootloader_Zvucx { height: 42px; }

After further investigation, it was proved to be a facebook script issue. This error was also ovbsered in Firefox, Safari and Chrome, not just IE.

You can refer to http://bugs.developers.facebook.net/show_bug.cgi?id=14971

It seems to affect every single website that uses social plugins for Facebook.

Solution:

Deleting cache and cookie of the web browser. Steps for IE:

1.  From Internet Explorer menu bar, select Tools\Internet Options.
2.  From the General Tab select "Delete" found in the Browsing History section.
3.  Click  "Delete Files" , click yes to confirm.
4.  Click  "Delete Cookies", click yes to confirm.
5.  Click  "Delete Passwords", click yes to confirm.
6.  Click Close
7.  Click OK.