PC will not shut down

Topic

New Reply

I have detailed my attempts to dual-boot W7 and Mint Cinnamon in previous posts, but here is a recap:

Dell Inspiron 519 PC, originally came with Vista.  Several years ago, bought and installed a second hard drive programmed with W7 HP 64 bit (a legitimate copy).  Since Vista now no longer used, attempted to substitute Linux Mint Cinnamon 19.1, the most recent version, for the Vista OS.  Removed the Vista HD and installed a new blank HD, which I loaded with Mint via a download.  This went well, but then could no longer open W7.  BIOS still lists the W7 HD, seen on the boot options at startup, but will not boot to it, defaults to Mint.  At first, BIOS showed the W7 drive as “disabled” but now merely shows it, I can select it, but the PC defaults to Mint anyway.

Previous advice here was that the Vista drive is needed to open W7.  Replaced the Vista HD and with that W7 booted as expected, much to my relief.  But the new pressing issue is that W7 will not shut down, gets hung up on the “shutting down” screen.  A malware scan came back clean.  No idea how to retreat from this, so shut down with the power button.  Vista still shuts down correctly.

Previous advice centered on repairing the bootloader (with some variations) as I thought I did not have the W7 installation disc.  Turns out I do in fact have it, apparently sent with that W7 HD and forgotten in a drawer- perhaps this changes the picture.  So, my question- what should I do next?

Reply | Quote

Replies

How long have you given the Windows 7 time to attempt a complete shutdown?

You need to check that Windows 7’s file system as there are likely some soft errors which there is need to test and fix because of the forced power down.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

I think it is related to power, check your energy settings

also I would look at possible services that crashes when shutting down, I would check event viewer

Just someone who don't want Windows to mess with its computer.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

anonymous wrote:

How long have you given the Windows 7 time to attempt a complete shutdown? You need to check that Windows 7’s file system as there are likely some soft errors which there is need to test and fix because of the forced power down.

about an hour

Reply | Quote

Zaphyrus wrote:

I think it is related to power, check your energy settings also I would look at possible services that crashes when shutting down, I would check event viewer

Note that this is a PC, not laptop.  Event viewer shows 6,600 errors.  What’s next?

Reply | Quote

The event viewer sections Application and System will be the best place to look for critical errors. You can group these errors together by clicking on Level. If your remember the approximate time that you forced that last shutdown there might be one there, there is no guarantee anything causing the fault was saved in an event log file.

You can search for the Event code with a preferred search engine to possibly gain some amount of understanding of it:

Kernel event 219 is a plug and play driver error.

Kernel event 3 is an error related to event tracing and log files.
—
If you see Kernel with Event 41 it is a power problem, this article expounds a bit upon the subject. Joe’s recommendation about running the Power Troubleshooter is good advice.

2 users thanked author for this post.

Zaphyrus, Slowpoke47

Reply | Quote

Have you run the Power troubleshooter?

Have you checked the event logs?

--Joe

1 user thanked author for this post.

Slowpoke47

Reply | Quote

joep517 wrote:

Have you run the Power troubleshooter? Have you checked the event logs?

This is a PC, not a laptop.  See s/shot above.  No idea what to do with this info.

Reply | Quote

This link may help you with your 7000 & 7009 events.

Complete the steps in Method 2 and Method 3.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

You can still run the power troubleshooter.

You can look at individual events which are errors around the time you began the shutdown.

--Joe

2 users thanked author for this post.

Ascaris, Slowpoke47

Reply | Quote

Since my Mint installation and Vista removal, W7 now has 6,600 errors (!) With the Vista HD removed from the machine, the W7 drive will not boot. It turns out I do have the W7 installation disc, buried in a drawer, now in hand.

If I reinstall the W7 OS without the Vista drive connected, maybe I’ll get a fresh start with 7, including bootloader and proper shutdown sequence. But if I do that, what happens to the added programs and local files, i.e. data?

 

Edit- removed “shutdown”- 6,600 errors, not shutdown errors.

Reply | Quote

Checkout EasyBCD for your boot issues before you go the reinstall route. You’ll have a boatload of patches to install if you start from scratch.

--Joe

1 user thanked author for this post.

Slowpoke47

Reply | Quote

joep517 wrote:

Checkout EasyBCD for your boot issues before you go the reinstall route. You’ll have a boatload of patches to install if you start from scratch.

As of now, with the Vista and W7 HD’s installed, the PC boots as always with the choice of OS at bootup.  If I do a system restore to before the Mint HD went in, maybe that would fix the shutdown issue for W7.

That would still leave me with the no-start problem with W7 and Mint installed, but the no-shutdown takes precedence- one fix at a time.

Reply | Quote

Mint installation was 3/1.  No Windows backups installed since then, but some personal files have been altered.  If I do a system restore, those changes would be lost, but no data has been changed since the last weekly backup, yesterday.  If I understand correctly, I can bring those files current using my backup disc.  Is this correct?

Reply | Quote

As far as putting the bootloader on the Win 7 drive: The discovery of the Windows disc doesn’t change anything as far as my suggestions.  Since you have it handy, it would certainly be worth a try to boot it and see if it will be able to repair it, but my guess is that it will tell you that it was not able to repair Windows (based on my recent experience with the Windows 10 install USB trying to place a bootloader on my Acer Swift’s drive).  This is essentially the same thing as following the above advice about creating a recovery disc… if the Windows disc cannot repair Windows, there’s no point to creating the recovery disc, as it will just try the same things.

I’d install Macrium Reflect Free edition and have it create a USB or disc bootable, then boot that and select “Fix Windows boot issues.”  It should find both Windows installations, so select 7, of course, and then select the Windows 7 drive for the place to install the bootloader.  It should show that it failed on the step to remove the old bootloader, which is expected, since it’s not there.  The rest of the steps should show as succeeded, and after that it will ask to reboot, so select yes, then go to Mint and enter the sudo update-grub command again.  After the next reboot, it should show two Windows boot manager entries.  At that point you can try removing the Vista drive again, and 7 should still boot fine after that.

As far as the shutdown issue… Other people have suggested looking in the event viewer, and that’ what I would suggest too.  It may take a good amount of drilling down through the messages and seeing what the actual text is for each one.  One thing I do sometimes is wait for an even number on the system clock and shut it down right then, so you know which log events took place immediately following the shutdown.

You might also want to give the Windows disks an error check for good measure.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Ascaris wrote:

As far as putting the bootloader on the Win 7 drive: The discovery of the Windows disc doesn’t change anything as far as my suggestions. Since you have it handy, it would certainly be worth a try to boot it and see if it will be able to repair it, but my guess is that it will tell you that it was not able to repair Windows (based on my recent experience with the Windows 10 install USB trying to place a bootloader on my Acer Swift’s drive). This is essentially the same thing as following the above advice about creating a recovery disc… if the Windows disc cannot repair Windows, there’s no point to creating the recovery disc, as it will just try the same things. I’d install Macrium Reflect Free edition and have it create a USB or disc bootable, then boot that and select “Fix Windows boot issues.” It should find both Windows installations, so select 7, of course, and then select the Windows 7 drive for the place to install the bootloader. It should show that it failed on the step to remove the old bootloader, which is expected, since it’s not there. The rest of the steps should show as succeeded, and after that it will ask to reboot, so select yes, then go to Mint and enter the sudo update-grub command again. After the next reboot, it should show two Windows boot manager entries. At that point you can try removing the Vista drive again, and 7 should still boot fine after that. As far as the shutdown issue… Other people have suggested looking in the event viewer, and that’ what I would suggest too. It may take a good amount of drilling down through the messages and seeing what the actual text is for each one. One thing I do sometimes is wait for an even number on the system clock and shut it down right then, so you know which log events took place immediately following the shutdown. You might also want to give the Windows disks an error check for good measure.

PLease see my post, time stamped the same as yours.  Can you comment on that strategy as the first move?

Reply | Quote

Sure!

I’m not really sure what you mean by changes to personal files being lost but no data having changed.  What personal files do you mean?  I usually see the term ‘personal files’ used in a way that is synonymous with data files, which are not normally rolled back by System Restore.

System restore is meant to preserve that kind of personal files, but it’s always a good idea to back up the files you don’t want to lose before doing any repair procedures.  Anything worth keeping is worth backing up!

You can try performing a system restore to see if it fixes the shutdown issue.  You may want to have it scan for changes and report them to you first, and then don’t do it just yet… the list of things it comes up with may contain the source of the shutdown hang.  Maybe you installed something that you could uninstall and see if that helps.

If that proves unhelpful, then you can perform the restore and see how it goes.  I’m kind of a backup fanatic, so I’d image the Windows drive in question first, just in case the restore process messes something up.  It shouldn’t, but you just never know about these things.

If it was working fine before, the only thing hardware-wise that will have changed is the addition of the Linux drive, and that certainly shouldn’t have any bearing on Windows, so the idea of going back to when it was working fine isn’t a bad one.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Ascaris wrote:

Sure! I’m not really sure what you mean by changes to personal files being lost but no data having changed. What personal files do you mean? I usually see the term ‘personal files’ used in a way that is synonymous with data files, which are not normally rolled back by System Restore. System restore is meant to preserve that kind of personal files, but it’s always a good idea to back up the files you don’t want to lose before doing any repair procedures. Anything worth keeping is worth backing up! You can try performing a system restore to see if it fixes the shutdown issue. You may want to have it scan for changes and report them to you first, and then don’t do it just yet… the list of things it comes up with may contain the source of the shutdown hang. Maybe you installed something that you could uninstall and see if that helps. If that proves unhelpful, then you can perform the restore and see how it goes. I’m kind of a backup fanatic, so I’d image the Windows drive in question first, just in case the restore process messes something up. It shouldn’t, but you just never know about these things. If it was working fine before, the only thing hardware-wise that will have changed is the addition of the Linux drive, and that certainly shouldn’t have any bearing on Windows, so the idea of going back to when it was working fine isn’t a bad one.

Thanks for your time and effort.  The deeper this goes, the more my comfort level and confidence sinks.  I tried to do a system image with Macrium, trial period still ongoing, but I failed at it for some reason.  My thought is to try something within my comfort level if possible.  The data I’m referring to is in fact personal files.  What I said was that, although some data was altered after the Mint install on 3/1, nothing has changed since yesterday’s backup, so if I do the system restore, I can bring those personal files up to date using yesterday’s backup.  Depending on the outcome, I can, with help, address the rest of the mess I made.

Reply | Quote

I don’t know if there is anything within your comfort zone that will put a bootloader on the Win 7 disk.  It’s a somewhat advanced thing, but then so is installing Linux– and that bit went pretty easily!

I’m not suggesting Reflect for backups at this point, though, but to make a USB or disc that you can use to boot and select “Fix Windows boot problems.”

It would be good to use Reflect or something else to begin a backup regime, but for now, the purpose is to create the bootloader.

If the personal files are data files like text documents, PDFs, images, spreadsheets, videos, audio files, or stuff like that, System Restore should not have any effect upon it.  System restore will roll back changes to system configuration files and executable or system files (.exe, .dll, and a bunch of others like that).  It’s still good to back them up first.  That doesn’t mean you need Reflect or anything like that– it could be as simple as copying them to a USB thumb drive and setting that aside until this is all done.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

I hope this is not too late, but I will try to post this before you move forward–

What’s the Rush?

It sounds like the only problem you have right now is a stuck shut down–and you have a usable work around of holding down the power button.

You posted in your previous thread that your primary need was to able to boot Win7. Now, it’s I have to be able to shut down in a *normal* fashion.

You are at risk of loosing all ability to boot Win7! Don’t do that until you have a better understanding of what you’re doing, the risk(s) involved, and a backup plan B available should thing go very wrong.

I don’t think you are properly prepared yet to recover from a major problem of either entering a wrong command, or having the software do something wrong!

Take a deep breath, hang on for awhile, let’s try other solutions that may be less drastic first …

2 users thanked author for this post.

Ascaris, Slowpoke47

Reply | Quote

Continually using the power switch in this manner will only aggravate the risk of file system corruption. Delaying this repair is not addressing the situation!

Reply | Quote

Just Lurking wrote:

@ Slowpoke47 I hope this is not too late, but I will try to post this before you move forward– What’s the Rush? It sounds like the only problem you have right now is a stuck shut down–and you have a usable work around of holding down the power button. You posted in your previous thread that your primary need was to able to boot Win7. Now, it’s I have to be able to shut down in a *normal* fashion. You are at risk of loosing all ability to boot Win7! Don’t do that until you have a better understanding of what you’re doing, the risk(s) involved, and a backup plan B available should thing go very wrong. I don’t think you are properly prepared yet to recover from a major problem of either entering a wrong command, or having the software do something wrong! Take a deep breath, hang on for awhile, let’s try other solutions that may be less drastic first …

Thanks for your input.  My thought is to go one step at a time.  If I restore the system to before the Mint install, on 3/1, I hope to fix the shutdown issue.  My weekly backup completed yesterday and no files have been changed since then.  I expect that, after SR, I can update any changes to personal files using that backup.  Once that happens successfully, I’m made whole to before the Mint.

That’s when I need to make a plan going forward, hopefully with guidance, and then there’s no rush.  The concern now is that I’ve been repeatedly warned that shutting down via the power button is dangerous, sooner or later.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Previous advice here was that the Vista drive is needed to open W7. Replaced the Vista HD and with that W7 booted as expected, much to my relief. But the new pressing issue is that W7 will not shut down, gets hung up on the “shutting down” screen.

*NOT A PRESSING ISSUE*! An aggravation–yes. An annoyance–yes. Pressing–no! You can hold down the power button and you can successfully shut down Win7.

When did you put the Vista Harddrive (HDD) back in and determine that you could again successfully boot Win7?

After booting Win7 that first time after reinstalling the Vista HDD, did you experience that shut down problem on the very first shut down–or was it after a period of time and some successful shut downs before the problem occurred?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

I know that you have a Win 7 installation disk but that might be quite old.  The latest Win 7 iso that I recently downloaded from Microsoft totalled some 5.8MB, which means that you need a 8GB memory stick, but it appeared to have all but 19 updates already incorporated.  It took me just over 3 hours from start to finish and it fixed my chkdsk cross-linked file problem!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

Previous advice here was that the Vista drive is needed to open W7. Replaced the Vista HD and with that W7 booted as expected, much to my relief. But the new pressing issue is that W7 will not shut down, gets hung up on the “shutting down” screen.

*NOT A PRESSING ISSUE*! An aggravation–yes. An annoyance–yes. Pressing–no! You can hold down the power button and you can successfully shut down Win7. When did you put the Vista Harddrive (HDD) back in and determine that you could again successfully boot Win7? After booting Win7 that first time after reinstalling the Vista HDD, did you experience that shut down problem on the very first shut down–or was it after a period of time and some successful shut downs before the problem occurred?

The shutdown issue arose right away after Vista was reinstalled, about three days ago.

If there is no downside to shutting down via the button, we’ll do that until things are straightened out.  We’ve been using the “sleep” mode.

What would you suggest as the next step?

Reply | Quote

anonymous wrote:

I know that you have a Win 7 installation disk but that might be quite old. The latest Win 7 iso that I recently downloaded from Microsoft totalled some 5.8MB, which means that you need a 8GB memory stick, but it appeared to have all but 19 updates already incorporated. It took me just over 3 hours from start to finish and it fixed my chkdsk cross-linked file problem!

Good point- if it comes to a reinstall, I’ll get an updated W7 download.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

The concern now is that I’ve been repeatedly warned that shutting down via the power button is dangerous, sooner or later.

Have you been using the power button to shut down a lot in the past?

I do see what the concern is–if you force a shut down before Windows flushes it’s caches and writes necessary data to its open files, you could potentially corrupt a system file. But, if the system has in fact experienced a permanent freeze, then any data that has not already been saved is lost no matter what–holding down the power button or not.

When your Win7 system hangs during shut down–does the *activity* light on your tower show ongoing blinking indicating activity is occurring–or is it dark continuously? If it’s dark and showing no activity–it’s frozen and only the power button will recover from the problem. (This is where having a whole harddrive image backup can save you if some sort of permanent file corruption has occurred. Maybe the System Restore can do the same, but there’s no guarantee that the Restore Point has the system file available to restore–whereas an system image file would.)

As a first trouble shooting option, I would suggest that you boot to Safe Mode to see if that makes the problem go away. If it does, that indicates that it is probably some background service or software that’s disabled during Safe Mode that is the culprit, and we have a starting point to look for the problem.

Do you know how to enter Safe Mode? Here’s a link: https://support.eset.com/kb2268/?locale=en_US&viewlocale=en_US

Quoting:

Start Windows 7/Vista/XP in Safe Mode with Networking. Immediately after the computer is powered on or restarted (usually after you hear your computer beep), tap the F8 key in 1 second intervals. After your computer displays hardware information and runs a memory test, the Advanced Boot Options menu will appear.

Just the top option is fine–don’t need to select the *Safe Mode with Networking*, etc.

Does shut down occur okay now?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

The concern now is that I’ve been repeatedly warned that shutting down via the power button is dangerous, sooner or later.

Have you been using the power button to shut down a lot in the past? I do see what the concern is–if you force a shut down before Windows flushes it’s caches and writes necessary data to its open files, you could potentially corrupt a system file. But, if the system has in fact experienced a permanent freeze, then any data that has not already been saved is lost no matter what–holding down the power button or not. When your Win7 system hangs during shut down–does the *activity* light on your tower show ongoing blinking indicating activity is occurring–or is it dark continuously? If it’s dark and showing no activity–it’s frozen and only the power button will recover from the problem. (This is where having a whole harddrive image backup can save you if some sort of permanent file corruption has occurred. Maybe the System Restore can do the same, but there’s no guarantee that the Restore Point has the system file available to restore–whereas an system image file would.) As a first trouble shooting option, I would suggest that you boot to Safe Mode to see if that makes the problem go away. If it does, that indicates that it is probably some background service or software that’s disabled during Safe Mode that is the culprit, and we have a starting point to look for the problem. Do you know how to enter Safe Mode? Here’s a link: https://support.eset.com/kb2268/?locale=en_US&viewlocale=en_US Quoting:

Start Windows 7/Vista/XP in Safe Mode with Networking. Immediately after the computer is powered on or restarted (usually after you hear your computer beep), tap the F8 key in 1 second intervals. After your computer displays hardware information and runs a memory test, the Advanced Boot Options menu will appear.

Just the top option is fine–don’t need to select the *Safe Mode with Networking*, etc. Does shut down occur okay now?

We never used the power button to shut down, as we were cautioned against that, as mentioned.  I’ll have to try shutting down and watch the case lights.  Can’t recall what they did.  I’ll let the shutdown procedure go for some time before I use the button.  When I have the answer to your question, I’ll post back.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

If I restore the system to before the Mint install, on 3/1, I hope to fix the shutdown issue.

It might. And, it should not have any major ill side effect.

Slowpoke47 wrote:

My weekly backup completed yesterday and no files have been changed since then. I expect that, after SR, I can update any changes to personal files using that backup.

To be clear, I think you do not understand how System Restore functions. It only backs up System Files. None of your personal files will be included in a Restore Point. So, unless you are backing up System Files to your *weekly backup*, you will not have the ability to restore any System File corruptions from that *weekly backup*. And, after using a Restore Point, none of your personal files will be changed–so your *weekly backup* will not be needed to update your personal files.

After doing the System Restore, you can see if the shut down problem has changed.

I would still recommend doing the boot to Safe Mode, first, to see if that has any effect on the shut down problem.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

If I restore the system to before the Mint install, on 3/1, I hope to fix the shutdown issue.

It might. And, it should not have any major ill side effect.

Slowpoke47 wrote:

My weekly backup completed yesterday and no files have been changed since then. I expect that, after SR, I can update any changes to personal files using that backup.

To be clear, I think you do not understand how System Restore functions. It only backs up System Files. None of your personal files will be included in a Restore Point. So, unless you are backing up System Files to your *weekly backup*, you will not have the ability to restore any System File corruptions from that *weekly backup*. And, after using a Restore Point, none of your personal files will be changed–so your *weekly backup* will not be needed to update your personal files. After doing the System Restore, you can see if the shut down problem has changed. I would still recommend doing the boot to Safe Mode, first, to see if that has any effect on the shut down problem.

Just went through shutdown using Start menu.  All on screen looked familiar.  Screen message about program(s) preventing shutdown, “Force shutdown?” answered Yes- program preventing shutdown was Task Host Window.  BUT- Shutdown completed as normal, much to my surprise.

Reply | Quote

Screen message about program(s) preventing shutdown, “Force shutdown?” answered Yes- program preventing shutdown was Task Host Window.

Hmm… typically vague of Windows and good that it did not last an hour. This kind of “Task Host” delayed shutdown is still common to see in newer version of windows with no clear reason except any badly behaving program.

Please go to the Application & System sections of Event Viewer and see if there are logged events around the time of shutting down the computer. You may get lucky sometimes. 😉

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

