• Windows XP start up very slowly (Black Screen after Windows XP logo)

     

    問題徵狀:

    Windows XP在開機過程中,跑馬燈階段結束,接下來您會看到二分鐘至數十分鐘不等的黑畫面,在黑畫面過程中,不會有任何的游標或視窗出現,在這段時間後仍可以正常出現登入Windows 的畫面。

    問題發生原因:

    以下所描述的只是可能的一種開機慢原因,並非所有開機慢的原因都是和這篇文章所描述有關。

    會發生這個問題,有可能是HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Digest下的子機碼不斷被產生,導致開機在載入C:\Windows\system32\config\Default檔案是需要非常長的時間所致。

     

    解決方法:

    1.請您確認在C:\Windows\system32\config\Default這個檔案size是否有數十MB以上。正常來講,這個檔案應該只會二百多KB至1 、2MB不等。如果確認這個檔案的大小確定有至數十MB,請再往下做。

    2.執行regedit,找到HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Digest機碼。請直接將Digest這一層整個刪除。

    3.重新開機,確認問題是否能解決。

    4.如果問題確定解決,您再回到HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings機碼下仍看到Digest會持續產生子機碼,請至新增移除程式看,是否有INTEL(R) management engine components程式存在,如果有的話,請您嘗試移除或是看是否有新版的程式可以安裝,來確認是否可以完全解決這個問題。

  • WindowsXP中,透過某些區段的內碼造字,在記事本以外的應用程式均不能正常顯示

    問題徵狀:當您在WindowsXP中,透過某些區段的內碼造字,在記事本以外的應用程式均不能正常顯示。

    image

    問題發生的原因是因為有部分私用字元區域,是保留給私用定義使用者或軟體廠商所編碼的Unicode 字元集中的字碼指標範圍。

    下列區段為Windows XP系統會占用到的位置:

    Unicode位置:F001~F031

    image

    在Big-5內的位置為8350~83A1

    image

    解決方法:

    請您安裝下列文章編號KB 831176的Hotfix,

    831176 富士通專用字體不會正確顯示在 Windows Server 2003 或 Windows XP 中的 Unicode 私人使用區域

     

    http://support.microsoft.com/kb/831176/zh-tw

    安裝完成後並重新開機,所有字元即可正常顯示。

  • · Windows Update自動更新時,KB2518864、KB2572073、KB2633880重覆要求更新

    問題徵狀:執行Windows Update自動更新時,KB2518864、KB2572073、KB2633880重覆要求更新

    KB2518864、KB2572073、KB2633880 Microsoft.NET Framework的更新元件,問題發生的原因是因為電腦上的 Microsoft.NET Framework 已損毀或遺失,導致檢查更新時無法正確判斷,以致重複檢查以及安裝。

    解決方法:

    (http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip) 下載 .NET Framework 自動清除工具,

    http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip

    選擇【.NET Framework - All Versions,然後按一下【Cleanup Now】。

    重新更新,已不會出現重複的更新。若您的軟體需要用的對應版本的.NET Framework,當您下次更新時,系統會自動幫您偵測並下載對應的版本。

  • WSUS: Script to delete duplicate SID created by Disk Imaging / Disk Cloning

    You might notice that some computers are appearing multiple times in WSUSAdmin - Computers and some of them disappear very often. This is due to duplicate SUS client IDs. Take a look at this script which deletes duplicate SUS client IDs found on a computer. These IDs are often found on computers where the operating system was installed using an image-based setup.

    Script Code

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

    @echo off
    Echo Save the batch file "AU_Clean_SID.cmd". This batch file will do the following:
    Echo 1.    Stops the wuauserv service
    Echo 2.    Deletes the AccountDomainSid registry key (if it exists)
    Echo 3.    Deletes the PingID registry key (if it exists)
    Echo 4.    Deletes the SusClientId registry key (if it exists)
    Echo 5.    Restarts the wuauserv service
    Echo 6.    Resets the Authorization Cookie
    Echo 7.    More information on http://msmvps.com/Athif
    Pause
    @echo on
    net stop wuauserv
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
    REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
    net start wuauserv
    wuauclt /resetauthorization /detectnow
    Pause

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

    SUS client ID will be generated at next detection.
     
  • Dedicated Video Memory does not display as expected

    Consider the following scenario:

    You have onboard UMA 384 MB + 1GB from the video adapter and you expect the total video memory to be about = 384MB + 1024 MB => 1408 MB

    However, in the Control Panel -> Appearance and Personalization ->Display ->Screen Resolution Panel, click [Advanced Settings]. Under the "Adapter" tab, you will see the Dedicated Video memory value displayed as 1536MB.

    UMA DSC_384

    Why?

    Basically, the UI is coded to display the Dedicated Video Memory in the form of power of 2. So, it uses this function “NextPowerof2(uNumMegs/8)” to calculate the allowed adjustment. And here are the allowed adjustments for different ranges of memory:

    //  129M-256M rounds in multiples of 32M

    //  257M-512M rounds in multiples of 64M

    //  513M-1G rounds in multiples of 128M

    //  1G+-2G rounds in multiples of 256M

    //  2G+-4G rounds in multiples of 512M

    And we can see that for the case of UMA_384+DSC(1024MB), the adjustment is in multiples of 256MB. It is not possible to display 1408MB. And since 1408MB is greater than 1280MB(256*5), that is why you are seeing 1536MB(256*6) by design.

    This power of 2 algorithm was implemented per KB938838.

    Windows Vista displays the incorrect dedicated video memory size for certain display adapters

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

    To display a more accurate video memory figures, use the videomemory.exe tool from the DirectX SDK tools. Link:
    http://msdn.microsoft.com/en-us/directx/aa937788