Main Forum > General Computer Support

System Protection - error 0x80070005

(1/3) > >>

Clade:
Good morning everyone!

Remembering that my language is not English. . . which may hinder a little communication.

Dell Inspiron N4050, Windows 7-64, Home basic.

Initially "C" (system), increased from one moment to another, the volume.

Observed that it was one of the restore points, which used no less than 30 GB, only he, and all together, used 90 GB. After that point and excluded from some other "C" has returned to normal.

Observed protection system that it found itself changed, using configuration, approximately 98 GB, because usually, I leave an 8 GB for restore points.

The system creates the restore point, changes the amount of GB available, but when I try to use the "apply", have the following information:

"Could not create the scheduled task for the following reason: Access is denied 0x80070005" and unexpected error in the property page

Deactivating and reactivating system protection, same error. Make changes, but it has this error.

Used Combofix, Malwaribytes and other good scanners but nothing relevant was found. . . imaginos then it is not difficult for malware.

Was also used SFC, CHKDSK C: f / r /.

Please positioning.

Clade:
Complementing information.

Roguekiller found Pum. policies (attached)

The equipment gives the normal boot, but looking msconfig, "System Startup" tab, I have no access to system startup does not have access to any of the options. (attached)

In the "General" tab, access the options is normal, but in an attempt to "apply" has the following information:. "System configuration can not save the original boot configuration for later restoration Changes in The startup will be reversed. device is not ready "

Boggin:
If the actions of this PUM are recent, boot up into Safe Mode and try your restore points to prior the infection.

Clade:
There are no restore points, only one, created as a test, when equipment has had difficulty.

Nor is it incompatible antivirus, uninstalled it and nothing has changed.

Shane:
First thing to do is to check the drive for bad sectors. Always the first thing because sometimes it is the cause and not an infection. Then if the drive is good then try running my windows repair and run all the repairs.

To do a bad sector check open a cmd.exe window and put in
chkdsk c: /r

It way say the drive is in use and would you like to schedule it for next boot, hit Y

Now reboot and it should do the scan, it will take a while. You can see the results in the event viewer afterwards. If the drive is good then try my WR and let me know how it goes :wink:

Shane

Navigation

[0] Message Index

[#] Next page