The shutdown issue arose right away after Vista was reinstalled, about three days ago.

Well, as you well know, during the time that the Vista HDD was removed, Win7 was totally inactive. The only active OS was Linux that had access to your Win7 HDD. I have no idea what that access may have done–if Linux has to modify any file(s), or add any files in order for it to have access to the HDD.

The only other time was the session you first booted after the reinstall of the Vista HDD. Can you think of anything you did during the time of that first bootup? Install any programs, uninstall any programs, any major setting changes, etc.?

Slowpoke47 wrote:

We’ve been using the “sleep” mode.

*Sleep* and *Hibernate* or *Hybrid Hibernate* modes are known to be prone to issues–I don’t know if they would effect the *shut down* problem–but I do know from experience that I got locked out from my system when I could not successfully wake up from *hibernate*.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

The shutdown issue arose right away after Vista was reinstalled, about three days ago.

Well, as you well know, during the time that the Vista HDD was removed, Win7 was totally inactive. The only active OS was Linux that had access to your Win7 HDD. I have no idea what that access may have done–if Linux has to modify any file(s), or add any files in order for it to have access to the HDD. The only other time was the session you first booted after the reinstall of the Vista HDD. Can you think of anything you did during the time of that first bootup? Install any programs, uninstall any programs, any major setting changes, etc.?

Slowpoke47 wrote:

We’ve been using the “sleep” mode.

*Sleep* and *Hibernate* or *Hybrid Hibernate* modes are know to be prone to issues–I don’t know if they would effect the *shut down* problem–but I do know from experience that I got locked out from my system when I could not successfully wake up from *hibernate*.

While Linux was running, and the W7 HD was in place, the Linux OS “saw” the 7 and allowed access to the 7 Pictures file.  The Linux user manual says that, when Linux is installed in a dual boot situation, the Linux will offer the choice of which OS to open on startup, but this did not happen.  I assume that was because the bootup capability of W7 had previously been co-opted by the Vista OS when they were running as dual boot.

I think at this point I should sit back and see what does or doesn’t happen through several cycles of booting up and shutting down W7.

We use the “sleep” option all the time.  Should we stop doing that?

Reply | Quote

Slowpoke47 wrote:

While Linux was running, and the W7 HD was in place, the Linux OS “saw” the 7 and allowed access to the 7 Pictures file. The Linux user manual says that, when Linux is installed in a dual boot situation, the Linux will offer the choice of which OS to open on startup, but this did not happen.

Linux didn’t see the 7, per se.  It saw that there was a drive with data on it that it was able to read (since it knows how to read NTFS), so it made it available to you, the user, to browse.  That would have happened whether or not there was Windows on the drive or if it was nothing but the Windows Pictures directory.

It didn’t give you the choice of Windows with the Vista drive removed because as far as it was concerned, there wasn’t any Windows on the PC– which is the same conclusion the system BIOS/UEFI came to, since it was unbootable there too.  They’re looking for the bootloader, and if it’s not there, it’s not possible to boot Windows, so there would be no use in putting Windows in a menu when it can’t be used.  That doesn’t mean your Windows installation is not actually there, of course.  You can go into Linux and browse the folders and see that it is right there on the disk, or install the Vista drive and see that 7 boots just fine, so clearly, it’s there.  It’s just not usable as an OS without a means to boot it.

Once the bootloader is put on the 7 drive and GRUB is told to look again for other operating systems, it will then offer the choice as the manual says.  You’re really close to being at that point, so don’t get discouraged now!

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Screen message about program(s) preventing shutdown, “Force shutdown?” answered Yes- program preventing shutdown was Task Host Window.

Well, that’s interesting.

Google Search–task host window windows 7

Slowpoke47 wrote:

BUT- Shutdown completed as normal, much to my surprise.

Hard to complain about that–here’s hoping it continues to be so …

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

Screen message about program(s) preventing shutdown, “Force shutdown?” answered Yes- program preventing shutdown was Task Host Window.

Well, that’s interesting. Google Search–task host window windows 7

Slowpoke47 wrote:

BUT- Shutdown completed as normal, much to my surprise.

Hard to complain about that–here’s hoping it continues to be so …

Many thanks for your guidance.  I forgot to answer your question re installing or uninstalling any programs, etc. and the answer is no, I did not.

Do you advise shutting down in situations where one might use “sleep”?

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

I think at this point I should sit back and see what does or doesn’t happen through several cycles of booting up and shutting down W7.

Good idea.

I have a series of questions to ask regarding your setup before you continue to attempt to switch out your Vista HDD, and bring back your Linux HDD.

So, let us know when you’re ready to proceed.

Slowpoke47 wrote:

We use the “sleep” option all the time. Should we stop doing that?

Totally your option. If you have some unexplained behavior and you want to test to see if it may be part of the problem–there’s no harm in disabling it, even if it’s only for a short period of time for testing.

Personally, after being locked out of my system for awhile (I was able to find a solution, but had to find a different computer to look it up on!), I have chosen not to use Sleep and/or Hibernation going forward.

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Do you advise shutting down in situations where one might use “sleep”?

I still use a screen saver, password protected, but I wouldn’t shut down unless it’s the end of a day, and I want to be power off over night. There are those who think it’s a bad idea to power down and back up frequently, even just for overnight. The argument is that the constant temperature change from up and running, and then power down (sleep or off) causes more wear and tear on electronic circuits and moving parts than just keeping the system up and running and maintaining a near constant running temperature.

I can relate to keeping the power on and the system running–I had one motherboard whose chip fan would wear out in about 1 year–started squealing each morning for a couple minutes–eventually quieting down–but only replacement eliminated the problem for about another year. After I finally kept the system running 24/7–never had to replace that fan again! I suspect that applies to spinning disk HDDs too. So, I’m becoming more of a let’em run unless there’s a reason to shut down.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

There are those who think it’s a bad idea to power down and back up frequently, even just for overnight. The argument is that the constant temperature change from up and running, and then power down (sleep or off) causes more wear and tear on electronic circuits and moving parts than just keeping the system up and running and maintaining a near constant running temperature.

I used to operate under that assumption… my first PC, which I lovingly built in 1990, was on all the time, and S3 (standby/sleep) wasn’t an option. Part of it was about the convenience of not having to wait for it to boot, but part was this idea about longevity.

I don’t subscribe to that idea anymore, though.  The temperatures are nowhere close to relatively constant unless the load on each component the system is relatively constant.  Using the PC causes spikes in activity that heat up many bits of the PC, from the PSU to the CPU to the PCH to the motherboard VRM, and if you’re not running that kind of load constantly, it’s going to go through significant heating and cooling cycles from minute to minute anyway.

On top of that, the system is full of capacitors, and they’d much rather be warm for only short bursts and spend the rest of the time cool.  Their service life shortens markedly with temperature, and the longer that high temperature is maintained, the quicker the cap will tend to fail.  As long as the voltage and other electrical limits of the capacitor are observed, heat is the best predictor of a capacitor’s longevity.

Other items in the PC have similar characteristics, but in a less pronounced way.  Even the CPU chip itself is subject to this, though the failure rate of CPUs of any age that haven’t been abused somehow is very, very low.  They do degrade over time, and the hotter they run, the more that degradation will take place.  It will probably be obsolete before this has any noticeable effect on non-overclocked CPUs, but it’s still taking place.

Now, if you use standby, the system cools just as much as if you’d shut it down, for all intents and purposes.  To get any benefit from the constant-heat effect, you’d have to keep it under some load all the time.

I only shut my PCs down if I am going to be working on them, or if it’s a laptop, if it is about to be taken somewhere where I won’t be using it for several hours, or if it will be in a laptop bag or such where it could be damaged by the lack of ventilation if it inadvertently resumes (there have been complaints about laptops waking to install Windows 10 updates and overheating, or else running their batteries down, since they do not return to standby after the updates were complete.  I don’t use Windows 10, but still, I’d rather not risk it).

Otherwise, I just use standby, set to lock the session as soon as the standby command is issued, so it will prompt for the password on resume each time.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

Do you advise shutting down in situations where one might use “sleep”?

I still use a screen saver, password protected, but I wouldn’t shut down unless it’s the end of a day, and I want to be power off over night. There are those who think it’s a bad idea to power down and back up frequently, even just for overnight. The argument is that the constant temperature change from up and running, and then power down (sleep or off) causes more wear and tear on electronic circuits and moving parts than just keeping the system up and running and maintaining a near constant running temperature. I can relate to keeping the power on and the system running–I had one motherboard whose chip fan would wear out in about 1 year–started squealing each morning for a couple minutes–eventually quieting down–but only replacement eliminated the problem for about another year. After I finally kept the system running 24/7–never had to replace that fan again! I suspect that applies to spinning disk HDDs too. So, I’m becoming more of a let’em run unless there’s a reason to shut down.

Thanks again for your insight.  I’ll post back when I have some experience to report.

Reply | Quote

Update:  Last 2 shutdowns were as normal.

Searching “Task Host Window- Windows 7” brings up a number of hits relating shutdown problems to this app.  Apparently Microsoft has identified a problem and has a Hotfix available.  This repair is offered for downloading by at least one third-party site.  I’m more inclined to look for this directly from MS, but not sure what route to follow.  Comments?

Edit- found this- https://support.microsoft.com/en-us/help/975777/there-is-a-delay-when-you-shut-down-restart-or-log-off-a-computer-that

Looks like MS recommends the Hotfix if the Task Host Window pop-up or screen appears.  In my case, that doesn’t happen, but THW is cited as preventing shutdown.  MS mentions an update to be issued for this.  Should I wait for that or apply the Hotfix?

Reply | Quote

Ascaris wrote:

Slowpoke47 wrote:

While Linux was running, and the W7 HD was in place, the Linux OS “saw” the 7 and allowed access to the 7 Pictures file. The Linux user manual says that, when Linux is installed in a dual boot situation, the Linux will offer the choice of which OS to open on startup, but this did not happen.

Linux didn’t see the 7, per se. It saw that there was a drive with data on it that it was able to read (since it knows how to read NTFS), so it made it available to you, the user, to browse. That would have happened whether or not there was Windows on the drive or if it was nothing but the Windows Pictures directory. It didn’t give you the choice of Windows with the Vista drive removed because as far as it was concerned, there wasn’t any Windows on the PC– which is the same conclusion the system BIOS/UEFI came to, since it was unbootable there too. They’re looking for the bootloader, and if it’s not there, it’s not possible to boot Windows, so there would be no use in putting Windows in a menu when it can’t be used. That doesn’t mean your Windows installation is not actually there, of course. You can go into Linux and browse the folders and see that it is right there on the disk, or install the Vista drive and see that 7 boots just fine, so clearly, it’s there. It’s just not usable as an OS without a means to boot it. Once the bootloader is put on the 7 drive and GRUB is told to look again for other operating systems, it will then offer the choice as the manual says. You’re really close to being at that point, so don’t get discouraged now!

My earnest thanks to you for following this thread and offering your guidance and insight.  After poking around a bit I see that the delayed shutdown may not be the result of my manipulations with this PC as there is an issue known to MS re Task Host Window, which is named (but not shown in a window) as preventing shutdown.  Not sure if I should follow up with that at this point, or not.  In any case, since I now have two consecutive normal shutdowns, my best bet may be to sit back and monitor the situation.

Since it appears that The PC is back to its condition from before the Mint install, there’s no need to rush off and do anything without some additional context.

BTW, interesting that, when the Linux and W7 HD’s were installed, the Mint OS would show the W7 Pictures folder, but nothing else from that OS- no Docs, etc.  But that doesn’t need to be addressed.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Looks like MS recommends the Hotfix if the Task Host Window pop-up or screen appears. In my case, that doesn’t happen, …. Should I wait for that or apply the Hotfix?

If it’s not causing a problem, at least at the moment, I would recommend to not fix what isn’t broken. You can store this information somewhere where you can easily find it again–like a bookmark to that MS hotfix page–come back to it if you need it in the future.

If the problem does return, I would try some other trouble shooting first, before assuming I need to apply the hotfix.

Again, just me and my opinion.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Update re W7 performance as of Thursday a.m.- last Tuesday, 3/5, had two normal shutdowns out of two.  Yesterday, 3/6, had two normal (but slow last step) and one hang-up on the “shutting down” screen.  Also, a few freeze-ups while working with files/ folders  in Explorer.  I recall that, over at least the last few weeks, there was on shutdown the message re programs preventing shutdown and the program shown was Task Host Window.  But the system did shut down without intervention before I began playing musical chairs with the hard disks.    This is apparently a known problem for MS and there is a “hotfix” available and there will be an update issued for this at some point.

I see it as important to get W7 working properly both on startup and shutdown before I once again substitute the Mint HD for Vista.  Perhaps the first step is System Restore, then tackle the shutdown hangup.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

I recall that, over at least the last few weeks, there was on shutdown the message re programs preventing shutdown and the program shown was Task Host Window. But the system did shut down without intervention …

Well, that appears to be *new information* that you had not mentioned in your previous posts.

So, looking back over the *last few weeks*–did you make any major changes in your system that may have triggered that shut down message? Installed new software? Uninstalled old software? Reconfigured settings? Usually, with computers, there’s a *cause and effect*, but I know sometimes it’s hard to remember when a problem first occurred, and what you might have been doing just before the problem occurred. Just FYI, it would be a good practice to jot down a note, with date and time, to yourself whenever something that’s new and out of the ordinary happens–just in case you need to go back and address an issue.

Slowpoke47 wrote:

Perhaps the first step is System Restore, then tackle the shutdown hangup.

Given what I mentioned above in the last sentence, how far back are you going to go to do a System Restore? I guess another question is *How far back do you have Restore Points to go back to?

Slowpoke47 wrote:

This is apparently a known problem for MS and there is a “hotfix” available …

So, the problem with this is MS did not clearly explain what triggers this problem. I don’t have the problem on my system. Scanning the Internet–it does not look like a large percentage of folks are having this problem–seems more isolated–so my take away is that the hotfix may or may not address whatever the issue is. Probably won’t hurt to try it–but remember–there are *causes and effects*–you don’t know ahead of time if all is going to go well. If you had a *whole drive imaging* backup in place that allowed you to restore back to the most recent *image* (I take images prior to all major installs, prior to all Windows Updates being downloaded and applied, prior to any experimenting of new settings for Windows or other programs, and prior to updates to various other software programs–just to be safe, and making sure I can go back if something goes wrong–it’s really liberating to know that you can do that!), that would really be an ideal safety net so you could do these changes without worrying. (You had mentioned in one of your posts that you had tried an imaging program, something had gone wrong, and you have not gone back to try and resolve what ever that problem may have been.)

So, there’s a huge *elephant* in the room!

Zaphyrus wrote:

also I would look at possible services that crashes when shutting down, I would check event viewer

And you responded:

Slowpoke47 wrote:

Event viewer shows 6,600 errors.

To be fair, looking at the screenshot, Event Viewer reports 6,602 *events*–not all of those are necessarily *errors*–some *events* are simply notifications and not *errors*.

But, looking at the screenshot, it looks like there are a lot of *errors* listed in that very small sample.

Slowpoke47 wrote:

Event viewer shows 6,600 errors. What’s next?

Below that post, you were given a number of different suggestions–there’s no evidence that you followed up on those suggestions–you may not have understood what was being offered as possible next troubleshooting steps.

But, the bottom line, if you have that many errors being reported, there’s a strong possibility that buried somewhere in that list is an event that may be effecting the shut down of your system.

Will a System Restore make whatever that event is go away? Who knows? You can sort the Event log by *Date and Time*–note the time of shut down, and the next reboot, look for any events with that approx. time. You can sort the Event log by *Event* number–you can see how many entries of a given event happen at the time of shut down. You can sort the Event log by *Task*–you can see if any of the entries around shut down have anything to do with *shut down*.

anonymous wrote:

The event viewer sections Application and System will be the best place to look for critical errors.

Your screen shot is of the *Administrative Events*–there are other Event logs as mentioned above to look at as well.

This is what I meant before in one of my other posts–there are other *troubleshooting* efforts that can be done besides looking for a quick fix of a *hotfix* or a System Restore. And there are actually *more* trouble shooting that can be done besides what’s mention so far above.

You will have to decide what you want to do next …

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

I recall that, over at least the last few weeks, there was on shutdown message re programs preventing shutdown and the program shown was Task Host Window</span>. But the system did shut down without intervention …

Well, that appears to be *new information* that you had not mentioned in your previous posts. So, looking back over the *last few weeks*–did you make any major changes in your system that may have triggered that shut down message? Installed new software? Uninstalled old software? Reconfigured settings? Usually, with computers, there’s a *cause and effect*, but I know sometimes it’s hard to remember when a problem first occurred, and what you might have been doing just before the problem occurred. Just FYI, it would be a good practice to jot down a note, with date and time, to yourself whenever something that’s new and out of the ordinary happens–just in case you need to go back and address an issue.

Slowpoke47 wrote:

Perhaps the first step is System Restore, then tackle the shutdown hangup.

Given what I mentioned above in the last sentence, how far back are you going to go to do a System Restore? I guess another question is *How far back do you have Restore Points to go back to?

Slowpoke47 wrote:

This is apparently a known problem for MS and there is a “hotfix” available …

So, the problem with this is MS did not clearly explain what triggers this problem. I don’t have the problem on my system. Scanning the Internet–it does not look like a large percentage of folks are having this problem–seems more isolated–so my take away is that the hotfix may or may not address whatever the issue is. Probably won’t hurt to try it–but remember–there are *causes and effects*–you don’t know ahead of time if all is going to go well. If you had a *whole drive imaging* backup in place that allowed you to restore back to the most recent *image* (I take images prior to all major installs, prior to all Windows Updates being downloaded and applied, prior to any experimenting of new settings for Windows or other programs, and prior to updates to various other software programs–just to be safe, and making sure I can go back if something goes wrong–it’s really liberating to know that you can do that!), that would really be an ideal safety net so you could do these changes without worrying. (You had mentioned in one of your posts that you had tried an imaging program, something had gone wrong, and you have not gone back to try and resolve what ever that problem may have been.) So, there’s a huge *elephant* in the room!

Zaphyrus wrote:

also I would look at possible services that crashes when shutting down, I would check event viewer

And you responded:

Slowpoke47 wrote:

Event viewer shows 6,600 errors.

To be fair, looking at the screenshot, Event Viewer reports 6,602 *events*–not all of those are necessarily *errors*–some *events* are simply notifications and not *errors*. But, looking at the screenshot, it looks like there are a lot of *errors* listed in that very small sample.

Slowpoke47 wrote:

Event viewer shows 6,600 errors. What’s next?

Below that post, you were given a number of different suggestions–there’s no evidence that you followed up on those suggestions–you may not have understood what was being offered as possible next troubleshooting steps. But, the bottom line, if you have that many errors being reported, there’s a strong possibility that buried somewhere in that list is an event that may be effecting the shut down of your system. Will a System Restore make whatever that event is go away? Who knows? You can sort the Event log by *Date and Time*–note the time of shut down, and the next reboot, look for any events with that approx. time. You can sort the Event log by *Event* number–you can see how many entries of a given event happen at the time of shut down. You can sort the Event log by *Task*–you can see if any of the entries around shut down have anything to do with *shut down*.

anonymous wrote:

The event viewer sections will be the best place to look for critical errors.

Your screen shot is of the *Administrative Events*–there are other Event logs as mentioned above to look at as well. This is what I meant before in one of my other posts–there are other *troubleshooting* efforts that can be done besides looking for a quick fix of a *hotfix* or a System Restore. And there are actually *more* trouble shooting that can be done besides what’s mention so far above. You will have to decide what you want to do next …

The background to this is that I am extremely uncomfortable with the suggestions offered, because I do not trust my ability to understand or carry them out correctly.

Re the “Task Host Window” message, I only remembered in retrospect having seen it and, since until lately, the system did shut down, so I didn’t recognize it as significant.  But, looking back, this PC has shut down in leisurely fashion for perhaps months, although never getting hung up until this last week or two.

I’m mostly over my head here, and apprehensive of making some irreversible mistake.  Since this is my first and only computer, I have no context re what is or isn’t a problem, which is why I didn’t mention the “Task Host Window” item before.  I didn’t se it as a problem until I saw the MS site.   Sorry to be so thick, but I’m trying to understand and doing the best I can.

It does seem logical that this W7 disk needs to be straightened out at both ends, bootup and shutdown, before anything else.

Reply | Quote

@slowpoke47, it seems to me that you’ll never be able to resolve the Windows 7 bootup issue, and reach your destination of having Linux installed, until you clear the hurdle of making an image backup. Having a backup really frees you up to experiment, make mistakes, and learn from them. (For example, you can then try some of the methods that have been proposed to create a boot sector on your Windows 7 drive, and be assured that you haven’t lost anything if the attempt messes something up.)

So I would recommend that you review the threads that are linked to in this post. At the end of it, with any luck you will have a clear idea of what to do. And of course, feel free to ask for additional details or guidance at any step of the backup process.

