Windows 10: my windows 10 drive is corrupt after i booted from a windows 7 drive, startup repair starts...

hello,


a while ago I had to find a file on a different drive then that was in my computer. so a put it in and and booted up the OS that was on it, windows 7. for some reason it started up disk repair even though it worked just fine in my laptop (wich broke thus i had removed the drive). but otherwise all went fine. it booted and I got the file i need, and then I shut down to boot from the windows 10 drive.


thats when things went downhill, it couldn't boot for some reason. I don't exactly remember what it said, but I thought it might be fixed if I would remove the windows 7 drive. it did not. so I thought startup repair would do the job. but even that didnt work. in fact, I noticed it starts a windows 7 startup repair, I do have an older installation of windows 7 on that drive, but I don't think that should matter, its all under a windows.old folder.


i am at loss and have no idea how to fix this without having to completely reinstall. any help would be appreciated.


Erik

:)

 

Windows 7 booting off wrong drive?!?!?

Please move if this is in the wrong place.

I have two hard drives, a 1.5TB drive, and a 160GB drive. Windows is installed on the 1.5TB drive, as are all my files and programs. The 160GB drive has a bunch of old files, and apparently the bootmgr and boot folder. Nothing else is on the 160GB drive, other than media files etc.

If I remove the 160GB drive from the machine, windows refuses to boot, plug it back in, it works fine. The setup with two hard drives I have now is temporary, as the 160GB drive will go into another machine.

My question is, can someone give me a step by step on how to make windows force to boot off the 1.5TB drive, ignoring the 160GB drive in the boot process completely?
I don't know how to do this in Windows 7, on XP I would just run the /fixmbr command and its related ones.

Any help would be appreciated.

Note: I would really really rather not have to wipe and reinstall, I know it can be done without one as I've had this issue with XP before.

 

Windows 10 boot drive

Is Windows 10 also limited to a max of 3Tb for a boot drive?

 

Repair Windows 7/8/10

Repairing Windows 7

Methods of advanced CLI repair were introduced with Windows 7 and Server 2008 that can allow sysadmins and end-users to attempt to resolve issues without wiping their hard drive, re-installing and either losing or restoring data.

I will list the important repair processes I use in the field, at my bench, remotely, for family, etc. that have allowed me to keep a current Windows 7 system deployed and running smooth. Keep in mind this is not a cure-all, some issues will require what is called an in-place upgrade. In more severe cases, a system re-install may still be required. For many it is worth the time to try and avoid that process and I am hopeful that some of you will be saved that hassle with this part of the guide!

If you're having issues with Windows 7, hopefully the below repair instructions will help you confirm OS file corruption and help resolve it.

Spoiler: Windows 7 Repair In-Place Upgrade

If CHKDSK and SFC fail to repair the issues with the system, then the next option is to perform an in-place upgrade. This is comparable to an Operating System Refresh in Windows 8/8.1 and 10. In that it re-installs most of the operating system's files without losing your profiles, data or programs. In many cases this process accomplishes just that.

Time to close the CLI windows and get back into the GUI, unless you want to deploy Windows through CLI. You'll have to source a different guide for that process!

Requirements to perform a Windows 7 and Server 2008 in-place upgrade:

• Must have installation media that matches the installed OS version and type. You can download that media click here.
• Must be able to get to the desktop on the affected system to correctly initiate this process, booting to the media will not allow an upgrade to be performed.

That last rule is the frustrating part of this repair process if you cannot get that far, backup what you can and do a fresh installation. Otherwise proceed.

• Start the process by using autorun or manually running setup.exe from the installation media.
• You'll come to the installation window, the options will be Upgrade or Custom. Choose Upgrade. This is critical as choosing custom will force you to overwrite, append or wipe out the current install rather than performing any kind of repair.
• Follow the on-screen prompts, which should be very few for you to interact with. The overall process looks and is the Windows 7 install GUI. Once it is completed, the system will automatically reboot (may need to more than once).
• After the reboot(s) after the in-place upgrade you should have a fully functional Windows 7 without issues or corruptions.

Performing an in-place upgrade makes sense, and gives you a stable and clean running operating system when there's an issue or corruption you just can't fix but things aren't broken enough to warrant a fresh installation. The point of this process is to refresh the Windows 7 OS files but retain your data, programs, and settings. That is precisely what the in-place upgrade procedure accomplishes.

I should also add that this process can be accomplished remotely as well, from start to finish. I have done so with persistent LogMeIn, ScreenConnect and Teamviewer installations on various remote systems I have performed this task on, RDP should work as well. Being able to do this level of repair remotely is a huge benefit to any sysadmins out there looking to keep a client happy and perform that "remote magic" IT guys are known for.

**If at this point your issues are not fixed, then there is something else occurring that is causing the issue be it Malware, hardware, drivers, etc. Please refer to the OP in this thread to run through some of those tests and diagnostics, or create a new thread seeking help and stating what you've tried.**
Spoiler: Update Windows 7 Successfully Update Windows 7 Successfully

Many of us have or will run into it, the endless hours of waiting for the Windows Update process to actually update or fail trying to update a Windows 7 install. Could be a fresh install, or a years-old install. This will eventually happen to you, unless you run a WSUS server, and even then the OS can get held up. Microsoft has been changing how all supported versions of Windows update, trending towards the cumulative monthly releases. This transition seems to be one of the tipping points on the matter.

Regardless, there are some excellent solutions available to help you keep up your Windows 7 installation.

• Solaris17's Windows Update Utility
  • Recommended method for most users that simply want their Windows 7 installation updated. Run as admin, follow directions, be patient.
  • Please comment in that thread if you need assistance or run into issues. Solaris has made many useful changes and revisions due to good feedback.
• Update Windows 7 Manually
  • Manually perform the tasks that Solaris's utility does if you prefer.
• Update Windows 7 Manually
  • Another source.
• Update Windows 7 Manually
  • One last source for good measure!
• Windows 7 Refreshed Media Creation
  • Creating a Windows Image file (WIM) that contains the necessary updates can make future deployments boatloads easier. This is well worth a read for the more technical types and sys admins.

Those links should provide you with some very useful ways to handle updating Windows 7. If you run into any issues updating Windows 7, please start a thread or post in a relevant linked thread if its kept current.