From: Sh@dow.br   
      
   On Thu, 1 Feb 2024 10:28:32 +0000, "Kerr-Mudd, John"    
   wrote:   
      
   >On Wed, 31 Jan 2024 18:39:41 -0300   
   >Shadow  wrote:   
   >   
   >> On Wed, 31 Jan 2024 19:44:07 +0000, "Kerr-Mudd, John"   
   >>  wrote:   
   >>   
   >> >On Wed, 31 Jan 2024 15:38:10 -0300   
   >> >Shadow  wrote:   
   >> >   
   >> >[]   
   >> >>   
   >> >> 	I managed to fix the problem, partially. I simply deleted the   
   >> >> "Hardware Manager"  Snapin key.   
   >> >>   
   >   
   >   
   >   
   >>   
   >> 	Since it referenced {94abaf2a-892a-11d1-bbc4-00a0c90640bf}   
   >> 	I deleted that key too:   
   >>   
   >> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns   
   >> \{90087284-d6d6-11d0-8353-00a0c90640bf}]   
   >> "NameString"="Extensão do 'Gerenciador de dispositivos'"   
   >> "Provider"="Microsoft Corporation"   
   >> "Version"="1.0"   
   >> "About"="{94abaf2a-892a-11d1-bbc4-00a0c90640bf}"   
   >>   
   >> 	Notice, no ""NameStringIndirect". Which usually refers to a   
   >> .dll.   
   >>   
   >> 	Is yours the same?   
   >   
   >Barring the Portugese translation, yes   
   >   
   >So it doesn't seem to be the registry at fault (or at least not these   
   >entries).   
      
   	I restored an ERUNT backup from when I knew it was working,   
   One of the first things I did before I started this thread.   
   	And I've scanned all the relevant DLLs  and EXEs with Jotti**.   
   No malware detected, not that it came as a surprise, after all, this   
   is a hardened XP.   
   	:)   
   	TY   
   	[]'s   
      
   ** I don't use a resident AV. Most of them have gone rogue and are   
   worse than the Trojans they claim to protect you from.   
   --   
   Don't be evil - Google 2004   
   We have a new policy  - Google 2012   
   Google Fuchsia - 2021   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)