MPSAN, Saving the 300 MB is negligible but it does allow one less partition in your entire drive backup. I do it because it's tidier.
Thanks Brian. (edit: I think the trial version may not allow for deleting partitions etc) For some reason I'm getting an "invalid parameter" error relating to the HD ID, though the docs seems to confirm your example. I've tried specifying it as 0x0 instead of 0, but no difference..
taotoo, Try running tbosdt.exe as an Admin. (right click and Run as Admin) Try... list hd 0 Edit... For deleting partitions it has to be TBOSDT for BootIt and not TBOSDT.
I do agree, but my 5 partitions only take 8 minutes. Perhaps this is something I can do later. Not sure which one is the "extra" partition I can remove.
Thanks Brian - yes the docs do seem to suggest I'll have to buy BootIt - not sure I'll go ahead as I was in two minds whether I wanted to attempt it anyway (MPSAN's sig was swaying me towards doing so...)
Relect 6 Pro: Bluetooth mouse not working when boot Macrium from USB Flash drive. Win 10 Pro Does anyone have a solution?
I assume if you know the DRIVER name you can always add it when making that Recovery UFD. I'm surprised REFLECT didn't find it when it makes it... but I'm not surprised at anything when it comes to Windows 10. Edit: Silver, I'm not sure when the generic M$ driver became available but I'd probably be sure that the UFD you're making is based on the latest WinPE (v5.1?). The latest Win10 WinPE has not quite settled yet as far as REFLECT is concerned.
Does it workk when booting from a CD ? If then try using some utility such as Flashboot, Win2Flash or UltraIso (there are also free ones such as Rufus or http://unetbootin.github.io/ ) to convert the .iso equivalent to the CD into a USB bootable key.
Get a "recovery mouse" with a tail (lead) for when you really need to boot from your flash drive. I wouldn't be trusting to a bluetooth mouse for recovery; they are too unreliable. If you really want a wireless mouse you could try a non-bluetooth one. These look just like wired mice (mouses?) to windows so you don't need extra drivers.
Agreed. My Logitech BT mouse hasn't worked on my ThinkPad Yoga Win 8.1 system either, when using the MR boot option; have to use the touch pad.
hi but is there a option in the winpe v6 to exclude in the backup the pagefile.sys and swapfile.sys files? thanks
So, I did a full Image with V6 Free of my win 8.1 before I updated to Win 10. All is OK, and I have not had any issues yet with Win 10. However, I do have 5 partitions now on my SSD where win 8.1 had only 4. My question is ... IF I wanted to restore my Win 8.1 would I have 4 Partitions again, or would it keep the 5th that win 10 created? I am just asking as I am not looking to go back...just wondered what would happen. I suppose I CAN wipe my SSD and then restore. I assume that, too, would work.
Assuming you imaged the entire disk, rather than picking and choosing some partitions, then you would have the original 4 partitions. Was it an entire disk image? If that's the case, I wouldn't see any need to wipe the disk.
Just a clarification. The latest version of WinPE that you can build with macrium reflect, as of today, is v5.0, based on Windows 8.1 kernel. Furthermore, there is currently no official release of Windows 10 based WinPE from MS, as of today.
It depends entirely on you. If you restore the entire HDD, then everything on your HDD, including the partition structure, will be erased and replaced with the partition structure in your image. So, you will end up with 4 partitions. If you choose to restore only 1 partition from the image, then only that particular partition will get restored and you will retain your current 5 partitions structure.
There is no option. During live (hot) imaging with Macrium, by default (intelligent sector copy option) the pagefile.sys file and the hiberfil.sys file are excluded from the backup. It wouldn't make any sense to include an option for this, as there is no logic in backing up these files. These files are session dependent and their contents are refreshed on every reboot in any case. There is a certain bit of confusion about this when doing cold imaging with Macrium, and I have been unable to obtain a clear answer on this. Some say that Macrium includes pagefile.sys and hiberfil.sys files during a cold image, while others claim that they are only included as sparse files i.e. their size is actually zero bytes in the image. The confusion exists because the image file of the system partition created by Macrium is always a couple of GBs larger when done through cold imaging, vs hot imaging. I meant to do some tests on this of my own but just could not find time. And since I always do hot imaging so this issue is irrelevant to me. By the way, if you really for some reason want to backup the contents of the pagefile.sys and hiberfil.sys, then you need to do a sector-by-sector copy of the partition, or enable "make an exact copy of partition" option in Macrium. Keep in mind that this option will also backup all the contents of the unused free space in the partition as well.
thanks Raza i want to make a test too , create a cold image and after delete pagefile.sys and swapfile.sys and create another image and compare them
Raza0007, I think this be due to the VSS image not containing all the files present in the cold image. There are quite a few files and folders not backed up in a VSS image. For example, I created a VSS image of Win10 and then copied a 3 GB file to C:\Windows\SoftwareDistribution\Download. A subsequent VSS image was the same size as the image created before the file was copied. C:\Windows\SoftwareDistribution\Download is a VSS excluded folder.
Brian, I actually did some of research on this topic a while ago but it has only added to my confusion. You are right that Macrium and other backup utilities are supposed to ignore C:\Windows\SoftwareDistributation directory from snapshots as well as backups as per Microsoft recommendations. The problem is that in this thread Nick, who I believe is one of the lead developers and CEO of Macrium, states quite clearly that Macrium does not follow these Microsoft recommendations. This is the reason I am still not satisfied with the resolution of this issue. Edit: I had not realized that my SoftwareDistributation directory is over 0.5 GB! So that accounts for half a gig of difference, that still leaves about 1 GB difference to be accounted for.
Raza0007, I wasn't using Macrium for my tests. Can you check the size of your System Restore points, if any, as VSS excludes them as well. The SVI folder. Here are my VSS exclusions in IFW. Quite a few.
I have my System Restore switched Off, so no restore points. Was this log that you attached provided by IFW or you got it from Windows logs? Macrium does not provide such a detailed VSS log unfortunately.
