Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 5 subscribers
  • Views 15640 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Corrupt local cache cannont be fixed

Cannonfodder

I tried to install SafeGuard 6.1 client software – like I did several times before - on a HP Elitebook 840 with W7x64 Enterprise on a M.2 SSD (disk/bus 1), there also is a 500 GB eSata Disk in it (disk/bus 0).

After installing and reboot the white POA screen appeared and then tried to load Windows but failed and got stuck.

So I tried out MBR & boot fix, the rollback tool, Windows system repair and at least I managed to kill and repair the bootloader, so Windows is now booting again, without troubles (and of course without POA).

Only thing is: I got a corrupted local cache, which I cannot fix and so cannot repair/uninstall SG and on serverside the errors because of missing the SGN Kernel.

Is there any way to avoid a new setup of the whole system and repair the installation or get rid of it (except „search & destroy“ all reg-entries ;)

Thank you in advance!

Kind regards,

Hans

:55314


This thread was automatically locked due to age.
Parents
  • 0

    That works fine as long as you do nothing else in between, what I did for several reasons.

    So, if the local cache is damaged (and, as it was in my case, the backup folder is empty), you got stuck?!

    And can the problem be caused by saying Windows to autologon a special user, so that when SafeGuard tries to "Autologon" after first installation it runs into troubles? Or do you think it was depending on the M2 SSD? (I know, it's a little bit like crystal ball telling, but maybe you already had some experiences on that and can suspect one of the two alternatives more likely ;)

    Best regards,

    Hans

    :55396
Reply
  • 0

    That works fine as long as you do nothing else in between, what I did for several reasons.

    So, if the local cache is damaged (and, as it was in my case, the backup folder is empty), you got stuck?!

    And can the problem be caused by saying Windows to autologon a special user, so that when SafeGuard tries to "Autologon" after first installation it runs into troubles? Or do you think it was depending on the M2 SSD? (I know, it's a little bit like crystal ball telling, but maybe you already had some experiences on that and can suspect one of the two alternatives more likely ;)

    Best regards,

    Hans

    :55396
Children
No Data
Unfiltered HTML