i wouldn't know really, i don't keep up with what microsoft is doing, i'm
just someone who had some problems with that file, and i used that temporary
fix and everything worked well afterwards. but i can't wait untill they get
that fix, my guess is they are still experimenting with the fix to make sure
the bugs are minimal.
--
Jonathan Perreault
Old Advice #1: Do Not Undermine Windows's Work, New Advice#2: Torture
Windows (Any) Now
Or It'll Undermine You As A User.
Before It Tortures You
Comment: No Matter The Problem Even With Linux
It's Microsoft's And Windows's Faults
"lamawithonel" <lamawithonel@xxxxxx> wrote in message
news:8C4009A0-3CED-4B94-BF49-B146891794A8@xxxxxx
Quote:
> MS,
>
> What's the official stance on this problem? My searches suggest it's
> existed since at least beta. Why no fix?
>
> "jonathan perreault" wrote:
> Quote:
>> Try this fix to see if it repairs your problem. This solution has worked
>> for
>> some people with problematic USB and General Devices:
>>
>> 1. Locate the file INFCACHE.1 in C:\Windows\inf
>>
>> 2. Right click on the INFCACHE.1 file, select Properties >Security >
>> Edit,
>> and give your account full control.
>>
>> 3. Delete INFCACHE.1 (Or just to be safe, rename it to INFCACHE.1.BAK or
>> temporarily move to your desktop but you shouldn't need to, windows
>> doesn't
>> need that file to run, and if it needs to it recreates it).
>>
>> 4. REBOOT
>>
>>
>> --
>>
>>
>> Jonathan Perreault
>> Old Advise: Do Not Undermine Windows's Work,
>> Or It'll Undermine You As A User.
>>
>> New Word Of Advice: Torture Windows (Any) Now
>> Before It Tortures You
>>