Error 1935 - Saved by a backup image, again

Discussion in 'backup, imaging & disk mgmt' started by Robin A., Apr 4, 2011.

Thread Status:
Not open for further replies.
  1. Robin A.

    Robin A. Registered Member

    Joined:
    Feb 25, 2006
    Posts:
    2,284
    Last weekend I decided to try and “feel” Office 2010. 2007 is getting old, and I have never really liked the 2007 ribbon - - it seems that it has been improved in 2010.

    The 2010 installation stopped with the 1935 (0x800736B3) error, and rolled back. I tried several times, always with the same result.

    I searched for “1935 error + Office 2010” and found several “solutions”, including some by MS. I wasted some time (about 3 hours, I guess) trying several of them:

    - Run the malware scanners. Nothing found (except the Chrome cookies reported by SUPER).

    - Install 2010 with different options, or uninstall 2007 before, or install as Administrator. All failed.

    - Disable all real-time security software before installing, except, of course, MSE. In my case, this only applies to WinPatrol. I stopped it and ran the installer – same error.

    - Run sfc /scannow. It found system errors, but could not repair them. Created a log, but I wasn´t able to open it (so what is it for?).

    - Repair .NET FW. It seems that it can´t be done in Windows 7, and anyway I don´t like the idea of replacing some Windows files with older versions.

    Finally, I restored a system image created on March 9 (4:29 min. to restore). The whole Office 2010 package installed without any problem, and without uninstalling 2007.

    So, it seems that between March 9 and April 3, the system was subtly “corrupted”, I don´t know when or how. I will keep on creating system images.
     
  2. napoleon1815

    napoleon1815 Registered Member

    Joined:
    Sep 9, 2010
    Posts:
    702
    Sorry to hear, but glad you had an image. What imaging software did you use? Just curious. Thanks.
     
  3. Robin A.

    Robin A. Registered Member

    Joined:
    Feb 25, 2006
    Posts:
    2,284
    This image was created using ShadowProtect from a WinPE disk and saved to a USB 3.0 external hard disk. It was restored with the disk connected to an USB 3.0 port. I also use Paragon programs, currently Hard Disk Manager 2011, and occasionally the Windows 7 built-in program.

    I didn´t know in advance what image to restore, I just selected this one first because it was recent and included the SP1 Windows 7 update. I was lucky and it solved the Office 2010 install problem in the first try.

    This experience shows that one can create a supposedly clean image which in fact contains subtle problems that are not evident in normal use. Until these problems are detected and corrected, they will be present in all the subsequent images. If I had not tried to install Office, I would have created more images with the same problem.
     
  4. Osaban

    Osaban Registered Member

    Joined:
    Apr 11, 2005
    Posts:
    4,222
    Your experience shows that it is a good practice to keep several images stored, and contrary to common belief, one deals more often with various configuration mistakes, glitches, corruption than with malware.

    Out of curiosity, how fast was it restoring with USB 3.0 compared to the standard 2?
     
  5. Robin A.

    Robin A. Registered Member

    Joined:
    Feb 25, 2006
    Posts:
    2,284
    I don´t have the exact comparison for this restore. Based on previous experiences I would expect a 25% improvement in restore time with USB 3.0.
     
  6. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    8,648
    Location:
    NSW, Australia
    I don't have USB3 so I can't do the test. If I create/restore an image to a USB2 HD the transfer speed isn't maxed out. The limiting factor is how fast the internal HD can create the compressed image. So in my case I wouldn't expect USB3 to be any faster than USB2 in this situation.

    I'm not arguing with the file transfer speed being faster with USB3 compared with USB2.
     
Loading...
Thread Status:
Not open for further replies.