J
Jean Gaudreau
Thanks for this solution, I had the same issue has mattymatt79 described, and
it worked good.
The registry values were all to 0.
--
Jean Gaudreau
"Todd J Heron" wrote:
> "Ian" <gruntyonline@hotmail.com> wrote in message...
> >I don't think you will need to use an identical server - you will be able
> >to tell by looking at the keys - there is nothing hardware >specific about
> >them - they are just golorified display settings. (take a back up of the
> >originals just in case though!
>
> >Post back with the results
>
> >Ian
>
> mattymatt79, After you follow the resolution indicated below, scan the
> computer for malware. I've seen mentioned in field reports the "black on
> black" being a classic GUI attack, according to Matt Wagner [MSFT].
>
> The color schemes in the computer's default profile may have been set to
> black for every scheme element. Please review the below steps for this may
> resolve your issue. On the Windows 2003 Server this can be verified by
> navigating to the following registry key:
>
> HKEY_USERS\.DEFAULT\Control Panel\Colors
> If this is the issue all colors scheme element registry values will be set
> to 0. Compare this with a known good copy below:
>
> [HKEY_USERS\.DEFAULT\Control Panel\Colors]
> "ActiveBorder"="212 208 200"
> "ActiveTitle"="0 84 227"
> "AppWorkSpace"="128 128 128"
> "Background"="0 78 152"
> "ButtonAlternateFace"="181 181 181"
> "ButtonDkShadow"="113 111 100"
> "ButtonFace"="236 233 216"
> "ButtonHilight"="255 255 255"
> "ButtonLight"="241 239 226"
> "ButtonShadow"="172 168 153"
> "ButtonText"="0 0 0"
> "GradientActiveTitle"="61 149 255"
> "GradientInactiveTitle"="157 185 235"
> "GrayText"="172 168 153"
> "Hilight"="49 106 197"
> "HilightText"="255 255 255"
> "HotTrackingColor"="0 0 128"
> "InactiveBorder"="212 208 200"
> "InactiveTitle"="122 150 223"
> "InactiveTitleText"="216 228 248"
> "InfoText"="0 0 0"
> "InfoWindow"="255 255 225"
> "Menu"="255 255 255"
> "MenuText"="0 0 0"
> "Scrollbar"="212 208 200"
> "TitleText"="255 255 255"
> "Window"="255 255 255"
> "WindowFrame"="0 0 0"
> "WindowText"="0 0 0"
> "MenuHilight"="49 106 197"
> "MenuBar"="236 233 216"
>
> There is two ways to fix this problem:
>
> 1. Export the registry key from a known good machine into a .REG file.
> Import the .REG file into the new machine.
>
> 2. You can also construct/copy-paste the following information into a text
> file and give it a file name with a .REG extension.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>
it worked good.
The registry values were all to 0.
--
Jean Gaudreau
"Todd J Heron" wrote:
> "Ian" <gruntyonline@hotmail.com> wrote in message...
> >I don't think you will need to use an identical server - you will be able
> >to tell by looking at the keys - there is nothing hardware >specific about
> >them - they are just golorified display settings. (take a back up of the
> >originals just in case though!
>
> >Post back with the results
>
> >Ian
>
> mattymatt79, After you follow the resolution indicated below, scan the
> computer for malware. I've seen mentioned in field reports the "black on
> black" being a classic GUI attack, according to Matt Wagner [MSFT].
>
> The color schemes in the computer's default profile may have been set to
> black for every scheme element. Please review the below steps for this may
> resolve your issue. On the Windows 2003 Server this can be verified by
> navigating to the following registry key:
>
> HKEY_USERS\.DEFAULT\Control Panel\Colors
> If this is the issue all colors scheme element registry values will be set
> to 0. Compare this with a known good copy below:
>
> [HKEY_USERS\.DEFAULT\Control Panel\Colors]
> "ActiveBorder"="212 208 200"
> "ActiveTitle"="0 84 227"
> "AppWorkSpace"="128 128 128"
> "Background"="0 78 152"
> "ButtonAlternateFace"="181 181 181"
> "ButtonDkShadow"="113 111 100"
> "ButtonFace"="236 233 216"
> "ButtonHilight"="255 255 255"
> "ButtonLight"="241 239 226"
> "ButtonShadow"="172 168 153"
> "ButtonText"="0 0 0"
> "GradientActiveTitle"="61 149 255"
> "GradientInactiveTitle"="157 185 235"
> "GrayText"="172 168 153"
> "Hilight"="49 106 197"
> "HilightText"="255 255 255"
> "HotTrackingColor"="0 0 128"
> "InactiveBorder"="212 208 200"
> "InactiveTitle"="122 150 223"
> "InactiveTitleText"="216 228 248"
> "InfoText"="0 0 0"
> "InfoWindow"="255 255 225"
> "Menu"="255 255 255"
> "MenuText"="0 0 0"
> "Scrollbar"="212 208 200"
> "TitleText"="255 255 255"
> "Window"="255 255 255"
> "WindowFrame"="0 0 0"
> "WindowText"="0 0 0"
> "MenuHilight"="49 106 197"
> "MenuBar"="236 233 216"
>
> There is two ways to fix this problem:
>
> 1. Export the registry key from a known good machine into a .REG file.
> Import the .REG file into the new machine.
>
> 2. You can also construct/copy-paste the following information into a text
> file and give it a file name with a .REG extension.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
>