• Tip: Search with Internet Explorer 9 (IE9)

    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"

  • Internet Explorer 9(IE9) Group Policy Preferences (GPP)

    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

     

     

  • Windows 7 SP1 installation failed with error 0x800f0a12

    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

     

     

  • Windows XP: Stop Error 0x0000007F or 0x1000007F after installing MS11-011 (KB2393802)

    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

  • Error message “Display driver stopped responding and has recovered.”

    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