Results 1 to 3 of 3

Thread: Prob. with Norton GoBack & boot error

  1. #1
    A shadowy flight. MSIC's Avatar
    Join Date
    Oct 2005
    Location
    London/Herts
    Posts
    3,413
    Thanks
    394
    Thanked
    229 times in 168 posts
    • MSIC's system
      • Motherboard:
      • ASRock H170M-ITX
      • CPU:
      • Core i5 6500
      • Memory:
      • 2 x 4GB Corsair Veng DDR4 2666
      • Storage:
      • 240GB SSD (boot) +1TB Samsung F3
      • Graphics card(s):
      • ASUS GeForce 750Ti
      • PSU:
      • Silverstone 450W ST455F
      • Case:
      • Silverstone SG06-450
      • Operating System:
      • Win10
      • Monitor(s):
      • Dell S2309W
      • Internet:
      • PlusNet FiberTTC

    Prob. with Norton GoBack & boot error

    Wondered if anyone might offer a little tech support please?
    A mate at work asked me to look at his PC as it wasnt booting up any more. Its a P4 Dell (no longer in warranty) with WinXP Home (dont know if SP1 or 2) which he'd stuck Norton GoBack on.
    His son has been turning the PC on and off at the wall (but not going through Start -> shutdown) and there has now developed an error in the boot process. I have tried my basic abilities to repair via the WinXP install disc, to no avail.
    When i add the hard drive to my own PC it doesnt mount in windows, and Partition Manager shows a "Type 44" partition (after a 7MB first partition) which google shows to be related to GoBack. It also means the data on it is not accessible to me.

    I seem to be a catch 22 - i can only access the data by booting from the hard drive, but the boot process is knackered. My friend does not want me to format the drive yet as he hasnt backed up important data

    Any ideas? I dont have the original GoBack disc (but can probably get it) and wondered if I could boot off that?

    Cheers in advance
    I'm commenting on an internet forum. Your facts hold no sway over me.
    - Another poster, from another forum.

    System as shown, plus: Microsoft Wireless mobile 4000 mouse and Logitech Illuminated keyboard.
    Sennheiser RS160 wireless headphones. Creative Gigaworks T40 SII. My wife.
    My Hexus Trust

  2. #2
    A shadowy flight. MSIC's Avatar
    Join Date
    Oct 2005
    Location
    London/Herts
    Posts
    3,413
    Thanks
    394
    Thanked
    229 times in 168 posts
    • MSIC's system
      • Motherboard:
      • ASRock H170M-ITX
      • CPU:
      • Core i5 6500
      • Memory:
      • 2 x 4GB Corsair Veng DDR4 2666
      • Storage:
      • 240GB SSD (boot) +1TB Samsung F3
      • Graphics card(s):
      • ASUS GeForce 750Ti
      • PSU:
      • Silverstone 450W ST455F
      • Case:
      • Silverstone SG06-450
      • Operating System:
      • Win10
      • Monitor(s):
      • Dell S2309W
      • Internet:
      • PlusNet FiberTTC
    Just to finish this thread in case anyone in the future does a search, it is sorted.
    Symantec has in their support area a downloadable ISO that you can boot from and disable Norton GoBack. From that point I was able to fix the windows installation and get it all working again.
    Bloody symantec - they are getting as bad as McAffee wanting to control your whole system.
    I'm commenting on an internet forum. Your facts hold no sway over me.
    - Another poster, from another forum.

    System as shown, plus: Microsoft Wireless mobile 4000 mouse and Logitech Illuminated keyboard.
    Sennheiser RS160 wireless headphones. Creative Gigaworks T40 SII. My wife.
    My Hexus Trust

  3. #3
    Registered User
    Join Date
    Jul 2007
    Posts
    1
    Thanks
    0
    Thanked
    0 times in 0 posts
    GoBack has a lot of install problems. A pity, because it works better than System Restore in that it EXACTLY restores to a former state - then gives you the option to retain critical files changed in the interim.
    Here's what to do if you have problems installing or reinstalling Goback (and SystemWorks 2006 Premier)
    1) Use the Norton Removal tool to remove traces of previous Norton stuff (You can download it from Symantec)
    2) Delete the Symantec Shared folder from Program Files/ Common Files
    3) Reinstall SystemWorks.
    If you get the blue screen of death and "Session Manager Init System process terminated" you should reboot and hit the spacebar on the GoBack splash screen. Then choose the option to disable GoBack. Alternatively, press CTRL ALT G repeatedly throughout bootup and choose option F to delete GoBack.
    If you get into a reboot loop at the User logon screen of Win XP, you can get out of this by rebooting in safe mode (F8) and going to Services in Settings - Control Panel - Admin Tools. Then right click on various Norton and Symantec Services to bring up their properties and set any that are automatic to "manual" (Specifically, the services most likely to be causing problems are Symantec Event Manager and Symantec Settings Manager - the others can usually stay "automatic"). Then restart and you should boot up normally.
    After all this, can you reinstall SystemWorks 2006 Premier in such a way that all functions work? I'm afraid I still haven't cracked that one!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Windows - boot process & simple troubleshooting
    By Paul Adams in forum Software
    Replies: 30
    Last Post: 17-11-2010, 04:38 AM
  2. Windows - a brief guide inside
    By Paul Adams in forum Software
    Replies: 31
    Last Post: 23-06-2007, 03:14 PM
  3. Weird boot error beep code.
    By black_knight in forum Help! Quick Relief From Tech Headaches
    Replies: 0
    Last Post: 24-06-2005, 11:25 AM
  4. Error in CLI.exe on Windows boot
    By Ruggerbugger in forum Software
    Replies: 10
    Last Post: 11-03-2005, 08:17 PM
  5. 8o!! taste hot WineX powaaah!
    By directhex in forum Software
    Replies: 33
    Last Post: 31-05-2004, 08:18 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •