Windows XP Prof SP3
When I run disk cleanup it deletes around 36 system files, c_850.nls and the
like. As a result windows does not boot up. It gives a file missing warning.
I repeated this three times, last time selecting only temporary files to be
deleted. Same keeps happening and I have to recover the system from the
image. Any help?

If the windows Disk Cleanup is doing that, something is seriously up with
your sys
You might try the system file checker for starters

"Tatar" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Windows XP Prof SP3
> When I run disk cleanup it deletes around 36 system files, c_850.nls and
> the like. As a result windows does not boot up. It gives a file missing
> warning. I repeated this three times, last time selecting only temporary
> files to be deleted. Same keeps happening and I have to recover the system
> from the image. Any help?
>

"Tatar" wrote:

> Windows XP Prof SP3
> When I run disk cleanup it deletes around 36 system files, c_850.nls and the
> like. As a result windows does not boot up. It gives a file missing warning.
> I repeated this three times, last time selecting only temporary files to be
> deleted. Same keeps happening and I have to recover the system from the
> image. Any help?
>
>
>
Since it does this each time you recover from the image, that means the
image might be corrupt as well. Check your hard drive with scandisk /r and
the hard drive maker's disk checking utilities to rule out problems with the
drive. If the drive is good, put a fresh image on it and install CCleaner and
see if it damages the install. If it doesn't, don't use Disk Cleanup anymore.
If it does, you have either a good image of a bad install, or a bad image.

Thanks DL and Mark. I have run sfc /scannow a few times and all is well.

"Mark Adams" <(E-Mail Removed)> wrote in message
news:842606F9-73BB-4638-B332-(E-Mail Removed)...
>
>
> "Tatar" wrote:
>
>> Windows XP Prof SP3
>> When I run disk cleanup it deletes around 36 system files, c_850.nls and
>> the
>> like. As a result windows does not boot up. It gives a file missing
>> warning.
>> I repeated this three times, last time selecting only temporary files to
>> be
>> deleted. Same keeps happening and I have to recover the system from the
>> image. Any help?
>>
>>
>>
> Since it does this each time you recover from the image, that means the
> image might be corrupt as well. Check your hard drive with scandisk /r and
> the hard drive maker's disk checking utilities to rule out problems with
> the
> drive. If the drive is good, put a fresh image on it and install CCleaner
> and
> see if it damages the install. If it doesn't, don't use Disk Cleanup
> anymore.
> If it does, you have either a good image of a bad install, or a bad image.

Yet another serious Disk Cleanup issue - The Winhelponline Blog:
http://www.winhelponline.com/blog/ye...cleanup-issue/

--
Regards,

Ramesh Srinivasan, Microsoft MVP [Windows Shell/User]
The Winhelponline Blog http://www.winhelponline.com/blog


"Tatar" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Thanks DL and Mark. I have run sfc /scannow a few times and all is well.
>
> "Mark Adams" <(E-Mail Removed)> wrote in message
> news:842606F9-73BB-4638-B332-(E-Mail Removed)...
>>
>>
>> "Tatar" wrote:
>>
>>> Windows XP Prof SP3
>>> When I run disk cleanup it deletes around 36 system files, c_850.nls and
>>> the
>>> like. As a result windows does not boot up. It gives a file missing
>>> warning.
>>> I repeated this three times, last time selecting only temporary files to
>>> be
>>> deleted. Same keeps happening and I have to recover the system from the
>>> image. Any help?
>>>
>>>
>>>
>> Since it does this each time you recover from the image, that means the
>> image might be corrupt as well. Check your hard drive with scandisk /r
>> and
>> the hard drive maker's disk checking utilities to rule out problems with
>> the
>> drive. If the drive is good, put a fresh image on it and install CCleaner
>> and
>> see if it damages the install. If it doesn't, don't use Disk Cleanup
>> anymore.
>> If it does, you have either a good image of a bad install, or a bad
>> image.
>
>