NEW IDEA: As I was thinking about the overarching issue, it occurred to me that you may not need to ditch the Vista disk (which enables your Windows 7 to boot up) in order to have Linux. How big (in GB capacity) is your Vista disk? If space allows, maybe you can create a new empty partition past the Vista partitions, and install Linux there.

In effect, you’d have a triple-booting computer, with Vista and Linux on one drive and Windows 7 on the other. I have one PC that’s triple-booting XP, Vista, and Kubuntu Linux on a single hard drive; if you can select from two OSes in two different drives, you should equally be able to select from three OSes in two drives.

This approach would bypass the whole issue of not being able to boot into Windows 7, while still allowing you to boot into Linux and use it.

We’d still need to address the “no shutdown” issue, but this would be a big step toward your objective.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

2 users thanked author for this post.

Sinclair, Slowpoke47

Reply | Quote

@Slowpoke47-
I’ve been following your ‘adventure’… and as a fellow non-techy, I know that it is easy to get overwhelmed by things that others find routine. I’ve admired your courage and persistence in continuing to problem solve.

It really changed my perspective, last year, to have to replace a failing hard drive. I decided not to copy my current system, because I’d experimented a lot, and had a lot of unnecessary programs and files on it. It took some work, but I was able to start over on a new disk… and add just the updating, programs and personal files I wanted. I went through being terrified, anxious, etc… even when sure of what needed to be done, just because my laptop is so precious to me… and because I do not have the money to replace it. Luckily (after lots of research, and having multiple back ups) it all turned out well. Really, having all the back ups, allowed me to feel able to experiment…

You were attempting to do one thing, and then had problems… exactly where most of us freak and stop experimenting. Having an image backup will allow you to restore your hardrive/computer, back to your best known state… which should reassure you. It took having an external hard drive enclosure hooked up to my computer to reassure me… I had to actually see and be able to browse through both the drive on my computer, and other hard drives, and see that what I wanted was there, in both places. Otherwise it all felt like some kind of not well understood magic for me, and my anxiety was based on thinking I would probably do something wrong and permanently mess it up. Once I knew that I could completely mess up one hard drive, and still have another one to function, I relaxed, and have felt easier about experimenting since then. In the long run, getting to move to Linux will be important to a lot of people… and thus documenting what you have or have not done is helping all of us learn.

I didn’t see mentioned something I’d read, and haven’t been able to find again… and my memory about it is poor… but it was about how Windows doesn’t play well with others, and that it is easier to have it primary (first) in a double boot situation, as attempting to put the Linux OS first will often mess up being able to boot back to Windows. Because I can’t find the reference, I may be getting the terminology wrong… maybe someone else could correct or help here.

We still have an old Vista laptop that I’m hoping to put some form of Linux on (probably a more light weight distro than Mint)… but I’ve had a lot of medical issues that have been slowing down my experimentation. I just want to say, please, don’t give up, as I’m sure what all of us are learning, whether it is problems encountered, ways to diagnose, or how to better guide non-techies through the process, your documentation of your experiences are valuable. So… have back ups… and continue forth, for all the rest of us facing the same Windows 7 EOL… Please…

Non-techy Win 10 Pro and Linux Mint experimenter

1 user thanked author for this post.

Slowpoke47

Reply | Quote

I would like to be there to solve your problem. You would learn some knowledge from me, but not experience the personal satisfaction of overcoming fear of the unknown nor gain the skill-set to do it yourself.

Reply | Quote

Just before this fiasco, I reconfigured the LAN here to connect one of the printers directly to the network rather than to this PC via USB cable as before.  That resulted in another horror show, trying to make the PC find the printer in the new arrangement and ultimately led to having to reinstall all the printer software.  Some decidedly odd things happened with that, documented here and https://computerhelpforums.com/.  In the end, the exact same steps that failed at first later worked.

At that time, as now, the Vista and W7 disks were installed and functioning, but without the current shutdown issue (BTW, in 7 only, Vista shuts down without incident)..

Reply | Quote

Through your printer experience do you like having new knowledge?

Do you believe afterwards you could fix the same or similar problem without help?

Reply | Quote

Cybertooth wrote:

@slowpoke47, it seems to me that you’ll never be able to resolve the Windows 7 bootup issue, and reach your destination of having Linux installed, until you clear the hurdle of making an image backup.

I did attempt this with Macrium Reflect, trial subscription ongoing, but At some point the program told me that the space needed for the image was ‘way bigger than any media I had on hand, IIRC several hundred GB, so I abandoned the effort.  But I could have misunderstood that info.

NEW IDEA: As I was thinking about the overarching issue, it occurred to me that you may not need to ditch the Vista disk (which enables your Windows 7 to boot up) in order to have Linux. How big (in GB capacity) is your Vista disk? If space allows, maybe you can create a new empty partition past the Vista partitions, and install Linux there. In effect, you’d have a triple-booting computer, with Vista and Linux on one drive and Windows 7 on the other. I have one PC that’s triple-booting XP, Vista, and Kubuntu Linux on a single hard drive; if you can select from two OSes in two different drives, you should equally be able to select from three OSes in two drives. This approach would bypass the whole issue of not being able to boot into Windows 7, while still allowing you to boot into Linux and use it. We’d still need to address the “no shutdown” issue, but this would be a big step toward your objective.

That’s an interesting suggestion, but the reason for the new HD is that the old one is just that, old- and it seemed that a new drive would last longer.

Note my comment above within the highlighted quote- I don’t know how to quote using less than the full original.

Reply | Quote

Slowpoke47 wrote:

I did attempt this with Macrium Reflect, trial subscription ongoing, but At some point the program told me that the space needed for the image was ‘way bigger than any media I had on hand, IIRC several hundred GB, so I abandoned the effort. But I could have misunderstood that info.

The Reflect message that you report doesn’t ring a bell, but it sounds like the disk where you wanted to store the backup image wasn’t big enough. You might try attempting the image again, but making sure to select one of the “compressed” file settings during the process of setting up the backup. I usually choose the “medium compressed” setting.

Slowpoke47 wrote:

That’s an interesting suggestion, but the reason for the new HD is that the old one is just that, old- and it seemed that a new drive would last longer. Note my comment above within the highlighted quote- I don’t know how to quote using less than the full original.

No doubt you’re right that a new HDD will last longer, but if you can image the current Vista drive with Macrium, then you can put the image on a new, blank HDD and plug it in. The new drive could even be a larger one to fit Vista and Linux comfortably. Then, after verifying that both Vista and Windows 7 boot up as normal with the new Vista drive in place, you can proceed to try installing Linux on that drive alongside Vista, and then see if you can boot into all three OSes.

Regarding how to quote less than the original, the only way that I know of is to delete the parts of the quote that I don’t need, as if I were editing a document. If I think that I might be responding to more than one thing from the quote (like in this post), then I’ll highlight the whole quote and copy it to the editing box here, and delete the appropriate sections of each copy so that my replies address each respective part.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Slowpoke47 wrote:

Note my comment above within the highlighted quote- I don’t know how to quote using less than the full original.

Simply highlight the text you want to quote, then hit the quote button. Only the highlighted text will be quoted.

Non-techy Win 10 Pro and Linux Mint experimenter

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Elly wrote:

Windows doesn’t play well with others, and that it is easier to have it primary (first) in a double boot situation, as attempting to put the Linux OS first will often mess up being able to boot back to Windows.

I’ll be making another attempt at a system image shortly.

Thanks for the encouragement.  Before I can test that out, the W7 disk has to be straightened out.  Interestingly, the Mint user manual says that it does in fact play well with others, whether the reverse is true, unknown.

I wonder if this is how Lewis and Clark felt in their forays into the unknown.

2 users thanked author for this post.

Elly, Cybertooth

Reply | Quote

Cybertooth wrote:

Slowpoke47 wrote:

I did attempt this with Macrium Reflect, trial subscription ongoing, but At some point the program told me that the space needed for the image was ‘way bigger than any media I had on hand, IIRC several hundred GB, so I abandoned the effort. But I could have misunderstood that info.

The Reflect message that you report doesn’t ring a bell, but it sounds like the disk where you wanted to store the backup image wasn’t big enough. You might try attempting the image again, but making sure to select one of the “compressed” file settings during the process of setting up the backup. I usually choose the “medium compressed” setting.

Slowpoke47 wrote:

That’s an interesting suggestion, but the reason for the new HD is that the old one is just that, old- and it seemed that a new drive would last longer. Note my comment above within the highlighted quote- I don’t know how to quote using less than the full original.

No doubt you’re right that a new HDD will last longer, but if you can image the current Vista drive with Macrium, then you can put the image on a new, blank HDD and plug it in. The new drive could even be a larger one to fit Vista and Linux comfortably. Then, after verifying that both Vista and Windows 7 boot up as normal with the new Vista drive in place, you can proceed to try installing Linux on that drive alongside Vista, and then see if you can boot into all three OSes. Regarding how to quote less than the original, the only way that I know of is to delete the parts of the quote that I don’t need, as if I were editing a document. If I think that I might be responding to more than one thing from the quote (like in this post), then I’ll highlight the whole quote and copy it to the editing box here, and delete the appropriate sections of each copy so that my replies address each respective part.

Have to leave off on this for today, but maybe you could answer one question- what sort of capacity range is usually needed for a system image?  Thanks!

Reply | Quote

The answer depends mainly on two factors: whether you compress the backup image and how much stuff is on the drive that you’re imaging. A third factor is how compressible the data is, as some types of files are more amenable to compression than others.

In my case, by using Medium compression, Reflect creates a ~165GB image from my Vista C: and D: drives which together amount to some 285GB. (That’s the stuff on the drives, not the total capacity of the drives.)

Hope this helps. Keep us posted!

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Look at current prices of two terabyte drives. Final image file size will depend on the fullness of the drive to be imaged, compression settings, ability for the backup program to ignore unused sectors and skip certain windows files.

Once you learn how to do one drive others will follow…

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Have you tried disabling, Fast startup?   It is known that when its enabled, it causes start and shutdown problems.

Just someone who don't want Windows to mess with its computer.

Reply | Quote

@ Zaphyrus

Zaphyrus wrote:

Have you tried disabling, Fast startup?

I think that feature is only available with Win8 and Win10:

What is Fast Startup and how to enable or disable it in Windows 10/8

1 user thanked author for this post.

Zaphyrus

Reply | Quote

You can find some really weird model-specific add-on software on some devices…

As in every now and then you might well a find Windows 7 system that leaves the NTFS in a state that Linux NTFS drivers recognize as “hibernated or fast startup enabled” after supposedly “shutting down”.

Of course some of that will be people putting the thing in hibernation or hybrid sleep instead of actual shutdown, but anyway.

Reply | Quote

@ slowpoke47 and @ Cybertooth

Slowpoke47 wrote:

Note my comment above within the highlighted quote- I don’t know how to quote using less than the full original.

Cybertooth wrote:

Regarding how to quote less than the original, the only way that I know of is to delete the parts of the quote that I don’t need, as if I were editing a document.

It’s actually easy–just use your mouse to highlight the section of text you wish to quote, and then hit the *QUOTE* button that’s at the bottom, right corner of the post–that will place the highlighted material as quoted material in the Reply Box at the bottom of the thread for you.

As above, I have quoted from two different posts and each is referenced as to the source and only the highlighted text has been brought in here.

If you want or need to get fancier and bring in a quote from another topic–just open a new webpage to that topic, highlight the material you want to bring in, and again press the *QUOTE* button. Copy the material that gets put into the Reply Box of that other topic, and then Paste that to the current topic–so like this:

Slowpoke47 wrote:

Today, removed the original Vista HD and installed a new blank drive which is now successfully loaded with Linux Mint.

During the installation, I unplugged the W7 HD inside the case, to be sure the new install went on the new HD. Both drives now connected, Mint working ok but BIOS can no longer open the W7 drive.

4 users thanked author for this post.

Elly, wavy, Cybertooth, Slowpoke47

Reply | Quote

Just Lurking wrote:

It’s actually easy–just use your mouse to highlight the section of text you wish to quote, and then hit the *QUOTE* button that’s at the bottom, right corner of the post–that will place the highlighted material as quoted material in the Reply Box at the bottom of the thread for you.

Many thanks for this.  I’m trying to further my computer skills, but that knowledge is full of holes, although greatly assisted by those such as yourself who know what to do in a given situation and provide guidance.

I’ve saved your post for reference.

1 user thanked author for this post.

Just Lurking

Reply | Quote

Thanks to all who posted.  Trying now to figure out what to do and in what order.  I now realize that System Restore is not the way to go because, as mentioned, that would purge the printer drivers, which I recently reinstalled after a LAN reconfiguration.  The printer is no longer supported by HP and the software reinstall took a tortuous path, to say the least.  Now that all is ok there, I don’t want to take any chances with it.

So, the three issues to address, in order as I see it, are:

1.  Deal with erratic shutdown performance: https://answers.microsoft.com/en-us/windows/forum/all/task-host-window-will-not-let-me-shut-down/ef7af008-fabe-4671-b51f-a9e31ca2e427

2.  Follow suggestions posted earlier in this thread to restore independent bootup of W7

3.  Reinstall HD with Mint OS in place of Vista and look for usable dual boot on startup.  My first choice would be to eliminate Vista completely.

As suggested, I will make another attempt to make a system image, need to find a suitable ext. drive, may not succeed locally (small town).  Please see screenshot, shows total of less than 220GB used.  I understand that a 250GB ext. drive is not enough for this image, but would 500GB be ok?

Reply | Quote

A 500GB drive will definitely be OK for your purpose.

However,  that 250GB drive should also be OK, even without compression, unless it currently has enough stuff on it that there’s not enough space left over for the image that you want to make.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

The background to this is that I am extremely uncomfortable with the suggestions offered, because I do not trust my ability to understand or carry them out correctly.

I understand. I’ve been watching your responses to *certain* suggestions, and I suspected you might not be in your comfort zone.

Slowpoke47 wrote:

I’m mostly over my head here, and apprehensive of making some irreversible mistake. Since this is my first and only computer, I have no context re what is or isn’t a problem, …

Don’t underestimate yourself! It looks like you have been computing with this originally Vista based system for some time now. I’ve seen evidence that you are doing certain things that suggests you are less than a *novice* computer user.

Slowpoke47 wrote:

Sorry to be so thick, but I’m trying to understand and doing the best I can.

Don’t be too hard on yourself–we all started at the beginning of our journey at one point or another.

Slowpoke47 wrote:

It does seem logical that this W7 disk needs to be straightened out at both ends, bootup and shutdown, before anything else.

I agree. I’m going to have to be away from my computer for the rest of the day and evening, so I probably won’t be commenting until tomorrow at the soonest. But, we need to do some non-invasive troubleshooting to see where the trouble might be with the shut down issue. I’ll walk you through it, one item at a time, so we can see the results. (By the way, you will need some of the skills I’m going to ask you to try if you want to reach the point of having your Win7 booting independently of your Vista harddrive.)

2 users thanked author for this post.

Elly, Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

I understand that a 250GB ext. drive is not enough for this image, but would 500GB be ok?

I have a 2 TB (Terabyte) WD (Western Digital) USB 3.0 Passport external harddrive for images. It can be used on systems that only have USB 2.0 abilities–just slower–but you have what you have unless you want to upgrade your hardware. I can store multiple images and can go back several months. I start deleting the oldest images when the external harddrive starts getting full to make room for new image backups.

These have been available at our local Costco for approx. $90.00–cheaper if on sale. I think I’ve seen capacities for this type harddrive at 3 and 4 TBs, but the 2 TB has been very adequate.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

A 500GB drive will definitely be OK for your purpose. However, that 250GB drive should also be OK, even without compression, unless it currently has enough stuff on it that there’s not enough space left over for the image that you want to make.

The only ext. drive I have currently is set up with a downloadable Linux Mint which got me set up with that OS on the new HD for this machine.  I’m saving that for the Mint addition to our laptop, also now using 7, once I get this mess fixed.  Since I know that download is correct, but was unable to check the ISO image as suggested, I’ll keep that aside as a known quantity.

So I’ll get another ext. medium for this effort- may want to keep that for future reference as well (if successful) since I expect to keep 7 indefinitely.  But I have been told that approaching the stated capacity in a case like this is not recommended.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Proud new owner of 1TB Seagate ext. drive.  $49 at Walmart.  Tomorrow I’ll try again for a system image.  But, a question- won’t the system image also capture the boot and shutdown problems?

Reply | Quote

In the backup programs I use, there is a check box to indicate what you want to backup: mbr, C:, Restore, OEM, etc.
Depending on what you choose to back up, you can back up anything from only the C: partition to the whole enchilada.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Slowpoke47 wrote:

Proud new owner of 1TB Seagate ext. drive. $49 at Walmart. Tomorrow I’ll try again for a system image. But, a question- won’t the system image also capture the boot and shutdown problems?

Yes, that’s the whole idea: to have a backup of your current Windows 7 drive so that you can try different things on the original drive to fix the shutdown problem, and then if anything goes wrong to be able to go back to the current state.

You want to image EVERYTHING on that disk, including the boot sector, OEM partition, etc.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

PKCano wrote:

In the backup programs I use, there is a check box to indicate what you want to backup: mbr, C:, Restore, OEM, etc. Depending on what you choose to back up, you can back up anything from only the C: partition to the whole enchilada.

I’ve been backing up automatically with Veeam.  It’s set up to back up files every week and the whole shebang monthly.

The new drive is so I can attempt a system image as the first step in correcting my boot and shutdown issues- I believe the advice to do that before diving in.  Didn’t want to co-opt the backup drive.  I’ll be doing that tomorrow morning.

Reply | Quote

I might have missed it but have you

-tried the w7 install disk to do a repair recovery of boot info (possibly/likely non existent on your W7 system disk for w7) ?

– tried easybsd to check same?

After using Macrium or similar to back up your W7 hdd of course to perhaps your Linux disk.

(free version available to install and boot from cd)

(all done w/o the vista disk running)

🍻

Just because you don't know where you are going doesn't mean any road will get you there.

Reply | Quote

That’s easybcd Wavy, not easybsd…..

 

Jerry

1 user thanked author for this post.

wavy

Reply | Quote

Cybertooth wrote:

Slowpoke47 wrote:

Proud new owner of 1TB Seagate ext. drive. $49 at Walmart. Tomorrow I’ll try again for a system image. But, a question- won’t the system image also capture the boot and shutdown problems?

Yes, that’s the whole idea: to have a backup of your current Windows 7 drive so that you can try different things on the original drive to fix the shutdown problem, and then if anything goes wrong to be able to go back to the current state. You want to image EVERYTHING on that disk, including the boot sector, OEM partition, etc.

Thanks for that- I’ll be working on the image this morning, once I get the year-end docs ready.  Meanwhile, in the course of some accounting work within Windows Explorer, I still get occasional screen freezes, no idea if this is a separate issue or not…

Another question- if I use the same usb port on the PC for the new ext. drive as I do for the usual backup drive, should I expect any “confusion” on the part of the OS?

Reply | Quote

…should I expect any “confusion” on the part of the OS?

Normally no confusion should happen, each device has a unique id.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

Just looked at Error Reporting in System Information, dozens of entries, not in chronological order, dating to last Sept.  No clue what if anything to do with this info.  File too big to attach, here’s a screenshot of part of the list:

Reply | Quote

That newest entry from earlier this week could be a vital bit of information. If you want to see what the faulting application is just move the mouse cursor over the “Faulting applica…” area then wait until you see a yellow tool-tip box.

One problem at a time if possible…

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Proud new owner of 1TB Seagate ext. drive. $49 at Walmart.

Good morning.

I had to swing by our local Costco yesterday–they now carry the Seagate 2 TB USB 3.0 drive, and not the WD external drive (if I remember correctly, Seagate and WD are the same company–just different *brand* names). Their price was $75 for that Seagate external drive.

Of course, you may not have a Costco nearby to consider as a source option.

Slowpoke47 wrote:

Another question- if I use the same usb port on the PC for the new ext. drive as I do for the usual backup drive, should I expect any “confusion” on the part of the OS?

Windows tries to *remember* what USB devices have been previously hooked up, and if it’s been disconnected for a time Windows attempts to re-assign the same drive letter the next time it sees that device–but, if for whatever reason Windows can not or will not assign the same drive letter, it will simply re-use a drive letter and assign the re-used drive letter to a new device, and the system will just continue.

The only *confusion* factor is usually on the part of the user seeing an unexpected drive letter on a new device. But, if you are paying attention, it’s not hard to follow what’s going on!

3 users thanked author for this post.

Myst, Cybertooth, Slowpoke47

Reply | Quote

The drive I bought is a Seagate.  System sees it when connected via included usb cable.  Attempting system image via Macrium but stuck on destination- looks like the only destinations offered are a folder to be specified or a CD/DVD.

The choices under “alternate locations do not include the ext. disk.  What am I doing wrong?

Reply | Quote

The three dots (…) on the right side ot the “Folder” pulldown will probably give you access to the folder on your external drive that you created to put the backup in.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

