• The value of a recent drive image

    Home » Forums » The value of a recent drive image

    Author
    Topic
    #491142

    This afternoon I was doing some finagling in my Windows 8 registry, (minor stuff, really, but here there be demons) and managed to make Windows 8 unbootable. It made three valiant tries, then put up the screen telling me to get out my installation media, repair work needed.

    But I didn’t bother with that. I booted into my dual boot Windows 7, opened Image for Windows, and restored my OS image of 9/22/13 from my NAS. The actual image file restore took 6 minutes 51 seconds (I timed it). Going through the menu selecting which and where added maybe a minute to that, and the booting back and forth a couple more minutes.

    After booting back into Windows 8, I had a Windows Defender Update and a Flash Player Update, which are going on in the background as I’m typing this. Bottom line is that from an unbootable Windows 8 I’m right back where I was in under ten minutes. If I weren’t dual booting, I would have booted the Image for Windows USB boot drive and accomplished the same thing in about the same amount of time.

    But what I’m getting at is that regardless of the cause of an unbootable Windows 8 (malware, file corruption, owner misfeasance:o or what-have-you), the cure can be quick and simple. Had it been a failed hard drive (and I’ve had a few) dealing with the hardware issue would have added significantly to the timeframe, but getting Windows up and running would still be quite painless.

    If yours is a standard Windows installation (whether XP, 7, or 8) the image restore would probably take more time, but not nearly as long as doing a reformat/reinstall of Windows and your programs. Everyone has heard the expression, “Pay me now, or pay me later.” “Later” is always more expensive.

    I highly recommend (as do many others here) developing a drive imaging regimen and using it with regularity. It is well worth the effort.

    Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
    We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
    We were all once "Average Users".

    Viewing 19 reply threads
    Author
    Replies
    • #1414277

      Can’t argue with under ten minutes.

      I just did a Refresh which took 45 minutes, plus 40 Windows Updates, plus reinstalling various desktop programs.

      And I wish I’d remembered to use Windows Easy Transfer to save email settings first, as a Refresh seems to lose those.

      Bruce

    • #1414308

      Six minutes is about the best I’ve heard of in terms of a image restore.
      I couldn’t agree more about taking the time to learn how to make and restore your own images.
      Nothing beats a well thought out backup regimen.

    • #1414323

      Ain’t Imaging grand. Many of us say it often (It’s in our signatures). My Images are at most less than a month old. I always create new Images right after patch Tuesday. In this way if a WU screws things up, I restore to last months Image. If I screw things up (just as bbearren did) which seems to happen too often, in less than 10 minutes I am back up and running. I happen to use Acronis from the Boot Disk, but the important point here is that no matter what app you use, it will not work unless you use it!

      Plus another key bbearren mentions is the fact that he restored his “latest” Image. He also creates a new Image regularly. Imagine if your most recent Image is 6 months old, or older. How many changes have happened since that Image was created? Gads, that would be a lot of extra work!

      • #1414968

        I always create new Images right after patch Tuesday.

        That is so wrong :o:
        I always image immediately BEFORE I permit a Patch Tuesday, and especially before emergency patches.

        When I first moved from XP to Win-7 I did not quite master how to put a total stop to updates,
        and unfortunately I spent most of a day creating a new document whilst Microsoft was quietly doing the dirty to me.
        At the end of the day I saved the document and closed down the computer,
        but this was instantly disrupted by a surreptitiously downloaded emergency patch that took control and got installed.

        When I next booted up, my mouse and keyboard stopped working within 1 minute.
        Every time I rebooted I had barely enough time to log in before they stopped working.

        I had to use my Macrium Boot Rescue CD and waste about 6 minutes creating a new full image backup of my destroyed system,
        and then 6 more minutes restoring the previous image backup of my fully functional system.
        After booting up my fully functional system it took less than one minute to mount as drive P: the backup of the destroyed system,
        and then in a few seconds I located the new document that cost me one day, and copied it from P: to C:.
        Then in less than 1 minute the portable freeware BestSync produced a comparison tree that detailed absolutely every file that differed between C: and P:,
        and then I had to spend an hour scrutinising those differences and choosing which were differences that I had created,
        and then a few more minutes synchronising those changes from P: to C:.
        http://www.risefly.com/fsedwld.htm

        I was annoyed with myself that I had failed to fully lock down Microsoft Patches.
        I was infinitely more annoyed with Microsoft when I discovered that their emergency patch was NOT for my protection,
        but to protect their exorbitant revenue stream :o:
        They had discovered that there was some exploit that protected unlicensed Windows from detection and crippling by their original “Windows Genuine Advantage”,
        and had my version been non-genuine they would have allowed me only one hour from power on before an automatic shut-down,
        and would only restore normality when I contacted them for a genuine license.
        Because I had a fully licensed system they did not shut down after one hour,
        instead their patch went wrong and killed my control within one minute of power-up, every time until I restored normality.

        • #1415338

          I always image immediately BEFORE I permit a Patch Tuesday, and especially before emergency patches.

          Agreed! I got in the habit of doing that in back in XP, since Windows Updates (even selectively applied) hosed the system on more than one occasion.

        • #1417984

          “When I first moved from XP to Win-7 I did not quite master how to put a total stop to [Microsoft] updates.”

          being new to rejecting ms automatic updates, I know I would be interested in what you have learned; perhaps others would be also.
          can you point to a procedure posted online, or perhaps share you method?

          thank you

          • #1418184

            ”When I first moved from XP to Win-7 I did not quite master how to put a total stop to [Microsoft] updates.”

            being new to rejecting ms automatic updates, I know I would be interested in what you have learned; perhaps others would be also.
            can you point to a procedure posted online, or perhaps share you method?

            thank you

            Simply open up WU and select “change settings”. From there select “Never check for updates” in the drop-down menu.
            This has worked in all versions of Windows, and I’ve never had to resort to anything more extreme, like disabling a service or something.

            • #1418228

              Wasn’t there a period when Microsoft forced some updates on us even when we turned off Windows Update as per your method? I seem to recall two or three times when i went to Shutdown a message appeared saying Windows is installing a Critical update before shutting down, or words to that effect? Maybe it was before they released Service Pack 1 ?

            • #1418234

              Wasn’t there a period when Microsoft forced some updates on us even when we turned off Windows Update as per your method? I seem to recall two or three times when i went to Shutdown a message appeared saying Windows is installing a Critical update before shutting down, or words to that effect? Maybe it was before they released Service Pack 1 ?

              I’ve never encountered that issue in W7, XP maybe, but not W7.
              The transition from W8 to 8.1 never turned WU back on, of course it flagged it on several occasions via Action center.

    • #1414949

      I have a regular backup regime. I always do a full image of the boot drive every 7 days with differential images every day. This has allowed me considerable flexibility. I have installed new operating systems and then backed off very quickly. I have also recovered from some stupid but apparently unfixable bugs by recovering back until the bug disappears. Essential to this is to get your data off onto another drive so that if you recover back a few days your data losses are minimised.

      • #1416748

        I’ve always told my customers, whether a home PC user, bank or Corp. office, “the thing that controls how often you do a backup, depends on how much data you’re willing to loose when your HD crashes.” Eh?

        If you never do anything on your PC but read email and play solitaire, then a monthly backup would probably be just fine, to save your monthly updates, etc.

        But, if you’re like me, or the bank trust Department, that won’t cut it!!!
        I back up all my data files daily and my entire C drive weekly. (not, weakly) :rolleyes:

        Daily, I use a batch file with XCOPY, to back up any file that’s new or has been changed, since the last backup.
        Those backups go to two external drives….a 32 gig, USB 3.0 Flash Drive and a 1TB, USB 3.0 External Hard drive. So, since these are ‘incremental’ updates, they take only a few seconds. If one of those external drives should fail, I still have the other one. Then I also have my Weekly backup of the entire C drive.

        My favorite thing I tell my customers, is: “The only bad backup, is the one that you decided NOT to make“.

        Good luck, Y’all !
        The Doctor 😎

    • #1414955

      I’m new to drive imaging and cloning. I think I understand the basic difference. I’m getting ready to migrate 12-20 workstations and laptops from XP to Win7pro64 and would like to make disk images before doing the upgrades. It also seems like it would be a good idea to make disk images instead of just backing up our six servers running variations of Winserv 2003 & 2008. It seems like Macrium Reflect Tech lic. standard is the best deal although its an annual subscription. Is there a tech license for Image for Windows? It doesn’t say anything about an annual license fee & I haven’t figured out the Image Deployment purchase option yet. It seems like the Acronis products are a lot more expensive than others… any guidance is welcome. Thanks, Joe

      • #1414972

        I’m new to drive imaging and cloning. I think I understand the basic difference. I’m getting ready to migrate 12-20 workstations and laptops from XP to Win7pro64 and would like to make disk images before doing the upgrades. It also seems like it would be a good idea to make disk images instead of just backing up our six servers running variations of Winserv 2003 & 2008. It seems like Macrium Reflect Tech lic. standard is the best deal although its an annual subscription. Is there a tech license for Image for Windows? It doesn’t say anything about an annual license fee & I haven’t figured out the Image Deployment purchase option yet. It seems like the Acronis products are a lot more expensive than others… any guidance is welcome. Thanks, Joe

        Technician use requires a full use license for each computer. Of course, this allows the continued use of the product by the client. There are reseller options, as well. This article has a little more information.

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
        We were all once "Average Users".

        • This reply was modified 5 years, 9 months ago by bbearren.
        • This reply was modified 5 years, 6 months ago by bbearren.
        • #1415098

          Thanks. I just checked out your site & did a a fast run through your blog. Looks like we’re on the same page except I was in USN 66-70 in DC & the Pacific and in optics. I’ll check out the tech stuff on your site in the late evening sometime.

          I followed your link for the tech lic. & have sent terabyte an email explaining my needs and requesting guidance & a quote. Do you work for them or are just a satisfied user?

          • #1415183

            Thanks. I just checked out your site & did a a fast run through your blog. Looks like we’re on the same page except I was in USN 66-70 in DC & the Pacific and in optics. I’ll check out the tech stuff on your site in the late evening sometime.

            I followed your link for the tech lic. & have sent terabyte an email explaining my needs and requesting guidance & a quote. Do you work for them or are just a satisfied user?

            No, I don’t work for TeraByte, but I’ve been a satisfied user for more than a dozen years.

            Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
            We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
            We were all once "Average Users".

            • This reply was modified 5 years, 9 months ago by bbearren.
            • This reply was modified 5 years, 6 months ago by bbearren.
    • #1414974

      alan.b – when I get a new computer, I partition the C: drive into a C: and D: drive. I then move my documents, music, videos, desktop, and downloads folders to a users folder that I create on the D: drive. That way, if I have to restore a backup drive image on C:, my user files are left intact. Also, I don’t have to image my computer just to back up my user files – I synchronize them daily between two computers or HDD’s.

    • #1414981

      I’ve posted this basic info before, but it bears repeating in this post.

      Like kgiov, I always create a logical D partition on my laptop drive, when I get a new one, to hold all my data, keeping the OS and programs on the C partition. That way, if I have to do a restoration because of an unrepairable OS glitch, I can restore only the C drive & not even touch the current data backup on the D drive.

      Like alan.b, I always do a drive image immediately BEFORE doing Patch Tuesday, in case anything goofs up with the patches, to my pocket-size external HD. I also do an automatic daily backup to my larger desktop external HD, with a new image of the C disk, which runs in the wee hours of the morning.

      After a week or so- and after the Windows Secrets letter describing any problems with Patch Tuesday patches (fortunately, none have ever surfaced on my computer)- I re-image the entire system to both external HD’s, do a copy of my data to the smaller EHD, (confession- borderline OCD personality), and swap it out with last month’s copy on my second pocket-size EHD, which I keep in my safe deposit box for offsite backup. When I travel, I change the daily external early-morning backups to the pocket-size EHD and take it with me. This has served me well, as I’ve had HD failures on trips TWICE, with previous laptops. In these cases, I get overnight shipping of a new internal HD, restore my backup to the new internal HD with my boot disk (copy also carried in my computer case) and the pocket EHD, and am up and going again in 36 hours, at the longest.

      IN ADDITION, when I work on a new file or modifying a file in my D partition, I immediately copy it to a 128 GB flash drive using Windows Explorer. This way, if I get a crash in midday that involves the D drive, and I have to restore the image from the EHD, I can search through files I think I’ve worked with on the flash drive, and look for ones with the current date, and copy them over. I’ve also accidentally deleted files, including from the recycle bin, or hopelessly messed up their format (mostly with spreadsheets), and can just copy over the file from the flash drive to quickly get my original file back.

      If I were REALLY paranoid- or more of an OCD victim- I’d unplug the flash drive after each use, and only plug it in only when making a backup, as the only recovery scenario I don’t think I’ve covered is the power surge that fries ALL my equipment at home. I’d still have the offsite backup to restore to a new system, but I’d lose any new files or file modifications made since the last offsite backup.

      I don’t do backups to the cloud for two reasons- security, and the much slower speeds over the web, were to I do a total restoration over the Web, vs. a USB 3.0 EHD.

      • #1415007

        Clonezilla has saved my butt on several occasions! The UI is not for the faint-of-heart, but it gets the job done.

        • #1415193

          Clonezilla has saved my butt on several occasions! The UI is not for the faint-of-heart, but it gets the job done.

          CloneZilla Live is well suited for Linux backup and recovery.

          For Windows, I prefer Macrium Reflect. I do my Windows backups from within Windows. For Linux, I am not aware of software which can accomplish this.

          So for Linux I have little choice. CloneZilla Live, even with its text driven interface and its arcane drive naming, is one of the few effective options.

          But for Windows, such arcana is completely unnecessary and unproductive. Macrium Reflect’s user interface is much easier to use and less user-error prone.

          -- rc primak

    • #1415123

      I created a system image by taking a snapshot of the entire computer with the side panel removed (Canon A590 @ max. resolution). However, this is not helping me to get my Windows setup running again. What am i doing wrong here? 🙂

      • #1415126

        I created a system image by taking a snapshot of the entire computer with the side panel removed (Canon A590 @ max. resolution). However, this is not helping me to get my Windows setup running again. What am i doing wrong here? 🙂

        You have to take photos with both side panels removed. We all know that.

        • #1415468

          You have to take photos with both side panels removed. We all know that.

          Don’t forget to put the film in the camera as well!

    • #1415136

      bbearren – you said: “I highly recommend (as do many others here) developing a drive imaging regimen and using it with regularity. It is well worth the effort.”

      So, if it works so well how come that owl ain’t smilin’?

      Regards

      • #1415185

        bbearren – you said: “I highly recommend (as do many others here) developing a drive imaging regimen and using it with regularity. It is well worth the effort.”

        So, if it works so well how come that owl ain’t smilin’?

        Regards

        It took all my persuasion just to get him to pose for the photo. He said, “I am smiling.”

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
        We were all once "Average Users".

        • This reply was modified 5 years, 10 months ago by bbearren.
        • This reply was modified 5 years, 6 months ago by bbearren.
    • #1415176

      I can’t be bothered to make frequent system images. I make 2 or 3 that contain the bulk of the installed software that I care about with the computer in pristine condition. If I have to do a restore, I just live with the updates. At least I don’t have to track down the software disks and codes. I am much more compulsive about my user files – automatic synchronization between 2 computers every day, with another synchronization of all user files for family members to a second HDD, and occasional backups of all user files (and the drive images) to an external drive that I don’t otherwise keep plugged in, in case of a power surge. In fact, I used to make lots of drive images, but then realized the main reason I was restoring old images was that my computer was slowing down, and decided that for the most part I don’t need my most recently updated C: drive.

    • #1415279

      I’ll catch a couple of these in one post. I put the OP in the Maintenance Forum because it applies to all Windows versions as well as other OS’s. Regardless of which OS you’re running, restoring a known-good drive image is always faster and simpler than repair/reinstall or a reformat/reinstall.

      I use Task Scheduler to run Window’s built-in Cleanmrg.exe with the sagerun switch to get rid of run-of-the-mill temp files on a daily basis. I do that because I also use Task Scheduler to run a MyDefrag daily defrag script that covers my system logical drives (I also run monthly scripts for both system and data logical drives) and I don’t see much point in defragging temporary files. And I do these things so that I can create a new lean and defragged drive image whenever I want without a lot of extra fuss.

      About every third or fourth drive image set, I run sfc /scannow first. I do this to insure that I have a “known-good” logical drive when I make a drive image. I recently had one of those sfc runs turn up bad, corrupt files that couldn’t be repaired. I had to go back about 4 images to find one that ran a good sfc /scannow. I covered that in this post. I also run chkdsk /r from time to time for similar reasons.

      Six minutes is about the best I’ve heard of in terms of a image restore.
      I couldn’t agree more about taking the time to learn how to make and restore your own images.
      Nothing beats a well thought out backup regimen.

      My OS restore is quick mainly because that logical drive contains only the OS; no Program Files, no Users, no ProgramData. In the case outlined in the OP, I knew that the damage was in the registry, because I was the culprit, so I also knew that I only needed to restore the OS logical drive image. The Users System Folder and ProgramData are on a separate HDD and logical drive. The Program Files System Folder is on another logical drive. I didn’t need to restore either of those drive images because the damage was confined to Windows only.

      That is so wrong :o:
      I always image immediately BEFORE I permit a Patch Tuesday, and especially before emergency patches.

      No, it’s not wrong, it’s just not the way you do it. It works fine for Ted. He has his data separated, his system doesn’t change much, and a month-old drive image restore just puts him back to before Patch Tuesday, for all practical purposes. We all have our own reasons for doing the things we do.

      I make drive images more frequently, so in the event of a MS Update [mess], I’m not far away from being current with my last image. I also have my data completely separate, so that doesn’t enter the equation. The main thing is to have a system that works for you, and to make regular use of it. That’s the point I’m trying to promote with the OP.

      As alan.b and Comedian both discussed, keeping data separate minimizes risk and increases survival opportunities. But all in all, for me it comes down to having a regimen with which one is comfortable, because that increases the likelihood of making regular use of it, and that is the real key – making it a practice and routine.

      One of the main reasons I dual boot Windows 7 and 8 is that I can work on either OS from the other, and also keep my desktop available at the same time, like while I’m making drive images, or running chkdsk on one of the partitions used by the other OS. It just makes it that much easier for me to keep my system clean, lean, quick, reliable and recoverable, as well as keeping it available.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

      • This reply was modified 5 years, 9 months ago by bbearren.
      • This reply was modified 5 years, 6 months ago by bbearren.
    • #1415346

      I do mine right after I apply patch Tuesday patches. In this way if something else crashes me sometime after the patches, I can get right back to work. If the patches themselves crash me I restore the previous month’s Image that I created right after the last patch Tuesday.

    • #1415351

      To address the issue of the timing of creating a drive image as part of your backup regimen, the truly relevant issue is summed up in just two words: frequently (no less frequently than once a month, IMO) and regularly (don’t skip creating an image, especially if your frequency is monthly).

      Without emphasis on those two, you’re lessening your chances of relatively painless recovery from things that go bump in Windows.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

      • This reply was modified 5 years, 9 months ago by bbearren.
      • This reply was modified 5 years, 6 months ago by bbearren.
    • #1417856

      In my experience (Image for Dos, Image for Windows & Easus Backup) an image is vital, as long as you don’t really, really need it. I have made images, and tested them by restoring right away, no problem. However, when the chips have been spilled all over the floor the restore failed miserably with both Image for DOS & Windows, so I switched to Easus. I just had a major problem restoring Win 7 on an HP Mini, using brand new recovery disks from HP. How could that go wrong? It did. Was I worried? Well yes I was. Before starting I’d made a system image, and a file backup too, using Easus. I was covered, right? Well I thought so, but when I tried to restore just a couple of hours later using Easus I got, “The layout of the original disk does not match the target disk. Please recover to an empty disk and perform recovery to recover system.” I tried an image made a month ago, same result.

      I don’t know what the “layout” means, it’s the same disk, same NTFS file system. Easus haven’t answered my querry yet. HP doesn’t do e-mail for out of warranty products, however, if I’m prepared to spend half a day on the phone to Bangalore I’ll get to speak to a techie in Indlish. HP Forums seemed like a good place to start, 24 hours later there has been just one, irrelevant response. Right now the HP is a paper-weight.

      But I wouldn’t want to put anyone off imaging, it does give you a warm, fuzzy feeling, until it doesn’t.

      David

    • #1417859

      Probably the HP recovery attempt changed your disk. Did you check what partitions you have now and compare with what you had before?

      • #1417882

        Probably the HP recovery attempt changed your disk. Did you check what partitions you have now and compare with what you had before?

        That could very well be part of the problem. See this thread , particularly post #6.

        Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
        We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
        We were all once "Average Users".

        • This reply was modified 5 years, 9 months ago by bbearren.
        • This reply was modified 5 years, 6 months ago by bbearren.
    • #1417864

      The “layout” usually refers to the main partition on your hard drive not being the same size as it was when you created the backup image. So, if you created the backup image on, say a 500GB partition and you’re trying to “restore” that image to a smaller partition (say, 450GB) then you would get that error message.

      Here’s an example that happened to me once a few years ago. My laptop had Windows 7 on a 500GB hard (labeled as my C: drive, as usual). I created a backup image. Later, i used Windows built-in disk management to shrink that 500GB partiton and create a second partition to hold photos and videos separately just in case something went wrong with Windows.

      Months later, i decided to “restore” the backup image and, guess what, it didn’t work because my hard drive “layout” had changed. This is offered as one example of what might go wrong when trying to restore from a backup.

      • #1417871

        The “layout” usually refers to the main partition on your hard drive not being the same size as it was when you created the backup image. So, if you created the backup image on, say a 500GB partition and you’re trying to “restore” that image to a smaller partition (say, 450GB) then you would get that error message.

        Here’s an example that happened to me once a few years ago. My laptop had Windows 7 on a 500GB hard (labeled as my C: drive, as usual). I created a backup image. Later, i used Windows built-in disk management to shrink that 500GB partiton and create a second partition to hold photos and videos separately just in case something went wrong with Windows.

        Months later, i decided to “restore” the backup image and, guess what, it didn’t work because my hard drive “layout” had changed. This is offered as one example of what might go wrong when trying to restore from a backup.

        These recent imaging apps usually handle image restoration to a different sized disk or partition without any issues. I don’t know EaseUS, but Acronis does it without any problems whatsoever.

        • #1417886

          These recent imaging apps usually handle image restoration to a different sized disk or partition without any issues. I don’t know EaseUS, but Acronis does it without any problems whatsoever.

          Yes, Acronis is quite flexible in that respect as long as the data fits in the intended destination it will restore it.

    • #1417875

      Mmm … like i said, it was just one example of what might[/I] go wrong …… 🙂

    • #1417880

      In my experience with Image for Windows and Image for DOS, I have never had a failure to restore an image; no restore failure of any kind. I have had failures in image creation, and every single one of them were due to the drive having bad sectors. In one case the drive could not be corrected by chkdsk, but my last images from that drive were all current. This was a case where it was really, really needed, and nothing was lost. Over the years I’ve had a few of those really, really cases, and I’ve never been disappointed.

      Having an imaging regimen plays into a total maintenance routine that allows one to avoid major problems or loss. Bad sectors can go unnoticed for an extended period of time except for when I run Image for Windows or Image for DOS. They both will Fail creating or validating an image on a drive with bad sectors. But my imaging regimen insures that I have a recent drive image at the ready. Of course chkdsk /r will also discover if there are any bad sectors, but I create drive images more often than I run chkdsk.

      Image for Windows and Image for DOS both allow for restoration of an image to a different drive geometry. It’s in the GUI in the menu options for restoration. For example, my laptop has a motherboard capable of BIOS or UEFI, and was shipped with BIOS/MBR setup. I wanted to convert it to UEFI, which requires that the drive be wiped and converted to GPT. This was easily accomplished booting Image for Windows from a thumb drive.

      Image for Windows and Image for DOS also can facilitate a total drive image, by which I mean the entire drive, all partitions and partitioning geometry, and all data contained within those partitions. This drive image can be restored to any drive that is at least the same size or larger than the original drive. As for partition/logical drive images, they can be restored to any partition/logical drive large enough to contain the data. For example, my OS logical drive is 61,435MB, but I can restore the image to a logical drive as small as 28GB.

      I’ve been using the TeraByte imaging software for well over a dozen years (since the end of the last century), and I’ve never had an issue with restoring a drive image to a good drive, regardless of layout/geometry differences. Of course, I’m very familiar with how it works, what I’m doing, and what my options are in most any given situation.

      There are others on these boards who use different imaging software, some free and some paid, with similar results. For those of us who rely on drive images, it’s tried and true and we all recommend drive imaging regularly. It’s not just warm and fuzzy, it works time and time again.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

      • This reply was modified 5 years, 9 months ago by bbearren.
      • This reply was modified 5 years, 6 months ago by bbearren.
    • #1418229

      I set Windows Update to notify only. I’ve never had an update pushed to my knowledge.

      Always create a fresh drive image before making system changes/Windows updates; you may need to start over!
      We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.
      We were all once "Average Users".

      • This reply was modified 5 years, 9 months ago by bbearren.
      • This reply was modified 5 years, 6 months ago by bbearren.
    • #1418765

      There were a few “stealth updates” for a period, I think it was in 2010. Susan Bradley and Woody Leonhard were both actively watching the issue at the time, and neither has mentioned “stealth updates” much since about 2012. I personally got the Updates Mechanism in Windows XP and Windows 7 “stealth updated” twice (around 2010-2011), but never recently.

      I placed Windows Updates on Notify but Do Not Download in about 2008, after a particularly nasty System Kernel Update disaster which forced me to reinstall Windows XP on my laptop. Turned out to be an outdated driver issue. Never again, I vowed.

      -- rc primak

    Viewing 19 reply threads
    Reply To: The value of a recent drive image

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: