Yeah, fixed now. Someone asked about it on the TeraByte Unlimited Forum and they said that it was a leftover after doing a search and replace. I guess they didn't think about the previous version having an 'a'.
After having used imaging for years to faithfully do my backups and having done the odd restore, I realise I still have only a very thin understanding of the basics. Earlier today I restored an image onto a new pc with slightly different hardware. So I assumed there might be some driver issues. Instead of rushing in, I did a test restore a few days ago to see how it would go. Initially I did this offline but later ran windows update. This morning I did a new image with the latest changes included and did another restore thinking that prior state was not relevant to me . I have been told very bluntly, that was a stupid move given that I had updated previously and activated my windows license. Anyway, while windows is still showing as activated, my Office 2016 is having none of it and wants me to run the validation again. This fails online and the phone validation is also unsuccessful. Since you can't talk to people anymore, I guess I need to buy another office license. However this leads me to question something regarding existing images in general. Having now moved to the new pc, I can start a new stain of images and obviously they will all be with the same hardware set. However any of my existing older images would again face the same issues described above. Now, I am not likely to restore any of these 6 month old images and if I needed a file I could use other means but in principle how do others deal with this. Does that mean that any images taken prior to moving to a new pc are likely to have these license issues?
beethoven, Did you deactivate the Office license on your previous computer prior to creating the image? https://answers.microsoft.com/en-us...o-new-pc/98ded6ce-ccb3-4d77-aec9-4f4b21026d2a I recall I deactivated my Win10 license too.
Brian, no I did not deactivate the license prior - I did not consider that. However, while I could have done so in this case, I certainly do not do that prior to taking a regular image. It seems to me that any "regular" images taken that way become second class images. Also, I am still using older versions of office (one time purchases as opposed to subscriptions) and looking at the link and comments it is not clear to me whether you need to uninstall the product or release the license somehow. Some of the comments in the thread seem to be from either the old days or overseas, I was only able to do this online or over the phone but automated and had no luck. I am using Bvckup for file backups and it was so easy to deal with the license issue in that case. They detected the hardware change, asked the reason (all online) and then transferred the license to my new setup.
After some time of usage of this product i wonder about the Deployment Tool Suite, since it has not been used, to my knowledge. I guess it is safe to uninstall for me as a basic user - backup and restoring, of IFW?
I wouldn't remove it. It's only 10 MB and I find it very useful. But IFW backup/restore doesn't use it.
Since IFW does not use it, and i dont use it, i can uninstall it without affecting IFW in any way - as is?
Thanks! Well, i have been thinking of not bother just because it is so small but, its there and... well i do not need it so why keep it .
I find it very useful as I have lots of partitions that aren't seen by my booted Windows OS. I can access these partitions and copy data to and from. Either with scripts or tbexplo.tbs. I use the fixboot.tbs script to create booting files for restored Windows partitions that don't have booting files. OSDTool.tbs is useful when copying an OS to different hardware. It can remove and install drivers. chgdtype.tbs is useful for converting partitions and systems from GPT to MBR and vice versa. Edit... tbexplo.tbs does Partitioning as well as Exploring.
Well, downloaded and installed Image for Windows. My 256gb nvme system drive contains windows 10 and Linux and i have 1TB HDD as a data drive. So dual bootin Win and OpenSuse. Using Grub as a bootmanager. So for testing purposes, i made a full backup of my system drive(win/linux) -> to my HDD and i used PHYlock. Total imagefile(.tbi) size was 65 GB and it took only about 7 minutes to make. Pretty impressive i would say. Because of nvme -> HDD. Then i did bootable USB and tried to restore imagefile back. Restoring the imagefile went just fine. I'm kinda impressed about quality and speed of this product. However, it's not so user friendly as one software i'm currently using, especially when restoring an imagefile. No biggie for me tho, but for not so tech-savvy ppl it can be difficult to understand restoring process. If i'm understanding this right, IFW does have an ability to add itself to windows own recovery environment, so you can easily restore an imagefile there. This is a big plus. I'm seriously consider to buy full license of this software. @Brian K When restoring an imagefile, there's an option to do "automatic" and "normal" restore. When i clicked "help" button to see, what are differenced between these restoring methods. It does not show anything? I clicked "automatic" and it worked. So what's difference between Normal and Automatic restore ? (im using USB recovery environment).
moredhelfinland, I don't use Automatic as it only saves seeing two screens and I want to see the Restore Options screen every time. Page 92 in the IFW manual says... If you buy the software I strongly suggest you get the "Special Bundle". It's only $10 more than "TeraByte Drive Image Backup and Restore Suite" and the included BootIt software (BM and UEFI) is incredibly useful. You can run BootIt Partition Work standalone or inside IFL.
@Brian K When restoring an imagefile, there's an option to do "automatic" and "normal" restore. I've always used Automatic as it defaults to that. It still displays the target drive prior to restoring. But maybe I'll switch to Normal in future.
I did a test with Automatic today. With IFL I copied a data partition to free space on another drive. On booting into Windows there was a signature collision and the copy wasn't seen. The test was repeated using Normal and the Options screen was seen so Change GUID could be selected. No signature collision this time. But in most image/restore cases you will be OK with Automatic.
Never heard about signature collision before, but thewindowsclub has written an article about it. Good reading for future use. I have used the diskpart many times, but did not knew there's an option to change disk ID by using command: Uniqueid disk
I agree. The first time that I purchased TeraByte Drive Image Backup and Restore Suite years ago, I didn't include the bundle. But years later, I purchased it again when there was a sale on and included the bundle. From memory, I think it was cheaper for me to do it that way at the time. It contains a lot of hidden gems that I wasn't even aware of at first.
Today i changed disc on one pc and thereafter rearranged some things, installed IFW. After installing it, as is, the way with choices but not changing anything, i can not create a Wim file. I use the option - create/update TB Wim.RE, when i click it, the frame that should become visible just flashes very rapidly, thats it. It never shows up so i can not do anything. When using the other option, Create image for Windows boot media, the RE option, it stop after a short time saying, DISM not found. Whats up, i dont understand this. This is without security on the pc, no AV
pb1, Just a few questions. Do you have TBOSDT on this system? Do you have a RE partition? Can you run this from an Admin command prompt... Code: reagentc /info Can you post the output?
Win.RE enabled. Do not know what TBOSDT is but as i said, i installed IFW as is. Yes all 4 partition are there, boot, reserved, C: and recovery that is almost 600MB. I just installed Macrium and it worked fine to recover, and works fine, so i guess this is an IFW issue.
Yeah i realized that, it is present. And the rec.partition is about 1.5GB and not 600. This is odd since i do not have any security that could cause this, or anything else that could block. Searching the net for DISM not found is fruitless, it only has info about Dism not working or missing files for it. An sfc scan says ok. This is on W11 latest build, on d.o for W10 it worked ok.
Even more odd is that i can not restore with Macrium via windows inbuilt recovery path, the one in settings that boots to recovery, only via Macriums own boot meny or media.