anonymous wrote:

That newest entry from earlier this week could be a vital bit of information. If you want to see what the faulting application is just move the mouse cursor over the “Faulting applica…” area then wait until you see a yellow tool-tip box. One problem at a time if possible…

One at a time, yes.  Perhaps this is not first priority.

 

Reply | Quote

PKCano wrote:

The three dots (…) on the right side ot the “Folder” pulldown will probably give you access to the folder on your external drive that you created to put the backup in.

Thanks- I’ll start over and try that.  At this point I’m gun-shy about just about any move I make.  When I selected the first item in the left pane, which looked to me to be the path to a system image, the screen in the s/shot came up, including the new drive, not visible in the s/shot.  It was selected as part of the image, as are the others but I unchecked it, seemed like the right thing to do since I want it to be the destination.  I looked at the Macrium user guide but it is somewhat over my head re terminology.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

I’ve been backing up automatically with Veeam. It’s set up to back up files every week and the whole shebang monthly.

You’re in a *perfect* position to test your backup solution. (Note: creating a backup is only half of the process of using imaging as a solution–until you successfully create a successful *restore*, you do not know if you can actually recover from a disaster situation.)

Here’s an outline:

With your Vista HDD and Win7 HDD installed, create a whole drive backup of the Win7 HDD.

Switch out your Win7 HDD for your Linux HDD. (Does Veeam only run under the Windows OS? If so, you may not be able to do the next step(s).)

Create a whole drive backup of the Linux HDD. (One really needs the ability to boot to some sort of *recovery media* that allows for backup and/or restore of a backup to whatever HDD is needed. Maybe you can boot to the Vista OS and use your Veeam backup software from there?)

Now, restore the backup of your Win7 HDD to the Linux HDD. Now, re-boot and can you select the Win7 OS and bring up that OS successfully? If yes, your backup and restore functions are working as they should. If not, then something is missing or not configured quite right and needs to be worked on.

And, now restore the backup of the Linux HDD to the HDD that has the restored Win7 on it. Re-boot and does Linux come up successfully. If yes, your backup and restore functions are working as they should.

And finally, replace the Linux HDD with the Un-Touched Win7 HDD and you are right back where you started from, and if everything worked as planned, you now know that your backup and restore functions are operational, and you can count on them in a disaster situation!

If any of these steps did not work, then we need to troubleshoot what’s not working.

Note, that throughout these testing procedures, your original Win7 HDD is never at *risk*–it is removed from the system for safe keeping, and we never attempt to restore to your *production* Win7 HDD–i.e. the HDD you currently use for everyday computing.

Did this make sense? Questions?

(I’m not familiar with the Veeam software. Is it an *imaging* program, or is it a *backup* program–there actually is a difference.)

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Attempting system image via Macrium …

Ah, see that you are attempting to use Macrium, and not Veeam software.

The need for being able to boot to *Recovery Media* is still a valid need. You will not be able to restore an OS partition from within the OS partition that is up and running–so can not run Macrium from the Win7 OS partition, and restore that Win7 OS partition. There’s no problem creating backup images while running Macrium from the Win7 OS, just can not restore those images.

Until you get to the point of removing the Vista HDD, you can probably run Macrium from the Vista OS, and restore the Win7 OS to the Win7 HDD, but once you remove the Vista HDD, then you will not have a second Win OS to boot to and use for restoring the Win7 OS partition.

Just Lurking wrote:

You’re in a *perfect* position to test your backup solution.

Just to clarify, what I mean by a *perfect* position–you have that *spare* Linux HDD that is not *critical* to your day to day computing–you can *sacrifice* it to testing without loosing *everything*. So test until you have everything setup right, and you’re comfortable with the outcomes.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

At this point my confusion is about complete.  NightOwl, you are correct that I am not a “novice” but my skills are anecdotal, with no training, and as such have multiple gaps.  I am doing the best I can to recover from my missteps using the guidance here, but the level of my understanding presumed by many of the advisors here is overly optimistic.  I’m sure that, in attempting to follow the suggestions, I’ve just been complicating the issue.

For context, here is a snapshot of the current situation:

Both Vista and W7 HD’s are installed.  Either will boot up as expected, and Vista shuts down without incident.  In 7, I’ve been getting freezes in Explorer which I escape using esc or by selecting the “close the program” option in the pop-up.  The shutdown of 7 is successful about ¾ of the time, albeit usually slowly.  The message at shutdown that Task Host Window is preventing shutdown began appearing occasionally some weeks (or months) back, but never stopped shutdown.  Now, of course, it appears every time.  The W7 OS has been scanned for malware, chkdsk and sfscan came back clean.

For the last few weeks I have used the Veeam app for weekly backups and a week ago installed the Macrium Reflect program to make a system image, both suggested here.  Once this is posted, I’ll try the image again, with the tip posted above by PKCano.

I believe the three issues to address, in order are:

Correct the W7 shutdown issue

Repair the W7 bootup to allow starting without Vista

Resubstituting the Mint HD for the Vista, which has nothing on it that needs to be saved.

But, I am at a loss as to just where to go from here for the reasons mentioned.

Reply | Quote

Thanks to PKCano’s suggestion, I was able to specify the ext disk as the image target.  The next screen is another head scratcher, see attached-

No clue what most of this means or what to do with it.

Reply | Quote

That screen looks different from the version of Macrium Reflect that I have. Is that what you got when you clicked on the “Next” button in post #339388?

I don’t know what the options might be under the drop-down menu in the first button in section 3. However, since you are looking to create just a single one-time image (for now, anyway), I would uncheck the boxes for “Differential” and “Incremental” and then set the number of backups for “Full” at 1. Also, please click on the buttons at right that say “Backups”; I’m curious to know what options they are offering you other than backups.

If the software allows you, leave item 1 at “None” and do nothing with item 2.

Before clicking on “Next,” click on “Advanced Options” down in the left corner. If your version of Reflect is anything like mine, this is where you get to set the compression level (I recommend “medium”) and whether to shut down the PC after the backup is finished (don’t select it to shut down). You can also add a comment line describing the image file. I would also tell it to “verify” the image.

Now you can click on “Next” and get the image creation process going. Come back here if you run into any other glitches or if you have any questions.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Should have added to my previous post- I understand if anyone throws up their hands in annoyance and gives up on this thread.  For those who know all this stuff, I can easily see how frustration can arise.

Reply | Quote

Cybertooth wrote:

That screen looks different from the version of Macrium Reflect that I have. Is that what you got when you clicked on the “Next” button

Yes

Thanks for your patience.  I’ll try your suggestions.

Reply | Quote

Cybertooth wrote:

That screen looks different from the version of Macrium Reflect that I have. Is that what you got when you clicked on the “Next” button in post #339388? I don’t know what the options might be under the drop-down menu in the first button in section 3. However, since you are looking to create just a single one-time image (for now, anyway), I would uncheck the boxes for “Differential” and “Incremental” and then set the number of backups for “Full” at 1. Also, please click on the buttons at right that say “Backups”; I’m curious to know what options they are offering you other than backups. If the software allows you, leave item 1 at “None” and do nothing with item 2. Before clicking on “Next,” click on “Advanced Options” down in the left corner. If your version of Reflect is anything like mine, this is where you get to set the compression level (I recommend “medium”) and whether to shut down the PC after the backup is finished (don’t select it to shut down). You can also add a comment line describing the image file. I would also tell it to “verify” the image. Now you can click on “Next” and get the image creation process going. Come back here if you run into any other glitches or if you have any questions.

Followed all steps.  The “Backup” down arrow offers three choices- Backup, Days, or Weeks.  Items 1 and 2 left as you suggest, as yet no objections from the app.  The Advanced button offers the options you cite, and a couple more that were self explanatory.  About to click “next.”

About 1:42 later- Macrium says “complete” and “Verified”  and Start>Computer shows a large file added to the Seagate drive.  Is the next step just to disconnect it and set it aside, or is there some intermediate step?

1 user thanked author for this post.

Cybertooth

Reply | Quote

Thanks for the great news, @slowpoke47. We’re definitely making progress here.

Now that you have the backup image as a fail-safe, it’s up to you how to proceed. You’ve said that you want to deal with the shutdown issue first. @nightowl suggests installing the backup image on a new HDD, even if it means overwriting the new Linux installation that you haven’t had much of a chance to use yet. That’s a reasonable approach, and among other things it will give you an opportunity to confirm that the backup image will, in fact, work should you need it.

To install this backup image, before swapping out any internal hard disks make sure to create a Macrium Reflect recovery CD/DVD or flash drive, if you don’t already have one. You will need it to restore any HDD images you’ve made.

NightOwl also says to make an image of the Linux installation before overwriting it with the Windows 7 image that you just made. That, too, is sensible; you can even put the Linux image on the new 1TB external HDD that you bought. Since at this point (that is, with the Linux HDD in place instead of the Vista HDD) you cannot boot into Windows 7 to use Reflect, you will need the Reflect recovery disk anyway in order to create the Linux image.

To recap:

1. Make (or make sure that you have) a Reflect recovery media.
2. Remove the Windows 7 HDD and connect the Linux HDD in its place. At this point, you will have a Vista HDD and a Linux HDD inside the PC case.
3. With the 1TB external HDD plugged in, boot into the Reflect recovery media.
4. Using a similar procedure to the one you used to create the Windows 7 image, make an image of the Linux HDD onto the 1TB external drive.
5. Still in the Reflect recovery media (it’s not necessary to reboot, but you can certainly do so), restore the Windows 7 image to the Linux HDD, overwriting it. At this point, you will have your old Vista HDD and the Windows 7 backup inside the PC case.
6. Close the Reflect application, remove the recovery media, unplug the 1TB external HDD, and reboot. The purpose is to see if the Windows 7 image restored to the new HDD will boot just as your original Windows 7 installation does.

At this point, we are in NightOwl’s paragraph that begins, “And, now restore the backup of the Linux HDD…” That’s quite a few steps taken and it’s a good time to see how things have gone before proceeding further.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

Switch out your Win7 HDD for your Linux HDD. (Does Veeam only run under the Windows OS? If so, you may not be able to do the next step(s).)

Yes, it’s on the W7 disk.

Just Lurking wrote:

(I’m not familiar with the Veeam software. Is it an *imaging* program, or is it a *backup* program–there actually is a difference.)

AFAIK, backup only.

What do you think of these two suggestions?

https://answers.microsoft.com/en-us/windows/forum/all/task-host-window-will-not-let-me-shut-down/ef7af008-fabe-4671-b51f-a9e31ca2e427

https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/shutdown-and-restart-prevented-by-task-host-window/31405c48-d000-4599-9a66-78c574d23d8f

Reply | Quote

Cybertooth wrote:

Thanks for the great news, @slowpoke47. We’re definitely making progress here. Now that you have the backup image as a fail-safe, it’s up to you how to proceed. You’ve said that you want to deal with the shutdown issue first. @nightowl suggests installing the backup image on a new HDD, even if it means overwriting the new Linux installation that you haven’t had much of a chance to use yet. That’s a reasonable approach, and among other things it will give you an opportunity to confirm that the backup image will, in fact, work should you need it. To install this backup image, before swapping out any internal hard disks make sure to create a Macrium Reflect recovery CD/DVD or flash drive, if you don’t already have one. You will need it to restore any HDD images you’ve made. NightOwl also says to make an image of the Linux installation before overwriting it with the Windows 7 image that you just made. That, too, is sensible; you can even put the Linux image on the new 1TB external HDD that you bought. Since at present you cannot boot into Windows 7 to use Reflect, you will need the Reflect recovery disk anyway in order to create the Linux image. To recap:

1. Make (or make sure that you have) a Reflect recovery media.
2. Remove the Windows 7 HDD and connect the Linux HDD in its place. At this point, you will have a Vista HDD and a Linux HDD inside the PC case.
3. With the 1TB external HDD plugged in, boot into the Reflect recovery media.
4. Using a similar procedure to the one you used to create the Windows 7 image, make an image of the Linux HDD onto the 1TB external drive.
5. Still in the Reflect recovery media (it’s not necessary to reboot, but you can certainly do so), restore the Windows 7 image to the Linux HDD, overwriting it. At this point, you will have your old Vista HDD and the Windows 7 backup inside the PC case.
6. Close the Reflect application, remove the recovery media, unplug the 1TB external HDD, and reboot. The purpose is to see if the Windows 7 image restored to the new HDD will boot just as your original Windows 7 installation does.

At this point, we are in NightOwl’s paragraph that begins, “And, now restore the backup of the Linux HDD…” That’s quite a few steps taken and it’s a good time to see how things have gone before proceeding further.

Thanks for that upvote.  Unable to go further with this before tomorrow, but will proceed then.  Again, many thanks.

1 user thanked author for this post.

Cybertooth

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

About 1:42 later- Macrium says “complete” and “Verified” and Start>Computer shows a large file added to the Seagate drive.

Congratulations! Sounds like you have created your first backup image. Two *Thumbs Up*!

Slowpoke47 wrote:

Is the next step just to disconnect it and set it aside, or is there some intermediate step?

I think your eyes are glazing over! I think you did not see my outline of what to do next in the process of verifying that you have a backup + Restore procedure in place that you can rely upon:

Just Lurking wrote:

Here’s an outline:

With your Vista HDD and Win7 HDD installed, create a whole drive backup of the Win7 HDD.

Switch out your Win7 HDD for your Linux HDD. (Does Veeam only run under the Windows OS? If so, you may not be able to do the next step(s).)

Create a whole drive backup of the Linux HDD. (One really needs the ability to boot to some sort of *recovery media* that allows for backup and/or restore of a backup to whatever HDD is needed. Maybe you can boot to the Vista OS and use your Veeam backup software from there?)

Now, restore the backup of your Win7 HDD to the Linux HDD. Now, re-boot and can you select the Win7 OS and bring up that OS successfully? If yes, your backup and restore functions are working as they should. If not, then something is missing or not configured quite right and needs to be worked on.

And, now restore the backup of the Linux HDD to the HDD that has the restored Win7 on it. Re-boot and does Linux come up successfully. If yes, your backup and restore functions are working as they should.

And finally, replace the Linux HDD with the Un-Touched Win7 HDD and you are right back where you started from, and if everything worked as planned, you now know that your backup and restore functions are operational, and you can count on them in a disaster situation!

If any of these steps did not work, then we need to troubleshoot what’s not working.

Note, that throughout these testing procedures, your original Win7 HDD is never at *risk*–it is removed from the system for safe keeping, and we never attempt to restore to your *production* Win7 HDD–i.e. the HDD you currently use for everyday computing.

Did this make sense? Questions?

This outline is *incorrect*–I made it when I thought you were going to be using the Veeam backup software–but, now that it’s the Macrium Reflect software, I need to recommend some slight changes.

Also, Cybertooth also made a similar recommendation in his outline:

Cybertooth wrote:

To recap:

Make (or make sure that you have) a Reflect recovery media.

So, bottom line–you’re not done yet.

And, there are some lingering fine points that could be done to make the image creation and backup a little more organized and understandable. I’ll go over that tomorrow.

But first–are you able to boot your system from an optical disc or flash drive to any sort of recovery media–i.e. have you done that before? If not, now’s the time to say so, and get coaching on how to do that–it will become necessary if you want to be able to use your backup image file to restore your harddrive with the OS you have backed up.

I don’t use Macrium software myself–I use something else that uses a Linux boot disc to load the recovery software. But, Cybertooth appears to be using Macrium software and should be able to help you to create the Recovery Media for Macrium. Then we can cover how to boot to that Recovery Software.

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

Thank you for your patience.  I really am doing my best, but, as stated, my anecdotal computer skills have plenty of holes.

Just Lurking wrote:

But first–are you able to boot your system from an optical disc or flash drive to any sort of recovery media–i.e. have you done that before? If not, now’s the time to say so, and get coaching on how to do that–it will become necessary if you want to be able to use your backup image file to restore your harddrive with the OS you have backed up.

My only experience with this has been to download the Mint OS to a flash drive.  The format was then changed to “bootable” but I was merely a spectator.  Not sure exactly how, but this bootable file acquired the actual Mint OS from the Mint website, now (I think) correctly set up on the new hard drive.

But there is this warning in the Macrium user guide.  Does this have any bearing on your guidance?

<p class=”title”>Important</p>

 Windows cannot boot from a USB connected drive. This is a restriction imposed by Windows. If you clone your system disk to a USB connected external drive then, to boot your clone,  the physical disk must be removed from the USB caddy and attached to your Motherboard SATA port.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

But there is this warning in the Macrium user guide. Does this have any bearing on your guidance?

Important

Windows cannot boot from a USB connected drive. This is a restriction imposed by Windows. If you clone your system disk to a USB connected external drive then, to boot your clone, the physical disk must be removed from the USB caddy and attached to your Motherboard SATA port.

Nope–does not apply to anything we are currently trying to do. Some folks have what’s called a harddrive (HDD) *USB caddy*–it’s a device that allows one to place a HDD that one might normally place in a desktop tower into the *caddy*. With most imaging software, one can create a *clone* directly from one HDD to another–i.e. an exact copy of a source HDD–say your Win7 HDD that’s in your tower to the HDD that’s in the *caddy*. Technically, because it’s an exact copy, some folks would like to think that the HDD should be bootable while still in the *USB caddy*, just like the Win7 HDD that’s in the tower. But, a *USB caddy* through a USB controller just does not have the capacity or speed to allow Windows to boot and operate. (One can boot from a USB device–i.e. external HDD, thumb flash drive, USB optical drive, … but, it can not be a standard Windows OS that’s booted.) But, if that HDD in the caddy is removed and put in place of the HDD in the tower–it should boot just like the original HDD that it was *cloned* from. So, that’s what that warning is all about.

What you need to do, is to be able to *access* the image file that is now stored on the USB HDD and copy that image file from the USB HDD to the internal HDD in your tower to make a HDD that is exactly like the data on the date you created the backup image. When you restore that image to the HDD, everything on that HDD is wiped out and replaced with the data from your image file.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

What do you think of these two suggestions?

https://answers.microsoft.com/en-us/windows/forum/all/task-host-window-will-not-let-me-shut-down/ef7af008-fabe-4671-b51f-a9e31ca2e427

https://answers.microsoft.com/en-us/windows/forum/windows_8-performance/shutdown-and-restart-prevented-by-task-host-window/31405c48-d000-4599-9a66-78c574d23d8f

So, I looked at these two references.

The first one would have you edit the Registry to tell Windows how long to wait for a program to respond to your shut down request (WaitToKillServiceTimeout)–if the program has not responded after a certain length of time, then Windows is supposed to *force* a shut down. In theory, there’s already a time limit that Windows is supposed to wait, and should then be *killing* any non-responding program–but, obviously it’s not able to successfully stop the non-responding program. So, simply shortening the wait time will probably have the same result–failure to close out the non-responding program.

