Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

Error 0x80070005


  • Please log in to reply

#1
Janis

Janis

    Member

  • Member
  • PipPipPip
  • 333 posts

My pc has been very problematic so I thought I'd do a windows restore.  I get an error message that restore can't complete  The number shown seems to point to an update issue    error number listed was 0x8007005.   Is there a fix for this?


  • 0

Advertisements


#2
SpywareDr

SpywareDr

    Member 3k

  • Member
  • PipPipPipPipPipPip
  • 3,996 posts

https://answers.micr...86-1dde915125cf

 

?


  • 0

#3
Janis

Janis

    Member

  • Topic Starter
  • Member
  • PipPipPip
  • 333 posts

Thanks much, hope it works for me


  • 0

#4
SpywareDr

SpywareDr

    Member 3k

  • Member
  • PipPipPipPipPipPip
  • 3,996 posts

<fingers-crossed> Let us know ...


  • 0

#5
raburgeson

raburgeson

    New Member

  • Member
  • Pip
  • 7 posts

I have been running my machine for 2 years now with that error. Microsoft has a patch and direction for it's use. On the other hand it's for all the operating systems. That made me curious. I used a small program call take ownership and used the supplied information to go to the file and take ownership. After reading I decided that file is a back door no matter if it was intended that way or not. Relax, the computer will run just fine if you do nothing. Half of Windows is bloatware. I have considered deleting the file completely. As it is not a problem I haven't done that yet so I do not know if there are any consequences if that is done.

 

If done Security side is anyone can have administrative rights. Operating side is older drivers can be installed if the pathways are closed correctly and you will get no messages like certificate is unsigned. Think this whole thing started when they included the MSI installer update for Windows XP. I personally do not like to see generic addresses which is an immediate security risk. Kind of like when ATAPI was the address of the cd/dvd drive was MSCDEX that did get exploited. Don't freak, how does the computer act unfixed.


Edited by raburgeson, 29 August 2019 - 01:25 PM.

  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP