Noel
Tue Dec 28 09:09:56 CST 2004
Hmmm - looks like I was at least partially correct about BitDefender being
responsible - the instructions on their website for resetting System Restore
to rid the archive of potential threats is badly wrong!!!
Doing things the way they recommend is almost guaranteed to cause problems
with System Restore - with an outcome similar to that produced by Norton -
stuffing the C:\_Restore\Temp folder with 32K++ files with the result that
SR freezes a new install.
Their advice for XP is almost as bad - but unlikely to cause the same
problems! (I have informed them of this - whether they bother to respond or
not will be interesting!)
Here is the CORRECT way to reset System Restore, and clear the archive......
(assuming it's not already broken)
To Reset System Restore -
System | Performance | File System | Troubleshooting and check
"Disable System Restore",
Apply and IMMEDIATELY reboot.
This will flush you restore folder and erase all checkpoints, then,
System | Performance | File System | Troubleshooting and uncheck
"Disable System Restore",
Apply and again IMMEDIATELY reboot.
This should now automatically create a new checkpoint immediately following
the restart.
Finally adjust the space allocated to the restore folder,
System | Performance | File System | Hard Disk and adjust the restore slider
to your preferred setting.
Most people find that a setting of 200-300MB is sufficient to hold 10-15
days worth of restore points, unless you are doing a lot of
installs/uninstalls, or installing large applications (such as Office).
HTH
--
Noel Paton (MS-MVP 2002-2005, Windows)
Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm
http://tinyurl.com/6oztj
A Happy Xmas, and a Merry New Year to everyone!
Please read
http://dts-l.org/goodpost.htm on how to post messages to NG's
"Noel Paton" <NoelDPspamless@btopenworld.com> wrote in message
news:umTyjyO7EHA.3236@TK2MSFTNGP15.phx.gbl...
> Norton is only the most common causer of the problem - it may be that
> BitDefender can also cause it.
>
> You can create your own Startup disk from Add/Remove Programs|Startup
> disk - if the PC won't/cant do that, then download a Win ME boot diskmaker
> (the OEM one) from www.bootdisk.com . Run the download to create a floppy
> disk that you can then use to boot the PC, and run the fix.
>
>
> --
> Noel Paton (MS-MVP 2002-2005, Windows)
>
> Nil Carborundum Illegitemi
>
http://www.btinternet.com/~winnoel/millsrpch.htm
>
http://tinyurl.com/6oztj
> A Happy Xmas, and a Merry New Year to everyone!
>
> Please read
http://dts-l.org/goodpost.htm on how to post messages to NG's
>
> "J. Ascher" <JAscher@discussions.microsoft.com> wrote in message
> news:0F3E8A39-59BF-4E8D-A95A-A664B0B4154D@microsoft.com...
>>I tried the first solution, bu the file wasn't to be found. I tried the
>> second option, but got the same message after reinstalling the update. I
>> don't think I have a start-up disk. I got my machin from Gateway and all
>> I
>> have that's close to this startup disk is three "system restore" disks.
>> If
>> this is what I need I need to know which of the three disks is a start
>> up.
>> Hope you can help!
>>
>> BTW, I use a free antivirus(Bitdefender), not Norton so I don't know why
>> Norton Live Update would be affecting my computer a couple of months
>> after I
>> uninstalled their software.
>>
>>
>> "Noel Paton" wrote:
>>
>>> Your %1/%2 error is caused usually by Norton LiveUpdate, corrupting the
>>> System Restore archive - although there are other possible causes.
>>>
>>> Do a Search for the file WININIT.INI - if you find it, then rename it to
>>> WININIT.JNK, and reboot - your problem should be gone.
>>>
>>> If you don't find it, then try this - Start|Run - enter SCANREG /FIX
>>> into
>>> the dialog box, and click OK - windows will reboot - see if that fixes
>>> it.
>>>
>>> If not, then open Windows Explorer - check in Folder Properties that you
>>> are
>>> able to view Hidden and System files (two settings), then Search on your
>>> PC
>>> for files named '_RESTORE' (without the quotes) - you should find the
>>> C:\_RESTORE folder - r-click on it, and select Properties.
>>> How many files/folders are there? If it's around 64 thousand, then
>>> LiveUpdate has been up to its tricks again, and you'll have to
>>> completely
>>> remove the folder from DOS - use the following method, which seems to
>>> be
>>> the easiest at present.
>>>
>>> Reboot to DOS using your Startup disk enter the following commands at
>>> the
>>> A:\> prompt.
>>>
>>> ATTRIB -R -H -S C:\_RESTORE
>>> REN C:\_RESTORE OLDREST
>>>
>>> remove the floppy, and reboot to normal windows. - your error should be
>>> gone, and you should now have a new, single restore point. Go to Windows
>>> Explorer, and delete the C:\OLDREST folder
>>>
>>> HTH
>>>
>>>
>>> --
>>> Noel Paton (MS-MVP 2002-2005, Windows)
>>>
>>> Nil Carborundum Illegitemi
>>>
http://www.btinternet.com/~winnoel/millsrpch.htm
>>>
http://tinyurl.com/6oztj
>>> A Happy Xmas, and a Merry New Year to everyone!
>>>
>>> Please read
http://dts-l.org/goodpost.htm on how to post messages to
>>> NG's
>>>
>>> "J. Ascher" <J. Ascher@discussions.microsoft.com> wrote in message
>>> news:3E11BA00-E657-40D6-8A60-291C1DADAC7E@microsoft.com...
>>> >I tried installing this on my machine, but when I restart the computer,
>>> >I
>>> >get
>>> > this message:
>>> >
>>> > Windows could not upgrade the file %1 from %2
>>> > %1 %2
>>> >
>>> > This repeats six (6) times. The screen says press any key to
>>> > continue.
>>> >
>>> > What do you recommend?
>>>
>>>
>>>
>
>