The second one has several troubleshooting suggestions–they are actually suggestions you have already been given earlier in this thread: 1. Run the Power Options Troubleshooter, 2. Place the computer in *Clean Boot* mode (this is almost the same as my recommendation to possibly *booting to Safe Mode* mentioned previously, 3. Look at *Event Viewer* to see if there are any error codes that might help direct one to a possible problem to be corrected–also mentioned previously.

Both of these links might be of importance–we just have not got to that point yet–but, let’s finish getting your Imaging Software figured out and operational first.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

But, a question- won’t the system image also capture the boot and shutdown problems?

Yes, absolutely! But, that’s why you will make new images as time goes by and you gradually correct and fix whatever problems you may be having.

You then begin to delete obsolete image backups when needed.

Creating image backups is a moving target!

Reply | Quote

Slowpoke47 wrote:

Make (or make sure that you have) a Reflect recovery media.

Just to be sure, this would be the system image I made yesterday?

Slowpoke47 wrote:

With the 1TB external HDD plugged in, boot into the Reflect recovery media. Using a similar procedure to the one you used to create the Windows 7 image, make an image of the Linux HDD onto the 1TB external drive.

I do have the bootable flash drive that retrieved the Mint OS and loaded it successfully on the new HD.

1.  Am I still better off to image it?

2.  And, if so, do I need to worry about any conflict (or whatever) between the two images?

Slowpoke47 wrote:

Still in the Reflect recovery media (it’s not necessary to reboot, but you can certainly do so), restore the Windows 7 image to the Linux HDD, overwriting it. At this point, you will have your old Vista HDD and the Windows 7 backup inside the PC case.

At this point, are both HD’s plugged in, and if so, how does the restore go to the correct disk?

 

Reply | Quote

@slowpoke47, here are the answers to the questions you had:

Just to be sure, this would be the system image I made yesterday?

No, the “recovery media” is the CD/DVD or flash drive that you would create from within Macrium Reflect, to then boot into when you’re ready to restore an image to a HDD.

I do have the bootable flash drive that retrieved the Mint OS and loaded it successfully on the new HD.

1.  Am I still better off to image it?

2.  And, if so, do I need to worry about any conflict (or whatever) between the two images?

If the Mint that you loaded onto the new HDD is identical to the one that’s on the flash drive (meaning: if you didn’t make any changes to the Mint that’s on the HDD, say by installing additional software or updates, or getting work done on it), then I would say that you do NOT need to image that Mint HDD and you can skip that step.

Regarding possible “conflicts between the two images,” refer back to the paragraph just above. If the image that’s on the new HDD is in any way different from the one that’s on the flash drive, then you MAY want to image the Mint that’s on the HDD. But if you haven’t made any changes, or if the changes are minimal or inconsequential, then you could legitimately decide that keeping those few changes isn’t worth the extra effort of making that image. Then when you’re ready to install Mint for good, you can simply reload what you have on the flash drive onto the new HDD, gleefully overwriting anything that’s on it.  🙂

The main thing at this stage is to make sure that you can make a Windows 7 image that will boot the same way as your current Windows 7 HDD does when Vista is in place. Then in theory we can work either on the image or on the original Windows 7 installation, to try to fix your shutdown problem as well as the “no bootup without Vista” issue.

EDIT: I overlooked your third question:

At this point, are both HD’s plugged in, and if so, how does the restore go to the correct disk?

Yes, as Step 5 specifies, inside the PC case you will have the Vista HDD and the new internal HDD. You will restore the Windows 7 image that you made earlier onto the new HDD, overwriting the Linux Mint installation.

The way to restore the image goes roughly as follows: Boot into the Macrium Reflect recovery disk that you have made or will need to make. Then, in the left panel, select the “Restore” tab. The external 1TB HDD should still be plugged in, so Reflect will show you a list of available images to be restored from the external HDD. Make sure to select the correct desired image from the right disk, and also to tell Reflect the HDD where you wish to restore the image to.

Reflect may show you multiple partitions on the Windows 7 image. Make sure that they are checked, then start the restoration process.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

So, we need to continue with the needed steps to complete your image creation and the ability to restore images successfully.

Just Lurking wrote:

This outline is *incorrect*–I made it when I thought you were going to be using the Veeam backup software–but, now that it’s the Macrium Reflect software, I need to recommend some slight changes.

I’m not going to make another outline. My impression is that you get *overwhelmed* by too much information. So, I’m going to introduce one step only at a time. We can discuss it and perform whatever intermediate steps are needed. But, until the step is completed, we should not worry about any future steps until we get there.

So, Step #1:

Create Bootable Recovery Media: here’s what Macrium Reflect says: https://knowledgebase.macrium.com/display/KNOW72/Rescue+Environment

Caution

The first thing you need to do after installing Macrium Reflect is create Rescue Media

Why?:

If you lose your Windows operating system, you can start your PC using Macrium Reflect rescue media on CD, DVD, or USB stick. This makes creating rescue media the first thing you need to do with Macrium Reflect. It contains a bootable, lightweight version of Windows and a full version of Macrium Reflect.

Why does this rescue media need to be tested?:

The default drivers placed on the bootable rescue media may not be the needed drivers for your computer system, the drivers may not be compatible, or other issues–you need to know that ahead of time so the problems can be corrected, and you can access your image file(s) on your external USB HDD, and demonstrate that you can restore those images to your HDD.

Slowpoke47 wrote:

My only experience with this has been to download the Mint OS to a flash drive. The format was then changed to “bootable” but I was merely a spectator. Not sure exactly how, but this bootable file acquired the actual Mint OS from the Mint website, now (I think) correctly set up on the new hard drive.

It’s not really important *how* it became bootable, or how the Mint OS was loaded onto that flash drive–what’s missing from the above statement is *Yes, I used that flash drive to boot my computer, by-passing the Windows boot sequence that shows the OS selection for Vista and Win7 OSs, and proceeded to install Mint onto the blank HDD.*

Basically, are you comfortable with the ability to boot either a bootable flash drive or bootable CD/DVD, by-passing the Windows bootup sequence? When you create the Macrium Rescue Media, you will have to select to either create a flash drive or CD/DVD as your bootable media.

Here’s the Macrium v7.2 User Guide–all 550 pages worth. Yikes–that’s a lot to memorize! They seemed to have forgotten to mention how to get to their *Create Rescue Media* section, but it looks like you select from the top Menu list the *Other Tasks* item, and then I think it will list *Create Rescue Media … * in the drop down menu.

In the User Guide–you will find a *boat load* of possible options to choose from to *customize* the bootable rescue media. My advise–put on some blinders and ignore all of those, at least for now. Just accept the *default* settings that the Macrium software suggests. We will then test out the results and only worry about all those optional choices if for some reason we need to!

Here’s a Macrium knowledge base summary: https://knowledgebase.macrium.com/display/KNOW72/Creating+rescue+media

Macrium Rescue Media Builder provides a simple interface to allow for quick rescue media generation by selecting where the rescue media will be generated and then clicking a ‘Build’ button.

All options for the rescue media will be suitably defaulted based on existing rescue media builds and a scan of the operating system environment.

Choose a rescue media target under ‘Select Device’
Click ‘Build’

So, just *Select Device*–either Flash Thumb Drive, or CD/DVD Burner, and then select *Build*–you of course have to supply the flash drive or recordable CD/DVD.

You should now be done with *Step 1*!

Questions? Discussions? Or let me know when you’re ready for step 2.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

The first thing you need to do after installing Macrium Reflect is create Rescue Media

How can I tell if this Rescue Media will fit on a 700MB CD-R?

Reply | Quote

It does; that’s exactly what I have.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Just Lurking

Reply | Quote

@ Slowpoke47

(Just for the record, you need to go back to Cybertooth’s original Reply, and quote it from there, otherwise, as you can see, the forum software is showing that the statement is coming from you, and not Cybertooth–which is technically true–you’re quoting something from *your* Reply and not Cybertooth’s.)

Slowpoke47 wrote:

Just to be sure, this would be the system image I made yesterday?

Nope. Yesterday’s system image is your *Image File* of the partitions on your HDDs. Reflect Recovery Media is the bootable flash drive or bootable CD/DVD that allows you to boot to your computer with a Windows *Lite* version that will also have the Macrium Reflect software so you can access your *Image File*, and you will not actually be booted to any other OS, such as your Win7, Win Vista, or Linux OS.

Slowpoke47 wrote:

I do have the bootable flash drive that retrieved the Mint OS and loaded it successfully on the new HD.

1. Am I still better off to image it?

2. And, if so, do I need to worry about any conflict (or whatever) between the two images?

I would recommend that you not try to follow either my outline of steps (multiple steps in one outline), or Cypertooth’s–you’re not quite ready yet. Let’s do one step at a time, I will explain the next step and try to explain why as we go. And I will be asking you questions as we go to make sure you understand, and what I’m recommending makes sense to you.

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

How can I tell if this Rescue Media will fit on a 700MB CD-R?

I can’t guarantee this because I’ve not used the Macrium software, but most likely if there is a size problem, the software will notify you of the issue, and probably ask for larger capacity media.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Slowpoke47 wrote:

How can I tell if this Rescue Media will fit on a 700MB CD-R?

NightOwl- our posts “crossed” and you may not have seen this.  I have blank CD’s on hand but will go out and buy something larger if needed.

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

How can I tell if this Rescue Media will fit on a 700MB CD-R?

I can’t guarantee this because I’ve not used the Macrium software, but most likely if there is a size problem, the software will notify you of the issue, and probably ask for larger capacity media.

OK, I’ll try it and see.

Reply | Quote

Slowpoke47 wrote:

NightOwl wrote:

@ Slowpoke47

Slowpoke47 wrote:

How can I tell if this Rescue Media will fit on a 700MB CD-R?

I can’t guarantee this because I’ve not used the Macrium software, but most likely if there is a size problem, the software will notify you of the issue, and probably ask for larger capacity media.

OK, I’ll try it and see.

The CD is hopelessly inadequate- Macrium calls for another one with about 5% completed by their bar graph.  I’ll go out and get something more suitable.

Reply | Quote

That would suggest that the Macrium Reflect recovery disk has increased in size considerably between the time that “my” version of Reflect was released and the time that yours came out. Wouldn’t surprise me.

Be that as it may, try putting the Reflect recovery medium on a blank DVD instead of a CD.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

The CD is hopelessly inadequate- Macrium calls for another one with about 5% completed by their bar graph.

Really! That’s weird. Cypertooth replied a short while ago saying that he is using a CD for the Recovery Media:

Cybertooth wrote:

It does; that’s exactly what I have.

Could you take a screenshoot of the setup page showing the settings being used to create the Rescue Media? Sounds like something isn’t going as expected ….

Alternatively, you can always re-create the Linux Mint installation flash drive if you ever need it–if we create an image backup of the Linux HDD, then you probably will never need the installation files again. But, you could use that flash drive as apposed to using an optical disc, and avoid a trip and the expense of purchasing other optical discs.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Reads like @Slowpoke47 is creating an image instead of a rescue disk (5% on a 700mb CD, gives a clue) given that W7 x64 is approx 15gb or greater when up to date.

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Cybertooth

Cybertooth wrote:

That would suggest that the Macrium Reflect recovery disk has increased in size considerably between the time that “my” version of Reflect was released and the time that yours came out. Wouldn’t surprise me.

Can you check, how much data is on your Rescue Media disc.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Yes, it’s only 175MB:

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Just Lurking

Reply | Quote

@ Cybertooth

Yeah, there’s no way the Rescue Media software and drivers have outgrown a 700 MB CD.

But, as you probably have seen already, we think we found the issue.

Thanks for reporting back.

Reply | Quote

Thanks all.  32GB flash drive installed and ready.  Macrium has found it.  The screen below generates with the flash in place and selected, and clicking on the blue Windows icon in the upper left pane. OK so far?  Anything else before clicking Next at bottom?

Reply | Quote

Just Lurking wrote:

@ Cybertooth

Cybertooth wrote:

That would suggest that the Macrium Reflect recovery disk has increased in size considerably between the time that “my” version of Reflect was released and the time that yours came out. Wouldn’t surprise me.

Can you check, how much data is on your Rescue Media disc.

Can’t do that until this operation finishes.  It is a large file.  I think I’m now good to go, as long as I head in the right direction.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

OK so far?

Nope! You are in the *Image Creation* screen–not the *Rescue Media Creation* screen.

Hang on for a few minutes while I try to find a screen shot …

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Can’t do that until this operation finishes.

Actually, the question was directed to Cybertooth.

If you have not already started down the wrong path–just hang on for a couple minutes until I try to find a couple screenshots.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

It will fit on a 700mb CD as already explained here #339678

Keeping IT Lean, Clean and Mean!

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

Can’t do that until this operation finishes.

Actually, the question was directed to Cybertooth. If you have not already started down the wrong path–just hang on for a couple minutes until I try to find a couple screenshots.

3:56 PM, have not done anything further since that s/shot.  Macrium waiting for further input.

Reply | Quote

@ Slowpoke47

Here’s your screenshoot, but I have circled the Menu item you need to select. You have selected the Icon button for *Create an Image File*.

After you select the Menu Item *Other Tasks*, you then select *Create Rescue Media*

Things should go quite a bit better if you follow those instructions!

Go back and review my previous instructions:

Just Lurking wrote:

Here’s the Macrium v7.2 User Guide–all 550 pages worth. Yikes–that’s a lot to memorize! They seemed to have forgotten to mention how to get to their *Create Rescue Media* section, but it looks like you select from the top Menu list the *Other Tasks* item, and then I think it will list *Create Rescue Media … * in the drop down menu.

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

3:56 PM, have not done anything further since that s/shot. Macrium waiting for further input.

Hit the *Cancel* button at the bottom of that screen.

Go to the *Create Rescue Media*.

Select your optical drive with a CD inserted.

Press *Build*

Don’t press any other buttons or options except what’s needed to complete the burning of the CD!

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

Started over.  Blank CD in PC.  My Macrium page layout is a little different, but you can see by the s/shot that there is an option “Create bootable rescue media” which generates the pop-up in the s/shot.  Haven’t done anything else, but I see in the automatically highlighted option is the text “add/change the boot menu” and near the top “Click build to update.”  Should I do that?

Reply | Quote

@Slowpoke47, just a quick NOTE: you are aware that you are using the trial ‘Home’ version of macrium Reflect. (HINT, HINT, NUDGE, NUDGE)
The ‘Free’ version is adequate for your purpose unless you wish to pay for the privilege of using it. 😉

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@slowpoke47, from your screenshot select the middle option, CD/DVD Burner. That’s where you want your rescue/recovery media to go.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

3:56 PM, have not done anything further since that s/shot. Macrium waiting for further input.

Hit the *Cancel* button at the bottom of that screen. Go to the *Create Rescue Media*. Select your optical drive with a CD inserted. Press *Build* Don’t press any other buttons or options except what’s needed to complete the burning of the CD!

Got it.

 

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

3:56 PM, have not done anything further since that s/shot. Macrium waiting for further input.

Hit the *Cancel* button at the bottom of that screen. Go to the *Create Rescue Media*. Select your optical drive with a CD inserted. Press *Build* Don’t press any other buttons or options except what’s needed to complete the burning of the CD!

Did exactly this.  After running several minutes, got pop-up, CD invalid.  This is a new, out-of-the-box disc.  I do have a couple of 32GB flashd drives, just ran out to get them earlier.  Should I try again with one of those?

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

After running several minutes, got pop-up, CD invalid.

I think we all have had a bad CD now and again. No way to know if that’s a 1-off error or if other discs in the box would give the same problem. Have you used other CDs from this box successfully. I know I’ve had a batch of CDs in the same box and most of them refused to work, at least on my optical drive. Switch brands, and everything was working as it should again. So, don’t know ….

Slowpoke47 wrote:

I do have a couple of 32GB flashd drives, … Should I try again with one of those?

Your call–probably will work just fine. You only need less than 1 GB, so lots of wasted space. But, you could try different optical discs in the future (or more right now that are in the box) to see if the problem persists. Once you have a bootable disc, you can re-use the flash drive for what ever purpose. I know some folks who swear they will only use flash drives and not CDs or DVDs–and that’s fine. You could purchase a 2 GB flash drive and use that to create your Rescue Media in the future, and again re-use the 32 GB flash drive for what ever you wish.

You could try one more optical disc. If it fails, then switch to the flash drive–at least for testing for now. Then switch to something else in the future.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

Cybertooth wrote:

@slowpoke47, from your screenshot select the middle option, CD/DVD Burner. That’s where you want your rescue/recovery media to go.

That’s just what I did. See my last post.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Perhaps taking the PC to a repair shop is the best way now that you have tried many different ways without a desirable result? Something like Best Buy “Geek Squad.” Maybe others could recommend a better place; if someone does, I would be interested to know about it as well.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Somewhere better than Geek Squad?

That would be somewhere other than Geek Squad! (My opinion only).

Chain repair places tend to be just terrible.  Local places can be too, but there’s the chance they are businesses started by a hobbyist or otherwise capable person who has an interest and not just some chain place trying to find warm bodies to “train.” You may run into one that has someone competent, but you won’t know beforehand, nor can you guarantee that the good guy would be the one to work on it.

Not only that, but Best Buy has been caught snooping through people’s hard drives to find something incriminating to hand over to the FBI.  That should be ruled unconstitutional under the Fourth Amendment, but it hasn’t been thus far.

Unfortunately, that means you will have to do some research locally.  It’s hard to even know if customer reviews on any given site are accurate, as they’re often fake, either good or bad.  The Better Business Bureau may have some useful info, but even then, complaints can be faked.

I concur with Microfix’s advice here.  The goal is to create a bootable drive (or disc) to write a bootloader to the Windows 7 hard drive.  No need to pull the eject handle yet… this is all part of the process of getting the bootable written.

As for paying for it… that’s a personal choice.  As long as you’re using the free one within Macrium’s terms, it’s up to you.  It is good to support companies who make stuff you like.

I’d buy any (consumer-oriented, reasonably priced) Linux software that offered live backup functionality like all the Windows ones do (Linux has long had the ability to do shadow copies like Windows), but so far, none exist that I know of.  I thought initially that Terabyte NovaBackup had that, but I was wrong… it just creates a bootable disc or USB too.

Actually, Acronis has a backup program for Linux… but it costs $500 per year, because only businesses who consider that kind of thing to be part of the cost of running business run Linux.  Of course!

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

2 users thanked author for this post.

OscarCP, Cybertooth

Reply | Quote

Try a different CD or two from the same package, sometimes they just come out bad (it’s happened to me).

If you try several different CDs at random and none of them works, then try one of the 32GB flash drives.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

Can you check, how much data is on your Rescue Media disc.

Just checked- that file is 69.5GB.  Currently cancelled out of Macrium and removed the rejected CD.  Not sure what next step should be.

Reply | Quote

I suspect you were looking at the size of the Windows 7 backup image that you had created. You haven’t yet created the rescue media disc. That one will come out to much less than 1GB.

Pop a new CD back in, relaunch Reflect, and start the process of creating rescue media again.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

You can’t use a CD you’ve already burned. You have to use a new CD.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Just checked- that file is 69.5GB.

What disc are you looking at, and how have you looked at it. Maybe a screenshot of the method you’re using to see the size of the file on disc.

Even if this is the previous disc that you attempted to put an image file on, there is no CD that will hold 69.5 GB of data–max is about 700MB to 750MB. Even a DVD is only about 4.3 GB or so at most.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

Try a different CD or two from the same package, sometimes they just come out bad (it’s happened to me). If you try several different CDs at random and none of them works, then try one of the 32GB flash drives.

ok, will do.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Cybertooth wrote:

I suspect you were looking at the size of the Windows 7 backup image that you had created. You haven’t yet created the rescue media disc. That one will come out to much less than 1GB. Pop a new CD back in, relaunch Reflect, and start the process of creating rescue media again.

That wpost was in answer to an earlier question by NightOwl.  Just about to try again with a different new CD.

Reply | Quote

Once I had problems with the disk drive reading or burning DVDs; I was advised to use +RW type, and that took care of my problem. But I still think that taking the PC to a place where people with the necessary expertise can look at it directly might be something to be considered as well.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

OscarCP

OscarCP wrote:

… I still think that taking the PC to a place where people with the necessary expertise can look at it directly might be something to be considered …

Oh, Oscar, where’s that sense of adventure?!

But, seriously–always something to be considered.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

Going to a tech shop is definitely a viable option.

However, none of the participants has yet run out of ideas or patience!  🙂

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

PKCano wrote:

You can’t use a CD you’ve already burned. You have to use a new CD.

Thanks for responding.  Yse, I do know that.  I’m using new discs.

Reply | Quote

Rescue media completed, no problem.  Looks like Cybertooth had the right answer.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Thanks @slowpoke47, but I would like to share the credit with @NightOwl.  🙂

Let us know how things go on the next step.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Whew! Boy, that took a whole lot more *discussion* than I anticipated!

Wait ’til I tell you the steps for *Step 2*! 😉

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

@ Slowpoke47

Slowpoke47 wrote:

Just checked- that file is 69.5GB.

What disc are you looking at, and how have you looked at it. Maybe a screenshot of the method you’re using to see the size of the file on disc. Even if this is the previous disc that you attempted to put an image file on, there is no CD that will hold 69.5 GB of data–max is about 700MB to 750MB. Even a DVD is only about 4.3 GB or so at most.

Didn’t mean to confuse the issue.  That file is on the ext. drive that ran yesterday- that’s the file size of the system image, which is what I thought you were asking in that post.  In any case, the second attempt at the recovery disc went well.

 

Reply | Quote

Just Lurking wrote:

@ Slowpoke47 Whew! Boy, that took a whole lot more *discussion* than I anticipated! Wait ’til I tell you the steps for *Step 2*! 🙂

Can’t begin to express my appreciation for everyone’s patience.  After this I may go and look for a job digging ditches, or suchlike.  OK, I’m ready to continue.  Hope to make you all proud, or at least, atone for past gaffes!

2 users thanked author for this post.

Cybertooth, Elly

Reply | Quote

Microfix wrote:

@slowpoke47, just a quick NOTE: you are aware that you are using the trial ‘Home’ version of macrium Reflect. (HINT, HINT, NUDGE, NUDGE) The ‘Free’ version is adequate for your purpose unless you wish to pay for the privilege of using it. 🙂

I’m not one who expects value for nothing, computer-wise or otherwise.  Once I get out of this mess, if it looks like I can benefit from (and understand) the Macrium app I’ll pony up.

Reply | Quote

I pay if an available free version is any good and of ‘value’ to me as I have done with many freemium utilities. I don’t use macrium reflect and don’t need it which is why I suggested the free version to start with, it’s your pony and PC 🙂

Keeping IT Lean, Clean and Mean!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

FWIW- While burning the rescue CD I noticed in a couple of spots on the Macrium screen the checkable option to create/repair boot function.  Just curious if there may be something to pursue there.  If yes, it still may not work with the Vista drive in place, as Vista, as the original OS, has subsumed the W7 boot function.

 

Reply | Quote

If the checkable option to create/repair boot function is in reference to your Windows 7 HDD, then yes, it may be worth a shot trying that. But first let’s finish these other steps, to make sure that youir Windows 7 backup works acceptably.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

While burning the rescue CD I noticed in a couple of spots on the Macrium screen the checkable option to create/repair boot function. Just curious if there may be something to pursue there.

You may not have noticed, but in the previous thread you started regarding not being able to boot you Win7 system after installing the Linux Mint OS, there were several mentions of perhaps Macrium might be able to fix a non-boot situation.

I have looked that up and from what I read, it sounded like Macrium could *repair* a non-boot situation, but it did not mention the ability to *move* the boot files from one OS to another (which is what you need done), and it did not mention being able to move boot files from one HDD to another HDD. Just because it does not specifically say it can (or can’t) do those things, doesn’t mean it can’t do those things–but it leaves it open to doubt. If other techniques don’t work, I was keeping the Macrium option on the back burner for a possible attempt.

But, we’ll leave that for the moment pending completing the imaging restore function trials coming up next.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

@ Slowpoke47

So, let me know if your ready for *Step 2*!

In preparation for *Step 2*, there’s a question buried way back in this thread that needs an answer to:

Just Lurking wrote:

Slowpoke47 wrote:

My only experience with this has been to download the Mint OS to a flash drive. The format was then changed to “bootable” but I was merely a spectator. Not sure exactly how, but this bootable file acquired the actual Mint OS from the Mint website, now (I think) correctly set up on the new hard drive.

It’s not really important *how* it became bootable, or how the Mint OS was loaded onto that flash drive–what’s missing from the above statement is *Yes, I used that flash drive to boot my computer, by-passing the Windows boot sequence that shows the OS selection for Vista and Win7 OSs, and proceeded to install Mint onto the blank HDD.*

Basically, are you comfortable with the ability to boot either a bootable flash drive or bootable CD/DVD, by-passing the Windows bootup sequence?

Just for the record, I realize you had removed both the Win7 HDD and the Vista HDD, so there was no longer any Windows based bootable media on the system when you used that Linux flash drive to install Linux to the new HDD. You then added back the Win7 HDD and discovered that you could not boot that Windows OS any longer. (Yes, we’re going to fix that–after we know you can recover from a *disaster*.)

Computers can load and run *lots* of different OSs. There’s DOS (Disk Operating System) could run programs from a floppy disk), there’s Linux (one can run Linux from a bootable CD–does not have to be *installed* on the HDD), there’s WinPE (Windows Preinstallation Environment), there’s WinRE (Windows Recovery Environment), there’s Macrium Rescue Media (well, to be honest, the Macrium Rescue Media is based on the WinPE or WinRE–so the Rescue Media is not a separate OS that a computer system can run. There are countless others as well.

But, a fairly common theme to many *Rescue Media* is that you can boot to that media before Windows has a chance to boot, you can load various programs for testing and evaluating problems, and often times you can make changes to the data on the HDD or the OS system files to correct a problem, etc.

Have you booted any forms of *Rescue Media* in the past, that boots prior to Windows booting, booting either from a flash drive or an optical disc?

Do you know how to boot from a flash drive or optical media as indicated above?

You answers will determine what we do next in *Step 2*.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

It’s not really important *how* it became bootable, or how the Mint OS was loaded onto that flash drive–what’s missing from the above statement is *Yes, I used that flash drive to boot my computer, by-passing the Windows boot sequence that shows the OS selection for Vista and Win7 OSs, and proceeded to install Mint onto the blank HDD.*

Just so I don’t use the wrong terminology- here’s what I did (mostly as you recount)- Once I had the flash drive, no Windows OS’s were involved.  The new blank HD was installed and connected and the W7 HD was in place but unplugged.  I plugged in the flash drive and started the PC, which had only one option- that flash drive.  The PC started and had to boot from that flash drive, nothing else was available.

So if that is booting from a flash drive, the answer is, yes, I did that.

The computer loaded Mint from the Mint site, I was just a spectator.

Reply | Quote

Microfix wrote:

I pay if an available free version is any good and of ‘value’ to me as I have done with many freemium utilities. I don’t use macrium reflect and don’t need it which is why I suggested the free version to start with, it’s your pony and PC 🙂

I’m with you.  The help I’ve received here has been invaluable- as you can see, I am subscribed.

Reply | Quote

Cybertooth wrote:

If the checkable option to create/repair boot function is in reference to your Windows 7 HDD, then yes, it may be worth a shot trying that. But first let’s finish these other steps, to make sure that youir Windows 7 backup works acceptably.

Something to keep in mind, anyway.  At some point I’ll need that.

Reply | Quote

At this point I want to acknowledge the generous amount of time that everyone who has posted has spent on my behalf.  I believe that the expertise here is superior to anything I might find in a repair shop, and you never know how good any particular tech might be.  In addition, there are files on this PC that we do not wish to risk in the hands of a third party- financial records and such.

I’m now called away and will sign off- thanks again!

1 user thanked author for this post.

Cybertooth

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

So if that is booting from a flash drive, the answer is, yes, I did that.

But, my question had a two part sentence–part one was booting from a bootable flash drive (or a bootable CD/DVD), and part two was *did you by-pass the Windows boot sequence*.

Having all drives where Windows is installed that are removed and/or disconnected does not count as *by-passing* the Windows boot sequence.

In order for Rescue Media to be available to work with Windows installations for repair, image creation, or image restores, the Windows HDDs have to be installed, connected, and running.

So, the correct answer is *No, apparently you have not used Rescue Media to boot your system, while by-passing the Windows boot sequence*.

A couple more questions:

1. I have seen you make reference to the BIOS. Are you referring to the System BIOS, and are you talking about being able to enter the System BIOS Setup program that you can access during initial boot by hitting a certain key or key combination?

If *Yes*–are you familiar with the Boot Priority Sequence (Name may vary from BIOS to BIOS, but it lists the 1st, 2nd, 3rd, etc. Boot Device in whatever order you have selected. Do you know what the priority listing for your devices is/are? It might be 1st=optical drive, 2nd=Vista HDD, 3rd=USB Flash Drive, 4th=Win7 HDD …..

If you don’t know the order–reboot and enter the BIOS and copy down that priority list. Report back here with that listing.

2. During bootup, there usually is a *Boot Menu* that one can access–this is not the BIOS Priority List. Instead this is the listing of all bootable devices that are or may be available during boot. My system uses F8 to bring that menu up. I can then select (and this over-rides the BIOS Boot Priority List) which ever HDD I want to choose, which optical drive, which USB drive (flash and/or external HDD), floppy drive if installed, USB optical drive, USB Floppy Drive,–so a bunch of choices. Are you familiar with this boot menu?

Usually the special key to bring up the *Boot Menu* is shown for 5-10 seconds during initial boot (on my system it’s along the bottom of the screen), and you have to push that key soon after that key is shown in order to get it to respond. I sometimes repeatedly press the key. It usually takes a brief period before it finally responds.

Record that Key, and report back here with that information once you have it.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

It looks like the Dell Inspiron 519 uses the f12 key to choose a boot device.

Mark

Win 10 home - 22H2
Attitude is a choice...Choose wisely

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ mledman

mledman wrote:

It looks like the Dell Inspiron 519 uses the f12 key to choose a boot device.

Ah–good, thanks for that.

@ Slowpoke47

Does that info match your observations on your system?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

So, the correct answer is *No, apparently you have not used Rescue Media to boot your system, while by-passing the Windows boot sequence*.

That is correct, in the Linux sequence I described, as stated, all went on without input from me to get started.

Yes, I am aware of the BIOS vis-a-vis boot order, etc.  and yes, F12 is the correct key to enter.  F2 also offers help at bootup, don’t at the moment remember which details are which, but will review.  Have to be away from the computer for 2-3 hours but will post details then.  Thank you!

Reply | Quote

On a Dell:
F1 = Help
F2 = BOIS/Setup
F8 = Safe Mode, Last known good, etc
F12 = boot order

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Have to be away from the computer for 2-3 hours but will post details then.

I will be gone for a couple hours this morning myself.

I’ll post as soon as I’m back.

@ PKCano

Thanks for the info.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Current status- Vista and Windows 7 hard disks still installed.  PC boots to W7 as expected.  Shutdown occasionally normal, other times slow to very slow to manual shutdown needed via power button.  Hangs up at “shutting down” and cites Task Host Manager.

Normal bootup screen

F12 Boot Order

From F12 <enter setup>

Boot Device Configuration

SATA 3200… is Windows 7, SATA 6400… is Vista, shown as highlighted.  Tried changing the highlight to W7, either way, W7 is the default as shown in first photo.  Unknown if my selecting W7 “sticks” since I didn’t know if too many bootup-shutdown cycles would be harmful- so I didn’t reboot to check.

1 user thanked author for this post.

Just Lurking

Reply | Quote

@ Slowpoke47

So, my BIOS has two boot priority sections.

1. The first section is for the harddrives (HDDs) only. I have 3 HDDs and one Flash Drive hooked up. These four devices are listed here and I can make them be in any order for 1st, 2nd, 3rd, and 4th.

2. The second section is for selecting 3 types of devices for booting, and which will be 1st, and then 2nd, and finally 3rd

So, I have the HDD that has my boot loader (allows me to select which OS I want to boot), set as the first HDD to boot from, and I have that HDD’s partition set as *Active* which is what the System is looking for in order to read the boot loader information. If those two things happen together (first HDD the the BIOS looks at, and set *Active*), the boot process proceeds, and the BIOS does not look at the next HDD in line for boot information (which it may have–but it would only be acted upon if I changed the HDD boot order so the now second HDD is changed to being 1st, or if the now 1st HDD did not have boot information and/or the first HDD was not set as *Active*–then the BIOS would move onto the 2nd HDD to see it is set *Active* and has boot information).

And, in the second section, I have my Optical Drive set as the first device to look for boot information, and then the second boot device is the HDD (and again, which HDD was previously set in the First Section).

So, that set up will look for a bootable optical disc to boot from 1st. If there is no disc, or there is a disc that is not bootable media, then the BIOS moves on and looks for a bootable HDD next.

If there is a bootable disc in the optical drive, then one of two things might happen:

1. Some bootable optical discs will trigger a message saying something to the effect, “Hit any Key if you want to boot from the optical drive.” If you do not hit a Key, then after a brief timeout, the BIOS will move onto the next boot device, usually the HDD. (I guess this behavior is in case you forgot to remove a bootable disc from the optical drive that you used on the last boot, and you don’t want to restart the system, so you can just wait for the timeout to be over and the system will boot from the HDD (and you can remove the bootable optical disc and put it away after the system has booted).

2. Or, many bootable optical discs will simply go ahead and boot immediately. If you did not really want to boot from the optical disc, you first have to close down whatever it is that the optical disc booted, remove the disc, and re-boot the system to get it to bypass the optical drive and move onto the HDD.

Alternatively, rather than using the BIOS boot priority to control what device to boot from, you can hit the F12 key right after you hear the initial bootup beep, you will get the Boot Menu, and you can manually select what device you want the system to attempt to boot from.

So, how is your boot priority set up–what’s first, second, third ….

Reply | Quote

@ Slowpoke47

Great screenshots, a picture is worth 10,000 words!

From your 4th screenshot, *Boot Device Configuration*, select the second item down from the top, *Hard Disk Boot Priority*, press *Enter*. Take a photo of that screen and post it.

Other comments in a moment.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

SATA 3200… is Windows 7, SATA 6400… is Vista, shown as highlighted. Tried changing the highlight to W7, either way, W7 is the default as shown in first photo. Unknown if my selecting W7 “sticks” since I didn’t know if too many bootup-shutdown cycles would be harmful- so I didn’t reboot to check.

Yes, the SATA 6400 is at the top and highlighted in your 2nd photo, *Please Select Boot Device*–that is not an actual *Boot Order*, just a list of boot device options that are listed–I don’t know how the order shown is created. What’s highlighted in that 2nd photo is unrelated to the *Windows Boot Manager*, the 1st photo.

No, it won’t *stick*. Bringing up the *Please Select Boot Device* boot menu just gives you a one time option to choose a boot device. Next time you bring it up, it will look exactly the same as it does now in that photo, unless possibly if you make system changes–then new information may show up–for instance if you take out your Vista HDD, and put the new HDD in that has the Linux Mint installed on it.

I don’t think you have to worry too much about bootup–shut down cycles. But, you can just use *Restart*, and that will not cause a *shut down* cycle.

Hmmm, I’ve not asked before, but just out of curiosity for now, does a *Restart* cause the same delay that the *Shut Down* command does?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

Hmmm, I’ve not asked before, but just out of curiosity for now, does a *Restart* cause the same delay that the *Shut Down* command does?

Didn’t this  time, but sometimes, yes.

The photo you requested.  (Whew) many steps from there to here!

1 user thanked author for this post.

Cybertooth

Reply | Quote

Looks like it’s a BIOS-based system, not UEFI.  I wasn’t sure from the start, so I gave both sets of directions, but that’s not UEFI there.  Too many chefs spoil the broth for sure, so all I will offer is that the thing about the Macrium Reflect USB still stands, and so does the thing about entering ‘sudo update-grub’ once you get the bootloader written.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

Ascaris wrote:

Looks like it’s a BIOS-based system, not UEFI.

Yes, thought I had mentioned that some time back.

Thanks for posting.  I’m well our of my comfort zone here and appreciate the help.

Reply | Quote

Just reviewing Ascaris’ post   https://www.askwoody.com/forums/topic/pc-will-not-shut-down/#post-337646 way back near the beginning of this thread, and joep517 https://www.askwoody.com/forums/topic/pc-will-not-shut-down/#post-337611 before that.  In both cases, the same question- if by either the EasyBCD or Macrium I attempt to rebuild the boot function, and since it was originally co-opted by Vista- with Vista still in the case, won’t that happen again?  Remember, I can’t boot 7 without Vista connected.

Reply | Quote

But you CAN boot the rescue media without Vista connected.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

and since it was originally co-opted by Vista- with Vista still in the case, won’t that happen again? Remember, I can’t boot 7 without Vista connected.

So, just for the record–if you remove the Win7 HDD (or disconnect the communication port wire, or unplug the power cord), you should still be able to boot the Vista OS!

Vista actually did not *co-opt* the Win7 bootloader–it was Win7 that co-opted the Vista partition with the Vista bootloader to place its (Win7’s) boot files on that Vista partition!

We have left out the whole discussion as to how Win7 was added to this system so it was able to create a Microsoft boot loader in the first place. That usually happens when one is running the *installation* media to create the partition(s) and place the OS files onto a HDD. Something happened that we don’t really know about–but let’s leave sleeping dogs lie–at least for now.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

NightOwl’s got you covered.  He’s suggesting everything I would have, so I’d say you’re in good hands!

As he said, it was Windows 7 that co-opted the pre-existing Vista bootloader (and only the bootloader), not the other way round.  The USB rescue drive has its own bootloader, so you can select it as the boot device from the boot options menu regardless of what other drives are installed on the system.

If you were to disconnect the Win 7 drive but leave the Vista one installed, it should still give you the boot menu asking which version of Windows you want, but the 7 option will give an error if you try it, since 7 isn’t there to be loaded.  There’s not really anything to be learned by trying that, as NightOwl has already said, since we already know what the story is.  There’s a Windows bootloader on the Vista drive that can load Vista from that same drive or 7 from the 7 drive.  If you want to take the Vista drive out, there’s no longer a Windows bootloader on the PC, so you’re going to need another Windows bootloader, and that’s what the EasyBCD or Macrium Reflect disc/USB drives will do for you.

Dell XPS 13/9310, i5-1135G7/16GB, KDE Neon
XPG Xenia 15, i7-9750H/16GB & GTX1660ti, KDE Neon
Acer Swift Go 14, i5-1335U/16GB, KDE Neon

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Okay, we are about ready to proceed to testing booting to Recovery Media.

But, before that, I would like to recommend a slight bit of *house keeping*.

I would like you to consider naming, or if already named, re-naming your various partitions so they have *descriptive* names that are *memorable*. So for instance, here’s a screen shoot you posted previously in this thread:

https://www.askwoody.com/wp-content/uploads/2019/03/Start-Computer-screenshot-3-8-19.jpg

If you bring that listing back up in Win7, you should be able to *right-click* with the mouse, and select at the bottom of the option menu that pops up *Properties*. You then should get a window that looks mostly like this:

The top box with the arrow pointing at it can be used to name your partition with whatever you wish. I named mine as *C-Win7_SSD*–that’s my Win7 partition that’s on my SSD HDD and has the drive letter C assigned to it.

So, the partition that’s identified as *Local Disk (C:)* on your screenshot is actually un-named–*Local Disk* is just a generic place holder name. But, I’m pretty sure that’s your Win7 partition that has the operating system files in it. Feel free to correct me if I’m wrong. But, in that screenshot, from your *Computer* (aka *My Computer* and *This Computer*–depending on the OS and the desktop theme that is being used) is lumping all the partitions together that are being *seen*, and not keeping things separated and lumped together by which harddrive (HDD) those partitions are on. A confusion factor! When doing imaging creation and restores, it’s important to keep track of which HDD is which and where the various partitions came from and are located.

This screenshot from your Macrium Image Formation screen keeps things a little bit better organized so you can tell where everything is and is coming from:

https://www.askwoody.com/wp-content/uploads/2019/03/Macrium-screenshot.jpg

A better way to name partitions is to list the nominal drive letter that is seen when booted to that particular OS–so in this case *C*, and to identify what the partition is for or related to–again in this case *Win7*. So, *C-Win7*. If you were administering multiple computers on a network, then also including a computer identifier would be good as well, but you are not doing things quite that fancy–at least not yet 😉 !

The *OS (D:)* looks like it’s probably the Vista partition that holds the OS system files on it. So, I would name it, instead of simply *OS*, so now *D-Vista*.

And the *Recovery (E:)*–I would use *E-Recovery*. Now, when you use the *Computer* to view your HDDs, you will still get the drive letter in the parentheses after the partition name you have given it–but the name just emphases that for you.

Some partitions do not have a drive letter assigned–for instance your *DellUtility*. You can just leave that as is.

I think there might be at least one *hidden* partition. But, we’ll try to identify that possibility next.

Questions?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

On this s/shot you mention, https://www.askwoody.com/wp-content/uploads/2019/03/Start-Computer-screenshot-3-8-19.jpg everything you see there is W7.  The letter names are for some reason, not conventional, e. g. calling the OS by “D.”   This came up earlier, and I looked at the analogous screen in Vista and the GB figures were all different, not reversed as you might expect if C and D were the two OS’s.

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

everything you see there is W7.

Okay, I think we have just *stumbled over* the confusion factor that I was talking about here:

Just Lurking wrote:

But, in that screenshot, from your *Computer* (aka *My Computer* and *This Computer*–depending on the OS and the desktop theme that is being used) is lumping all the partitions together that are being *seen*, and not keeping things separated and lumped together by which harddrive (HDD) those partitions are on. A confusion factor!

Screenshot of Win7 HDD?

You will have to help me out here: I’m going to add up those partition sizes in that screenshot that you say is the Win7 harddrive–289 + 581 + 14.6 = 893.6 GB. Do you agree with the GB numbers from that screen shot? Is that the size of your Win7 HDD?

The Macrium screenshot indicates that your Vista HDD (WD6400) is 596.17 GB, and your Win7 HDD (WD3200) is 298.09 GB.

A Google search says the WD6400 is a 640 GB HDD. (FYI–Windows uses a different way to calculate data sizes for HDDs–it is always less than what the manufacturers list. These numbers appear to be accurate.)

Google search for WD3200 says it’s a 320 GB HDD.

I’ll post another trouble shooting effort to clarify this matter in a moment.

See here:

Just Lurking wrote:

If I ask you to load, or run *Disk Management*, do you know what I mean?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@nightowl, in the screenshot, that “Local Disk C:” must be the Vista HDD, and “OS D:” must the Windows 7 HDD. Gotta be.

It’d be interesting to know how @slowpoke47 obtained that screenshot, i.e. what OS he had booted into when he captured the image.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

PKCano wrote:

But you CAN boot the rescue media without Vista connected.

And that would be the rescue media I just made?

Reply | Quote

Yes, that’s right.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

So, just for the record–if you remove the Win7 HDD (or disconnect the communication port wire, or unplug the power cord), you should still be able to boot the Vista OS!

Would this be worth trying, for informational purposes?  If Vista won’t boot without 7, would that tell us anything useful?

Reply | Quote

Given that the boot record is on the Vista HDD, it would be highly surprising if Vista didn’t boot without the Win7 HDD connected. Give it a try and report on what happens.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

You will have to help me out here: I’m going to add up those partition sizes in that screenshot that you say is the Win7 harddrive–289 + 581 + 14.6 = 893.6 GB. Do you agree with the GB numbers from that screen shot? Is that the size of your Win7 HDD?

Yes, just looked again (“289″= typo, actually 298, but total correct).

Reply | Quote

Have to set this effort aside for today.  NightOwl- are you thinking that the two OS’s are in some way “merged”?

I will try booting up Vista without W7 connected tomorrow and post back.

Reply | Quote

@ Slowpoke47

If I ask you to load, or run *Disk Management*, do you know what I mean?

Disk Management is a Windows program that will show the HDDs connected to your computer. It will list each HDD separately (Disk 0, Disk 1, Disk 2, etc), and show all the partitions that are on a particular HDD. It will also show any USB connected Card Reader(s) for memory cards, any connected Flash/thumb drive(s), and the Optical drive(s) connected and available.

You might be able to go to your Start menu, and in the Search Box, type Disk Management, and it will probably bring up that program. Expand the size so you can clearly see the different drives and the partitions on those drives. Post a screenshot.

Alternatively, if you right mouse button click on *Computer*, or *My Computer*, or *This Computer*–the popup menu should have an entry that says *Manage*–click that and you should get another menu window. Find and click on *Disk Management*. Shortly you should have that program. Do as mentioned above and post a screenshot.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Control Panel>Administrative Tools>Computer Management>Disk Management run on each OS will give a clear picture of the partitions and and their functions.

2 users thanked author for this post.

Slowpoke47, Just Lurking

Reply | Quote

@ PKCano

And a third possible way to reach *Disk Management*–thank you!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@Slowpoke47

Slowpoke47 wrote:

and since it was originally co-opted by Vista- with Vista still in the case, won’t that happen again?

Sorry, forgot to answer that question–No, neither Win Vista, nor Win7 will do anything to the boot loader on their own at this point. You would have to manually make any changes at this time. The possible *automated* creation of the boot loader and placement of the boot files on the Vista HDD occurred at some point when you first installed and started using the Win7 HDD. That window (pun intended) of opportunity has come and gone!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Would this be worth trying, for informational purposes? If Vista won’t boot without 7, would that tell us anything useful?

I’m 99.99% sure Vista will boot without the Win7 HDD connected–so the answer is *Nope–it’s not worth trying.*

Slowpoke47 wrote:

NightOwl- are you thinking that the two OS’s are in some way “merged”?

Nope. I do not think that the two OSs are merged. Their shared bootloader is *merged*, and we know for sure that the Win7 OS HDD is dependent on having the Vista HDD installed if you want to boot to Win7–which must mean that the bootloader is on the Vista HDD, and not the Win7 HDD.

Slowpoke47 wrote:

I will try booting up Vista without W7 connected tomorrow and post back.

As stated above, probably not necessary. You could if you wanted to confirm beyond a 0.01% chance that I’m wrong in my estimation of the possibility. I always use the dislaimer that one should *never say never*–because there’s *always* a chance!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Cybertooth

Cybertooth wrote:

@nightowl, in the screenshot, that “Local Disk C:” must be the Vista HDD, and “OS D:” must the Windows 7 HDD. Gotta be.

Why? What’s your reasoning? What evidence are you using to draw that conclusion? *I’ll show you mine, if you show me yours!*

Did you read my post just above yours that I just quoted? I’m guessing you may have, but did not read it carefully, or did not understand the content.

I was going to go over the information again, because I’m not sure @ Slowpoke47 saw the post–so let me see if I can reply in a manner that’s easier to follow:

We know there are two HDDs on @ Slowpoke47’s system–he has already posted screenshots of that information that clearly show the model #’s of those two HDDs:

Two WD HDDs and their Model Numbers

If you search Google for the WD6400 HDD, you get this:

Look at several entries–all say it’s a 640 GB HDD

Search Google for the WD3200 HDD, and you get:

Again, look at several entries–all say it’s a 320 GB HDD

And, @ Slowpoke47 made the following statement:

Slowpoke47 wrote:

SATA 3200… is Windows 7, SATA 6400… is Vista,

So, the WD3200 is your Win7 HDD, and it is a 320 GB HDD. And, the WD6400 is your Vista HDD, and it is a 640 GB HDD.

I asked these two questions below based on the screen shot here which you stated:

Slowpoke47 wrote:

everything you see there is W7

Just Lurking wrote:

I’m going to add up those partition sizes in that screenshot that you say is the Win7 harddrive–289 + 581 + 14.6 = 893.6 GB. Do you agree with the GB numbers from that screen shot? Is that the size of your Win7 HDD?

You corrected me on a typo for the *289* listing, saying it was supposed to be *298* (which I acknowledge–I typed the wrong number), but the total number of GB was correct at 893.6 GB.

Neither of your HDDs is that large–they are 640 and 320–not 893.6. So, that total number of GB can not be all *W7*.

The number of GB reported by Windows is not the same as reported by HDD manufacturers. Here is a link to a webpage that discusses that info: Why Do Hard Drives Show the Wrong Capacity in Windows?

The formula to calculate the number of GB to expect in Windows is as follows:

# of GB stated by HDD manufacturer * (1000 * 1000 * 1000) / (1024 * 1024 * 1024) = approx GB in Windows

So, for the Vista HDD which is 640 GB:

640 * (1000 * 1000 * 1000) / (1024 * 1024 * 1024) = 596.05 GB

The Win7 HDD which is 320 GB:

320 * (1000 * 1000 * 1000) / (1024 * 1024 * 1024) = 298.02 GB

Look at the Macrium screenshot when creating an image backup of the two HDDs:

Macrium Summary of Image Backup of Vista and Win7 HDDs

The total size for each HDD is a very close match to what’s calculated above.

So, based on the Macrium screenshot–the Vista HDD has 3 partitions (maybe one more hidden–to be determined), and the Win7 has only a single partition.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

The letter names are for some reason, not conventional, e. g. calling the OS by “D.” This came up earlier, and I looked at the analogous screen in Vista and the GB figures were all different, not reversed as you might expect if C and D were the two OS’s.

We need you to boot to Vista. (You could kill two birds with one boot if you wanted to disconnect your Win7 HDD to see if the Vista OS will boot without the Win7 HDD attached.)

Use the same technique you used to create the screenshot that you stated was “everything you see there is W7.” I’m pretty sure you used the click of *My Computer* to get that listing. Post the screen shot here once you have it.

Need to see how Vista’s drive letters, and partition sizes vary compared to that Win7 screenshot.

Windows is notorious for not having consistent drive letter layouts. That’s why I was suggesting that you name your partitions with *memorable* and *descriptive* names so you can not confuse them when you perform image creations and restorations.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

Cybertooth wrote:

@nightowl, in the screenshot, that “Local Disk C:” must be the Vista HDD, and “OS D:” must the Windows 7 HDD. Gotta be.

Why? What’s your reasoning? What evidence are you using to draw that conclusion?

I transposed the labels when writing my post. Sorry about that.

What I was really focused on when preparing that post was the screenshot that @slowpoke47 offered, which could be interpreted as indicating that his drives C, D, and E were partitions from a single larger disk, as you inquired of him:

You will have to help me out here: I’m going to add up those partition sizes in that screenshot that you say is the Win7 harddrive–289 + 581 + 14.6 = 893.6 GB. Do you agree with the GB numbers from that screen shot? Is that the size of your Win7 HDD?

The point was that it was already known they were separate HDDs. Hence the “gotta be”: despite Slowpoke47’s possible impression that Vista and 7 were somehow “merged,” as you put it, based on everything else we’ve seen they had to be different physical disks. And the purpose of writing the post was to reinforce this idea and help to dispel that misimpression.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

2 users thanked author for this post.

Slowpoke47, Just Lurking

Reply | Quote

@ Cybertooth

Cybertooth wrote:

I transposed the labels when writing my post.

Okay, that makes sense! When I first read your response, I thought you were saying it the other way around (see–it was easy for me to transpose the two labels as well). Then I re-read it and said to myself–that doesn’t sound right. But, it was what it was, and I had to ask ….

1 user thanked author for this post.

Cybertooth

Reply | Quote

Again, to all, thank you for your efforts on my behalf.  I will not have time this morning to read the posts since last night when I had to exit, but I did have a few minutes to prepare  just this one post before heading out the door, may be helpful.

This is Vista with the W7 drive connected.

With the data plug of W7 disconnected, as you can see, all is the same.  The smaller plug (power?) was still connected in this s/shot.   Could be I should have done that.  If my understanding is correct, the W7 disk would still have been spinning, but there would be no data available from 7.  I did not shut down when I unplugged the data cable, if that makes any difference.

The three bar graphs are identical to those currently showing in W7.

An interesting point is that the Vista and 7 graphs have not always matched, as they do now.  Before I began playing musical chairs with the hard disks, the numbers differed between the two systems.  Could these two OS’s have “merged”?

In the process of “moving out” of Vista, I transferred the few remaining Vista data files to 7.  I believe that those blue bar graphs did not match across the OS’s before that, but not sure, as I had no reason to check.  Unknown if this was a factor.

And today, for the first time, Vista had the shutdown hangup, had to use the power button.

I expect to be back in about 3-4 hours, will check in then.

 

1 user thanked author for this post.

Cybertooth

Reply | Quote

@slowpoke47, thanks for the two new shots.

If the larger of the two connectors going from the PC into the Windows 7 HDD (a SATA disk, right?) was unplugged, then it was the power cable. That’s interesting, Windows Explorer was still listing the Windows 7 HDD even though it wasn’t powered?

I’m not sure what you meant when you wrote that

The three bar graphs are identical to those currently showing in W7.

Do you mean that Windows Explorer gives you an identical list of drives (each with the same drive letters, sizes, and usage) when you boot into Windows 7 as when you boot into Vista?

Regarding the hangup when shutting down from Vista, my inclination would be to ignore it unless it keeps happening as with your Windows 7. Were you shutting down after having disconnected the Windows 7 HDD? If so, then maybe for some reason the OS was expecting to see that now-nonexistent drive during the shutdown process.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

I did not shut down when I unplugged the data cable, if that makes any difference.

I would have to say not shutting down before unplugging a HDD is a very bad idea and choice! You have no idea what the state of the HDD is in as far as the Windows OS accessing data and writing data to a HDD. You can see the HDD activity light flashing constantly when the OS is up and running–but you don’t know which of any attached HDDs is being access at any given time.

Very risky! Consequences are Unknown!

You have expressed concern about using the Power Button to shut down a frozen Windows shut down process. I think disconnecting a HDD while the system is actively running is a fair riskier event, unless you have *Hot Swapping* enable, and you follow certain procedures–similar to using USB devices such as Flash/Thumb drives! There is a proper way to disconnect a Flash/Thumb drive to make sure Windows has finished writing anything to that device.

Disconnecting a SATA HDD while a system is running is called *Hot Swapping*. It’s a feature that has been available for awhile on modern systems. But the system has to be set up appropriately, and certain settings are necessary, and certain procedures need to be followed.

I have no idea if you are properly set up for *Hot Swapping*. And, I don’t know if you have followed the *proper procedures*. Here’s a list of links where *Hot Swapping* is discussed. You can decide if you want to pursue the information. It is *off topic* to this thread, and you should start a new thread in an appropriate forum if you want to pursue it further:

https://jonhoo.wordpress.com/2009/11/09/hot-swapping-drives-in-windows-7/

https://www.sevenforums.com/hardware-devices/163264-sata-hotswapping.html

http://www.techerator.com/2010/10/easily-hot-swap-sata-hard-drives-with-hotswap/

https://arstechnica.com/civis/viewtopic.php?t=1142171

https://www.howtogeek.com/forum/topic/hot-swapping-sata-hdds

/showthread//121561-Is-SATA-hard-drive-hot-swappable

https://answers.microsoft.com/en-us/windows/forum/all/how-to-set-up-hot-swap-in-windows-7/93f9a70f-5a5e-434d-955f-40532bc1463d

Google Searching will bring up many other results.

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

Just Lurking wrote:

Do as mentioned above and post a screenshot.

Currently reviewing the posts made after I signed out yesterday.

Will continue down the thread to get myself up to date.

Reply | Quote

Cybertooth wrote:

Do you mean that Windows Explorer gives you an identical list of drives (each with the same drive letters, sizes, and usage) when you boot into Windows 7 as when you boot into Vista?

The letters identifying the drives are different, but the figures- GB used, total GB- match between the two HD’s.

Reply | Quote

Ah, OK thanks.

Now the answer to your earlier question:

An interesting point is that the Vista and 7 graphs have not always matched, as they do now.  Before I began playing musical chairs with the hard disks, the numbers differed between the two systems.  Could these two OS’s have “merged”?

…is that they have not merged. The reason you get the same drive listings but with different drive letters is that whichever Windows you’ve booted into, generally likes to consider the drive that it resides on as the C: drive. (This isn’t always the case.)

I have another request for you. That Disk Management screenshot, did you take it after booting into Windows 7 or into Vista? Now please boot into the other OS, go into Disk Management, capture a screenshot of the disks, and post it here for comparison to your first screenshot.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Just Lurking wrote:

I would have to say not shutting down before unplugging a HDD is a very bad idea

There’s another lesson I’m learning by doing it wrong.  Won’t make that mistake again!  Hope there are no consequences.

 

Reply | Quote

Cybertooth wrote:

@slowpoke47, thanks for the two new shots. If the larger of the two connectors going from the PC into the Windows 7 HDD (a SATA disk, right?) was unplugged, then it was the power cable. That’s interesting, Windows Explorer was still listing the Windows 7 HDD even though it wasn’t powered? I’m not sure what you meant when you wrote that

The three bar graphs are identical to those currently showing in W7.

Do you mean that Windows Explorer gives you an identical list of drives (each with the same drive letters, sizes, and usage) when you boot into Windows 7 as when you boot into Vista? Regarding the hangup when shutting down from Vista, my inclination would be to ignore it unless it keeps happening as with your Windows 7. Were you shutting down after having disconnected the Windows 7 HDD? If so, then maybe for some reason the OS was expecting to see that now-nonexistent drive during the shutdown process.

Again, perhaps my ignorance shows.  The wider, flat plug was removed.  The “squarish” one remained connected.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Here is the s/shot of Disk Management in Vista:

Couple of comments- in switching between the two OS’s, I’m seeing Vista boot to the desktop and then to Firefox almost “instantly” while W7 takes maybe ½ minute (not timed) to show the desktop and maybe ¾- 1 full minute to open FF.  Is this of interest?

Also- is there undue exposure when going online in Vista as an obsolete, un-updated OS with no antimalware in effect?

1 user thanked author for this post.

Cybertooth

Reply | Quote

Fantastic, you posted the screenshot I wanted even before I posted my request!  🙂

This confirms that the two OSes have not “merged” or commingled in any way.  I was concerned that maybe the page file and crash dump for one OS had appeared in the other OS’s drive, but thanks to your newest shot I see that each one has its own page file and crash dump. So we’re good there.

To address your most recent question–I would advise strongly against going online with Vista if the OS is not updated, the browser (Firefox) is not updated, and there is no active antivirus software on it. Basically, the gates to the city are open and there are no guards at the entrance or even looking down from the watchtower.

Looks like your OSes are configured to open Firefox automatically when you boot into them. For Vista, please open your Start menu, type “msconfig” in the search bar, and then click on the result “msconfig.exe”. Select the “Startup” tab and find the Firefox item on the list, then uncheck it and click on the “Apply” button.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

With the data plug of W7 disconnected, as you can see, all is the same.

Most likely, if you pulled the communication cable from the Win7 HDD while Vista was up and running, based on the fact that the response to re-clicking on the *My Computer* and getting the same response suggests that the system did not automatically scan and detect that change. Probably needed to re-boot for the Vista system to *see* that change. (Or some other manual procedure to tell the Vista system to re-scan for any changes made.)

But, that result is not very important.

Slowpoke47 wrote:

The three bar graphs are identical to those currently showing in W7.

What is important, is that all the drive letter assignments are different! Did you note that?

In Win7, Local Disk (C:) in Vista is Local Disk (F:)
In Win7, OS (D:) in Vista is OS (C:)
In Win7, Recovery (E:) in Vista is Recovery (D:)

Vista Drive Letter Assignments

So, in Vista you have the following lineup–the C:, the D:, the E:, and the F: drive letter assignments:

OS (C:) your OS Partition for Vista on the Vista HDD
Recovery (D:) your Vista Recovery Partition on your Vista HDD
DVD RW (E:) your optical drive
Local Drive (F:) your OS Partition for Win7 on your Win7 HDD

Win7 Drive Letter Assignments

And, in the previous Win7 screenshot, you have the following lineup–the C:, the D:, the E:, and the F: drive letter assignments:

Local Drive (C:) your OS Partition for Win7 on your Win7 HDD
OS (D:) your OS Partition for Vista on the Vista HDD
Recovery (E:) your Vista Recovery Partition on your Vista HDD
DVD RW (F:) your optical drive

So, first off, this is what Microsoft does when it creates a multiboot setup–it shows the *Old OS Partition* in your *My Computer* when booted to the *New OS* (Win7), and does the same for the *Old OS* showing the *New OS Partition* in the *My Computer* when booted to the *Old OS* (i.e. Vista), in both OSs the current booted OS assigns the non-booted OS Partition a Drive letter, and allows you to access that partition, change data, move files from one OS partition to another–potentially risky if you change critical system files on the non-booted OS. Other third party multiboot setups often *hide* the *Old OS Partition* so you can not have easy direct access–the *Old OS Partition* is protected, and when booted to the *Old OS*, the *New OS Partition* is hidden from the *Old OS*. There are ways to access it, but you have to be a geek and sort of know what your are doing!

Slowpoke47 wrote:

Could these two OS’s have “merged”?

Same answer as before–Nope! The two OSs have NOT MERGED. It’s just that the *My Computer* shows the OS Partition of the Non-Booted OS in its list of Partitions.

Once more, I would recommend you do this in order to keep better track of what’s going on:

Just Lurking wrote:

I would like you to consider naming, or if already named, re-naming your various partitions so they have *descriptive* names that are *memorable*. So for instance, here’s a screen shoot you posted previously in this thread:

https://www.askwoody.com/wp-content/uploads/2019/03/Start-Computer-screenshot-3-8-19.jpg

If you bring that listing back up in Win7, you should be able to *right-click* with the mouse, and select at the bottom of the option menu that pops up *Properties*. You then should get a window that looks mostly like this: …

1 user thanked author for this post.

Cybertooth

Reply | Quote

I second the suggestion by @nightowl to give new names to the OS drives, reflecting the OS (Vista or 7) that’s on each. Perhaps even the “Recovery” drive could get “Vista” tacked onto its label, for example “Vista Recovery” or “Recovery Vista”.

This would greatly simplify the troubleshooting process.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

in switching between the two OS’s, I’m seeing Vista boot to the desktop and then to Firefox almost “instantly” while W7 takes maybe ½ minute (not timed) to show the desktop and maybe ¾- 1 full minute to open FF. Is this of interest?

Not in this thread. Start a new topic in the appropriate forum.

Probably the two system are doing different startup procedures that effect how long things take.

Looks like you have set things up to start FireFox automatically on startup–hope you did that on purpose.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Maybe unrelated but could you check if the power and reset button cables are undamaged and attached correctly to the motherboard and the case buttons. Take special note at the motherboard end that the cables are on the correct + and ground pins. The cables could have been damaged or detached from the motherboard when installing the HDD.

W10&11 x64 Pro&Home

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Also- is there undue exposure when going online in Vista as an obsolete, un-updated OS with no antimalware in effect?

Of course there is!

There are probably a couple anti-malware options still available for Vista. Do some searching. Maybe Malwarebytes, or Webroot are options?

Firefox is probably no longer updating for Vista. Possibly Opera is still being updated for Vista.

I guess Vista OS is not being updated by Microsoft any longer?

Guess what?! One of the best protections against getting hit by malware is regular image backups–so you can simply restore a prior backup before any malware hit your system!

But, you plan on ditching Vista anyway–so that should not be a worry for much longer–yes?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Here’s some info about this:

Microsoft stopped providing monthly patches for Vista in 2017.

Firefox support for Vista ended last year.

There’s still security software working on Vista. For example, I’m using Norton 360 and HitmanPro.Alert on my Vista system. I suspect that Slowpoke47 deactivated his AV because the plan was to transition to Linux, so there was little point in renewing the subscription, but of course the transition has yet to conclude.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

To address your most recent question–I would advise strongly against going online with Vista if the OS is not updated, the browser (Firefox) is not updated, and there is no active antivirus software on it. Basically, the gates to the city are open and there are no guards at the entrance or even looking down from the watchtower. Looks like your OSes are configured to open Firefox automatically when you boot into them. For Vista, please open your Start menu, type “msconfig” in the search bar, and then click on the result “msconfig.exe”. Select the “Startup” tab and find the Firefox item on the list, then uncheck it and click on the “Apply”

I did that, with apprehension, because the only way I knew to get the Vista s/shot into W7 for posting here, etc. was to attach it to a gmail draft in Vista and open it in 7.

Neither OS is set to open FF automatically, they each have a FF icon in the tray.

 

 

Reply | Quote

@slowpoke47, for future reference, here’s one method for posting screenshots at Woody’s here without exposing your Vista system to online threats.:

Take your screenshot normally in Vista. Then, open your Paint application and paste the screenshot onto it. Give it the file name you choose, and then when you go to save it, navigate over to your Windows 7 HDD and save it somewhere on that drive (make sure to remember where you put it).

Now you can shut down Vista, boot into 7, come to Woody’s, and post the screenshot from where you saved it in the Win7 drive.

The procedure is a little roundabout, but preferable to exposing your undefended Vista system to online threats. Hopefully you won’t be needing to do it much more.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

” Take your screenshot normally in Vista. Then, open your Paint application and paste the screenshot onto it. Give it the file name you choose, and then when you go to save it, navigate over to your Windows 7 HDD and save it somewhere on that drive (make sure to remember where you put it). ”

My two-cents contribution to this long-running saga:

I always put the screenshots and other documents I need to append to emails or, in this case, a posting at Woody’s, by saving them to my PCs (or Mac) Desktop. No way I’ll ever forget about where I put them, as I can see them every time I look at the screen, when no other windows are open, especially with none in “full screen” mode.

Once I am done with them, I usually trash them.

Ex-Windows user (Win. 98, XP, 7); since mid-2017 using also macOS. Presently on Monterey 12.15 & sometimes running also Linux (Mint).

MacBook Pro circa mid-2015, 15" display, with 16GB 1600 GHz DDR3 RAM, 1 TB SSD, a Haswell architecture Intel CPU with 4 Cores and 8 Threads model i7-4870HQ @ 2.50GHz.
Intel Iris Pro GPU with Built-in Bus, VRAM 1.5 GB, Display 2880 x 1800 Retina, 24-Bit color.
macOS Monterey; browsers: Waterfox "Current", Vivaldi and (now and then) Chrome; security apps. Intego AV

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

That works very well.

In this particular case, though. @slowpoke47 wanted to create the screenshot in Vista and then post it here from Windows 7, so he was going online with the vulnerable Vista system to upload the image to Gmail in order then to boot into 7 to prepare his AskWoody post. The method I described was one way to save the screenshot directly on the Windows 7 drive, avoiding going online with Vista.

One way to accomplish this while preserving your method of saving to the desktop, would be to save it to the Windows 7 desktop from his Vista system. (Forgive me if that’s what you had in mind all along.) In Paint, he could navigate over to the Windows 7 drive (whatever letter was assigned to it), then find the Users folder in that drive, expand it, and select his username from the three folders “Default/username/Public” that will be listed. Finally, under “username” he could click on “Desktop”and place the screenshot there.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

Reply | Quote

Cybertooth wrote:

Here’s some info about this: Microsoft stopped providing monthly patches for Vista in 2017. Firefox support for Vista ended last year. There’s still security software working on Vista. For example, I’m using Norton 360 and HitmanPro.Alert on my Vista system. I suspect that Slowpoke47 deactivated his AV because the plan was to transition to Linux, so there was little point in renewing the subscription, but of course the transition has yet to conclude.

This is why I was nervous- Vista in this computer has been abandoned since W7 was installed, not long after that OS came out.  No a/v on it for years.

Reply | Quote

Just Lurking wrote:

But, you plan on ditching Vista anyway–so that should not be a worry for much longer–yes?

This is the key statement.  I just want to get out of Dodge with my hide intact.

Reply | Quote

Sinclair wrote:

Maybe unrelated but could you check if the power and reset button cables are undamaged and attached correctly to the motherboard and the case buttons. Take special note at the motherboard end that the cables are on the correct + and ground pins. The cables could have been damaged or detached from the motherboard when installing the HDD.

Thanks for your post- All of these connections were checked as a matter of habit when I made any changes.

Reply | Quote

Just Lurking wrote:

Looks like you have set things up to start FireFox automatically on startup–hope you did that on purpose.

No- Firefox starts using an icon in the tray.  I have not set up anything to run at startup beyond what’s needed to boot up.

Reply | Quote

I’m a little confused. You reported earlier that

I’m seeing Vista boot to the desktop and then to Firefox almost “instantly” while W7 takes maybe ½ minute (not timed) to show the desktop and maybe ¾- 1 full minute to open FF.

If it’s not Firefox starting up automatically, then are you manually opening Firefox as soon as possible after Vista boots up? If you are not opening Firefox manually, then something is causing it to open without your specific input.

This mini-topic sounds like it could be a distraction from the main discussion in this thread (“off-topic,” as they call it), but I’m wondering if there might be malware on your machine that could also be related to your shutdown problems.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

navigate over to your Windows 7 HDD

I have always used Paint to edit screenshots.  I think it’s an underrated program (but-what do I know?  haha).  The move that stopped me was how to get the file from Vista to 7 since the two doc files are independent (aren’t they?)

Reply | Quote

Yeah, Paint is a neat, and underrated, little program.

When saving an image in Paint, it’s easy to save it to the folder or drive that you want. For example, if you’re in Vista, when you go to save the image, just use the left panel of the Explorer-like window that pops up asking you where to save it. Scroll up and down in that left panel to find the drive and folder where you want to save the image, and select it. The location can be a folder on the Windows 7 drive or it can even be an external disk or flash drive: as long as Explorer can see the folder, you can most likely save to it.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

If it’s not Firefox starting up automatically, then are you manually opening Firefox as soon as possible after Vista boots up?

Yes- I misstated that- should have said that both the desktop and FF were quick to boot- The desktop on startup and FF only on request.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Good, that’s one less “trouble” to “shoot.”  🙂

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Cybertooth wrote:

Yeah, Paint is a neat, and underrated, little program. When saving an image in Paint, it’s easy to save it to the folder or drive that you want. For example, if you’re in Vista, when you go to save the image, just use the left panel of the Explorer-like window that pops up asking you where to save it. Scroll up and down in that left panel to find the drive and folder where you want to save the image, and select it. The location can be a folder on the Windows 7 drive or it can even be an external disk or flash drive: as long as Explorer can see the folder, you can most likely save to it.

This is good to know, never needed this before now.  (And when this problem is cleared up, I hope not to need it again!)  I’m going to keep a note about it, thank you.

Reply | Quote

Cybertooth wrote:

Good, that’s one less “trouble” to “shoot.” 🙂

Great- I’ve long since run out of ammo!

1 user thanked author for this post.

Cybertooth

Reply | Quote

@ Cybertooth

When @ Slowpoke47 boots the Rescue Media for Macrium, what can he expect to see?

Will Macrium load automatically? Or will there be a *Desktop* of sorts with a *Shortcut* Icon for launching Macrium? Or will there be some sort of *Start* button, and have to look for *Programs* and then a *Macrium* entry after pressing the *Start* button?

We need to get ready.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@nightowl, when he boots the PC with the Macrium Reflect rescue media in the optical drive, his PC will either boot to the Macrium disc directly, or give him a choice to “press any key to boot from CD/DVD”.

Once he boots into the Macrium disc whichever way, the Windows PE environment will load and then launch automatically into Reflect, with no further interaction. Once the loading is finished, he will be able to select drives to back up or to restore to, as desired.

One caveat is that any external HDD where he may want to store a new image, or from which he may want to restore an existing image, should be plugged in before booting. If the external HDD gets connected after the rescue media boots, it may not be recognized and he’ll have to start the process again with the external drive plugged in.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

2 users thanked author for this post.

Just Lurking, Slowpoke47

Reply | Quote

Would it be helpful if I redid the Start>Computer s/shot in Vista after shutting down the PC and disconnecting both cables to the W7 disk?

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Would it be helpful if I redid the Start>Computer s/shot in Vista

Nope! I think we are done with that. I’ll post some info about the Disk Management screenshots shortly.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

When @ Slowpoke47 boots the Rescue Media for Macrium, what can he expect to see? Will Macrium load automatically? Or will there be a *Desktop* of sorts with a *Shortcut* Icon for launching Macrium? Or will there be some sort of *Start* button, and have to look for *Programs* and then a *Macrium* entry after pressing the *Start* button?

FWIW, I have an on-again-off-again video project I’ve been tinkering with. It’s still a work in progress so I’m not publicly linking to it yet from the rest of my site, but a little after the 9:00 minute mark it illustrates the Macrium Rescue media booting. Perhaps that’s useful to you.

I also describe the “Fix Windows Boot problems” function at Step 11 in this tutorial.

 

4 users thanked author for this post.

satrow, Cybertooth, Just Lurking, Slowpoke47

Reply | Quote

@ Slowpoke47

So, let’s look at the Disk Management screenshots for a moment:

(Remember, you can click on the screenshots to get a larger image view.)

This is the Vista Disk Management screenshot. The two red arrows show Disk 0, and Disk 1. So, just as an FYI, Microsoft usually (but not always) starts disk numbering at zero (0). When be look at the Macrium Image Backup summary page shortly, you will see that the disk numbering starts at one (1). That can throw some folks off because it’s not the *same*.

Also, when we look at the next screenshot of the Win7 Disk Management, the two disks will be in the reverse order–just represents a different sort order from one OS to another–the Vista OS and the Win7 OSs are separate from one another–not merged. Again, don’t let it throw you off.

The two blue arrows–one pointing to *System* and the other to *Boot*. For unexplained reasons, these two terms mean the opposite of what you would expect–this is just Microsoft *speak* and we all have to deal with it! *System* means that the boot files are located here. On a *typical* Windows installation, usually the *System* label is found on a small partition at the beginning of the HDD–see the small box at the beginning of the Disk 1 that says 39 MB–that’s where I would have expected to see *System*. So, Dell has chosen to use a *non-standard* setup. (By the way, that 39 MB partition is labeled differently in the Macrium Image Formation summary–it’s the *DellUtility* partition there–we will look at that screenshot shortly. And the *Boot* label means that the operating system files are located here–you would think that would be labeled *System* wouldn’t you?

And the green arrows–the only *Active* partition is the Vista *OS (C:)* partition–the Win7 partition *(F:)* does not have the *Active* label. When your system boots, it has to find the *Active* partition in order to boot successfully, because that’s were the boot files are located.

Now, onto the Win7 Disk Management:

So the red arrows show again the two separate HDDs, but now the listing of the partitions have been switched. Again, not a big deal–just a confusion factor.

Blue arrows: the one pointing to the 39 MB partition in Disk 0 is labeled up in the top portion of the Disk Management with the Red Box around it as *OEM* Partition–again, it will be labeled *DellUtility* in the Macrium screenshot.

The blue arrow pointing to *System* in the 3rd partition (the *OS (D:)*–the Vista OS partition) of Disk 0 indicates that the boot files are in that partition. And the blue arrow pointing to *Boot* in Disk 1 shows that the OS files are located there for the Win7 OS.

Green arrows–two of them have the label *Not Active* to emphasize that the Win7 OS located on *C:* is not the active partition. The *Active* partition has to be where the boot files are located–and we have previously determined that they are on the Vista HDD, and now specifically on the OS *System* partition (i.e. the *OS (D:)* partition.

So, onto the Macrium Image Summary page:

So, notice that the top disk is *Disk 1*, and the next one down is *Disk 2*–the numbering is different from Microsoft’s numbering.

The first two red arrows on Disk 1 point to the first partition on the Vista HDD, and point out that the label is now *DellUtility*, and is the 39 MB partition. And the third arrow in Disk 1 points out that the *OS (D:)* partition is the *Active* partition.

The final red arrow on Disk 2 points out that there is no *Active* designation for the Win7 partition (the *(C:)* partition), the only partition on the Win7 HDD.

Questions?

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

I’ve looked at dg1261’s two links, and have somewhat of an inkling what to expect.  But, with my lack of experience and compromised hearing (tinnitus), I don’t think I could perform these operations without further help.  But I’m ready for some non-tech-level guidance, if offered.

Reply | Quote

@ Cybertooth

Cybertooth wrote:

Once the loading is finished, he will be able to select drives to back up or to restore to, as desired.

And, how about exiting and rebooting to Windows … necessary steps and clicks?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Sorry for taking so long, I’m in and out of the office the rest of the day.

If I remember correctly, once Slowpoke47 is finished restoring his selected image to the desired HDD, he can click on the red X on the upper right as if it were a normal Windows window. Then the program will close and either the CD/DVD will slide out on its own, or it will ask to press Enter to log out and then start to reboot. (He may have to open the CD tray manually to make sure it doesn’t boot right back into the Macrium rescue disc.)

My recollection of the process is obviously a bit fuzzy, but I can say for sure that once you’re in the process, the steps to get out of Macrium and reboot are well indicated and hard to misinterpret.

I’ll see if I get a chance to try it out this afternoon with my Macrium disc, and report back if still needed.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

But I’m ready for some non-tech-level guidance, if offered.

Indeed, more to come!

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Slowpoke47

So, let’s get ready to load the Macrium Recovery Media and do a test run of things.

Remember this: You can not screw anything up unless you start hitting options and buttons randomly! Do not put checks in boxes and then hit an *Apply* button. Macrium does have check boxes to select various harddrives (HDDs) and/or individual partitions–those are meaningless unless you again hit a button that says *Restore*, or *Next*, or something of that nature.

And, you can never cause any major problems if you *create* an image. It could be the *wrong* image, but the creation on an image will not cause any harm.

It’s when it’s time to *restore* an image to the HDD that you have to be *spot on* correct! Restoring wipes out everything on the drive and replaces it with whatever is on the image! If you restore the Vista partition to your Win7 partition–you will be a very unhappy computer user!

As Cybertooth mentioned:

1. Hook up your external HDD with your backup Image file(s)

2. Put your Rescue Media CD into your optical drive (if any autorun pop-ups occur, just cancel them out).

3. Because your optical drive is 1st on the Boot Priority list in the BIOS, you should only have to *Restart* your system from Windows. As Cybertooth said, either the disc will automatically load the Macrium software, or you will have a message to *Hit any key to boot from the CD … *

4. Once the Macrium software loads, look around. Select the *Restore* Icon, and it should bring up a dialogue box to select an image file source. You should be able to use a drop down arrow or the box with the … (dots) in it to bring up a selection menu. Look for your external HDD.

5. Once you see the file listed, select it and hit the *Next* button, or maybe it will be the *Open* button. It should load the image file and allow you to look at it. You should see a summary page much like we have been looking at here for the Image Creation Summary–you should see two HDDs listed–your Win7 HDD should show a single partition, and the Vista HDD should have the 3 partitions listed. Stop! You are done here!

6. Hit the *Cancel* button.

7. Remove your Rescue Media CD disc. Then hit the red box with the X in it to close out the Macrium software. (There might be some other exit information seen, or maybe it might say *Reboot*–any of these items should work. Possible Ctrl-Alt-Delete may work as well. If all else has failed, hold down the power button until your system shuts down.)

8. In theory, this should send you to a reboot sequence that takes you back to the Windows OS selection screen, etc. If you had to power down, then hit the power button to start up again.

If you’re unsure of anything–don’t proceed. Ask questions until you’re satisfied that you can proceed comfortably.

Report back here when done! Write down questions you run across as you go and ask them once back here.

2 users thanked author for this post.

Cybertooth, Slowpoke47

Reply | Quote

Just Lurking wrote:

1. Hook up your external HDD with your backup Image file(s)

Just to beat it to death- this would be the system image just made last week?

I’m assuming that, once this is started, I will not have the ability to come back here for help via this PC until finished.  I may be able to set up a laptop nearby and bring up this thread, might be a few minutes at it.

Reply | Quote

OK, I just tried loading and then exiting the Reflect rescue CD from my Windows 7 laptop.

The startup process was as I remembered it: after hitting a key (any key) to boot into the CD, WinPE and then Reflect loaded without requiring any response from me.

Exiting simply required hitting the red X button in the upper right. However, then the booting process started back up, without sliding the CD out or asking me to do anything.

At this point, the laptop booted the same way as the previous time, but this time I didn’t hit any keys, so it passed over the CD and went into Windows normally.

Hope this helps.

 

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

2 users thanked author for this post.

Just Lurking, Slowpoke47

Reply | Quote

@ Slowpoke47

Slowpoke47 wrote:

Just to beat it to death- this would be the system image just made last week?

Yup–your new USB 1TB HDD that you used last week.

Slowpoke47 wrote:

I’m assuming that, once this is started, I will not have the ability to come back here for help via this PC until finished.

Well, you should only be gone for 5-10 minutes at most!

But, correct–until you reboot, you probably will not have access to the internet. I think there are some Recovery Media that offers browsers and internet access, but I’m not sure of this Macrium Rescue Media.

@ Cybertooth–do you know–does the Macrium Rescue media support internet access?

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

1. Hook up your external HDD with your backup Image file(s) 2. Put your Rescue Media CD into your optical drive (if any autorun pop-ups occur, just cancel them out).

IS the PC meant to be on at this point?

Reply | Quote

@Slowpoke47

Slowpoke47 wrote:

IS the PC meant to be on at this point?

Yes.

Reply | Quote

Just Lurking wrote:

@ Cybertooth–do you know–does the Macrium Rescue media support internet access?

Not that I’m aware of. There’s no need for it, really, as all the user is doing is to create or restore disk images.While setting itself up, WinPE does ask if you want to install some drivers, such as for Ethernet, but I haven’t found any way to make use of them in that environment so I just ignore that and click on “Continue.”

As far as I know, the only thing you can do with the Macrium Reflect rescue media is to use the functions offered from within Macrium Reflect. There’s no way to use any other program that’s not linked to it. Maybe one could browse one of the images and find a program to try and click on, but I’d be surprised if it worked. This rescue CD is really a single-purpose disc.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

@ Cybertooth

Cybertooth wrote:

While setting itself up, WinPE does ask if you want to install some drivers, such as for Ethernet, but I haven’t found any way to make use of them in that environment

I’ll bet that is so you can use a network to browse Macruim to a remote computer for a stored image file–or maybe to remotely create and/or restore an image file to that remote computer. Advanced usage!

2 users thanked author for this post.

Slowpoke47, Cybertooth

Reply | Quote

@ Slowpoke47

It’s been about a half hour now. I thought you’d be back sooner than this!

I have to be away from my computer for a couple hours.

I hope I come back to *Success* for your first booting to Rescue Media.

We’ll next create an image file of your Linux Mint HDD, after removing your Win7 HDD for safe keeping.

Outline to come.

1 user thanked author for this post.

Slowpoke47

Reply | Quote

PC back up and running- the Macrium screen was slightly different from what I thought I read in NightOwl’s step-by-step, but close enough that I think I did it right.  There was no “cancel” button anywhere on the screen (step 6) unless you meant the usual red button, top right of screen.  The rescue CD is removed, but the System Image HD is still connected.

Once I removed the rescue disc, the screen went completely black, nothing at all on it.  I waited a little, nothing happened.  Pressed esc and the PC began the normal bootup, usual black screen to start to choose Vista or 7.  The rest of the way was almost normal, then the normal desktop appeared, and I’m back using the same PC to report the result.

Does all this sound right?

Reply | Quote

@slowpoke47, that sounds just about right. It looks like you’re back in business!

The procedure for exiting the Macrium rescue disc is to click on that red X button and then let the PC boot back up, bypassing (ignoring) the option to boot again into the rescue disc. Sounds like you removed the rescue disc before hitting the red X button to exit Macrium?

But no matter, everything should be fine.

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.

Slowpoke47

Reply | Quote

Just Lurking wrote:

It’s been about a half hour now. I thought you’d be back sooner than this!

Sorry- I didn’t feel comfortable with the steps unless I could see them as I went, so I took a few minutes to set up a laptop nearby to be able to refer to your post.

Should I be removing the System Image HD yet? 

Just Lurking wrote:

I hope I come back to *Success* for your first booting to Rescue Media.

See my previous post- do you think I did it right?  There was a slight bit of interpretation and a whole lot of apprehension involved.

Just Lurking wrote:

We’ll next create an image file of your Linux Mint HDD

Bear in mind that this was downloaded using a bootable flash drive, which I’m saving to use, at some point, on the laptop, where it will be a partition.  (Big talk, but hoping for help if needed).  As of yet, I have done nothing with this OS other than to poke around.  If an image is your recommendation, would that be before any added software,etc.?

Cannot thank you enough.  You have saved my bacon!

Reply | Quote

Cybertooth wrote:

But no matter, everything should be fine.

By fine, do you mean the boot function should be restored?

I have to exit for today, will check back in tomorrow morning.  Thank you for your help and patience!

Reply | Quote

You’re very welcome, glad to do what I can to help.

By “fine,” I mean that nothing got messed up when you got that black screen after you were done with the Macrium rescue disc, and we can proceed to the next step. We still need to fix your Windows 7 bootup and shutdown issues, and then ultimately to replace your Vista with Linux while keeping the ability to select which OS to boot into once you have Linux and Win7 inside your PC.

@nightowl has an excellent handle on how to proceed here, so I will avoid stepping on his toes as to what is to be done next.

 

Keep Running Windows 7 Safely for Years to Come  
Make Windows 10 look and work like Windows 7

1 user thanked author for this post.