Jump to content

Win 7 inplace upgrade as non-destructive repair ???


glnz

Recommended Posts

I've been bugging MS to help me with a problem doing a 100% clean Reinstall of Office 365 Home 64-bit on my Win 7 Pro 64-bit PC.  Each Reinstall of O365 creates 70± Warning messages in Event Viewer that certain registry keys are protected and cannot be modified by Office 365 Click-to-Run.  (O365 actually works fine so far - I just don't like those Warning messages and want to Reinstall without them.)

The MS O365 help line tech 2 level person accessed my PC and showed me how my further Event Viewer error messages show errors with ntdll.dll and kernelbase.dll.  He says the only way we can fix the problem with Reinstall of Office 365 Home 64-bit is to repair those dll's in my Win 7 Pro 64-bit OS, and the only way to do that in a non-destructive fashion is to do an "inplace upgrade" of my Win 7 off the .iso image of Win 7 Pro 64-bit.

What do you think?

First, please see the very interesting article about non-destructive repair using inplace upgrade at
http://mcs-notes1.open.ac.uk:8080/tbtknowl.nsf/0e36766f24334c4c80256554005a57dc/8779f10d83d5276e8025794400355753?OpenDocument 
(I have also attached that article to this post.)

Second, following the instructions of the MS tech 2, I am downloading an .iso of Win 7 Pro 64-bit from  http://91.121.154.109/Windows 7/Eng/ .   Do you like that source? 
The .iso I am downloading is called en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso.  I see that the file's date is August of 2015 (last year), so that means I'll have to do a lot of Windows Updates afterwards (and carefully so as to avoid the updates that install the Win 10 "spy" features)?  Do you think there are better .iso sources for the install, maybe already updated?  The

Third, he also showed me the normal MS Windows .iso download page https://www.microsoft.com/en-in/software-download/windows7 , but when I inserted my perfectly good Key for my Win 7 at the bottom of that page, it did NOT verify.  He said that MS's verification server is down, and has been down for some days.  (Really?)  I know my key is good because I used it for a re-install of the OS almost two years ago on this PC.

Fourth, my PC is actually dual-boot Win 7 Pro SP1 64-bit and Win 10 Pro 64-bit.  (FYI - I have separate keys/licenses for each - the 10 is NOT an upgrade of the 7.)  Do you think the non-destructive repair of Win 7 using inplace upgrade will wipe out the 10?  I think I'm OK because I did a destructive 7 repair about 1½ years ago, and that did not wipe out the other OS (which was then 8.1, since changed to 10).  But is there anything special I should do to preserve the 10?

Fifth - reminder that my core problem isn't with the OS, which seems to be 100% fine.  It's only that I am getting 70+ Warning messages about non-modifiable registry keys whenever I reinstall my O365 Home 64-bit.

Hey, what do you think????   Easy, huh?

Thanks.

Win 7 non-destructive reinstall instructions.htm

Link to comment
Share on other sites


It should be OK, BUT (you never know) check the hash(es) of the downloaded .iso:
en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso    aka X17-59186.iso should be:
MD5: ed15956fe33c13642a6d2cb2c7aa9749

SHA1: 0bcfc54019ea175b1ee51f6d2b207a3d14dd2b58

In any case, ignore the date you see, that should be a "standard" iso as it was available on Digital River (or on MSDN or Technet) with just SP1 integrated.

See also:
https://www.reddit.com/r/windows/comments/4xlzuq/is_this_a_legitimate_link_for_windows_7/

jaclaz
 

Link to comment
Share on other sites

jaclaz - many thanks.  Two Qs:

1)     I think I saw on this forum guidance about downloading a "technical" copy of the Win 7 Pro 64-bit .iso and pointing to it when doing a scannow or some other file-repairing cmd command.  Do you recall that, or can you give me the link?

        I remember it only worked with the right "technical" and not "other-typical" download.  (Or am I confusing this with Win 10?)

2)     The SHA1 code matches, but how do I check the MD5?

Thanks.

Edited by glnz
Link to comment
Share on other sites

If SHA1 matches it is fine.

Both MD5 and SHA1 were provided as - while most hashing tools compute BOTH MD5 and SHA1 - some will only compute MD5 or only SHA1.

Cannot say about the other question, I don't recall any particular "technical" version, AFAIK they are all the same.

jaclaz


 


 

 
 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...