Okay, things just seemed to get a little weirder. Following Brian K’s suggestion, I used MR v6 Free to mount the “1-Data(None) drive” to see what was in there. First, used MRv6Free to do a Full Image to an external usb drive, which went just fine. Then I mounted the “1-Data(None) drive” on the image. Here is what I found: 1. Before mounting the image, the 250GB SSD (image SOURCE) “1-Data(None) drive” was showing a RED colored bar w/ 93.3MB of the 100MB partition used. 2. Using the new image on the external usb, MRv6Free assigned “F” to the mounted “1-Data(None) drive”. 3. Once mounted, Windows Explorer showed the mounted Drive F as containing a total of 89.3MB (NOT the 93.3MB that MFv6Free had shown on the SOURCE 250GB SSD before making the image). 4. Mounted “Drive F” had two folders and one file: Folder “Boot” with 13.9MB; Folder “System Volume” with 20MB and the System File “bootmgr” with 375KB (.375MB). 5. 13.9MB + 20MB + .375MB = 34.275MB 6. So, before making todays Full Image, MFv6Free showed the “1-Data(None) drive” with 93.3MB used – bar color RED. Once the IMAGE of the “1-Data(None) drive” (external usb drive) was mounted as “Drive F”, Windows Explorer showed the “F” drive as using 89.3MB. BUT, the sum of the folders and file in drive “F” only shows about 34 to 35MB used. 7. AND, after unmounting the image of “1-Data(None) drive” (Drive “F”) MFv6Free IS NOW SHOWING THE SOURCE 250GB SSD DRIVES’ “1-Data(None) drive” AS CONTAINING 89.3MB – WITH A NICE BLUE COLOR BAR!!!! UPDATE: Just rebooted my laptop. When I opened MRv6Free again it is back to showing the SOURCE 250GB SSDs' “1-Data(None) drive” with 93.3MB used of the 100MB partition - with a RED colored bar! This is driving me nuts. Again, I just need to know if this is something I need to worry about. Okay, I know that both Brian K and Raza0007 already said I didn't need to worry about it, but I'm a bit obsessive and one more assurance would be appreciated. Thanks!
I don't think it uses the "boot" folder when the PE stuff is on the OS drive, just when it's on another drive. If you have a "boot" folder, be careful... it may belong to someone else. The safest solution would be an uninstall followed by a reinstall... I'm not sure about the other options you mentioned.
OK, I will try...and the boot folder on the C drive is only for Reflect and contains 2 folders. Anyway, I think I will do an image backup, and then uninstall Reflect Free V6 and start over as you suggested. I can even use REVO, but, perhaps I should just let win 8.1 uninstall. If I had to, I could even restore a ver 5 image I took just before my ver6 update...that could even tell me if anything will make the LAN work...and yes, I know, I am not using the LAN, but wanted to see why I can not add the driver!
Just make sure you have Macrium delete EVERYTHING when you do the uninstall (it will ask)... you may be able to keep any schedules (XMLs) you've created, I forget, but dump the PE files. The "boot" folder you describe sounds like it belongs to Macrium only (I don't see that on Win8 ).
OK, I will do it. Also, I do not keep any XML as I ONLY do an Image a few times a Month, or when I am going to try something. As I said, I am not going to do too much more regarding this as I do not NEED Ethernet...now anyway.
Try mounting the image again. In Folder Options, temporarily "Show hidden files, folders and drives" and also unhide "Hide protected operating system files". You need to account for the full 90 MB or so.
MPSAN - I noticed that too. I saw it as an "Advanced Option" when running a restore operation. I checked yes, and as the restore progress log came up, under "Operation 2 of 2" there was a section that said "SSD target detected Attempting TRIM operation ..." and then no indication if the TRIM operation was successful. The next line just said "Processing: [the file name of my restore file] and later the line after that just said "Restore completed successfully". So MF v6Free gives no indication of if it actually DOES successfully run the TRIM operation. It's really not a big deal. I just run the TRIM routine included with my SSD drive (Samsung Magician). It only takes a few seconds and that way I know it's done. I will keep that MF v6Free TRIM checkbox checked, however. Can't hurt!
Actually, I did enable show hidden files, folders and drives and I also unchecked the box for "Hide protected operating system files" BEFORE I got the results I reported above. Everything seems to be running normally ..........
Actually, I did enable show hidden files, folders and drives and I also unchecked the box for "Hide protected operating system files" BEFORE I got the results I reported above. Everything seems to be running normally .......... UPDATE: I decided to try restoring my 250GB SSD with an image I made a few days ago. I used MR v6Free to browse to an image file, on a usb drive, that I wanted to try restoring from. I was happy to see that MR v6Free displayed the “1-Data (None)” partition of the image with a BLUE bar and showed 89.3MB used of the 100MB partition. Good, I thought, let’s try restoring the drive with this image. I did a restore using MR v6Free and everything went smoothly. Windows booted normally. However, after the image restore, MR v6Free still shows the RESTORED 250GB SSD with the “1-Data (None)” partition having 93.3MB used of the 100MB partition (RED bar). I used MR v6Free to mount the image file I just restored from – making sure I did check the “Show Hidden System Files” box that MR v6Free offers when mounting a drive. [Settings in Windows Control Panel also still set to show hidden and system files.] MR v6Free again assigned drive letter “F” to the “1-Data (None)” partition. Using Windows Explorer, I checked the Properties of Drive F. Windows Explorer shows Used Space @ 89.3MB, Free Space @ 10.6MB, and the Capacity of the “F” drive @ 99.9MB. Windows Explorer again shows the “F” drive containing a “Boot” Folder holding 13.9MB; a System Volume Information folder holding 20KB [I must have misread that on my last post because I thought it said MB before.]; and a System File titled “bootmgr” containing 375KB. In addition, there is now an additional text file titled “rescuepe.log” – but that only contains 1KB. I assume the addition .log file is a result of the image restore I just did. So, especially with I believe was my previous mistake on the size of the System Volume Information folder, the “F” drive seems to be showing even more data that I can’t account for. The good news is that the restored image seems to work just fine. Am I in trouble?
Well, if your restored image were not working you would be in trouble but since it is working fine you are OK I guess. The only thing is you are no closer to understanding what is going on with your anomaly.
Slacker Sonny, My mounted SRP is reported in Windows Explorer as having 24.1 MB of used space yet the contents only add to 14.2 MB. The same contents as yours. I can't explain our numbers. I doubt it is a problem. Our OS boot and that's what the SRP is supposed to do.
I took this quote from one of your earlier posts. As I mentioned before, you do not need to be concerned about the red color, however, I can understand why you want to get to the bottom of this system reserved partition's increased size. I have a question, when you cloned the 500 GB drive to the 250 GB drive, did you enable encryption on the smaller drive, like Bitlocker? System Reserved Partition holds the important files to decrypt your hard disk, so that may account for the size increase. The discrepancy in the sizes between the mounted image of the drive and the actual size being reported by MR6, maybe caused due to Macrium excluding certain files in the image creation. Do a sector-by-sector image (i.e. make an exact copy) of this partition, then mount it and see if there is a size difference. If you are still unable to figure it out I would recommend you leave it be as this partition is managed by the OS and you do not need to worry about it. See these links on some good info on the SRP Link 1 Link 2
I do not know about Win 8, but on windows 7, the boot folder is created by the OS, it is located either on the C drive or on the special reserved partition. It is associated with the bootmgr and used in the boot process. I would recommend not deleting it. Macrium only uses this folder and puts its own subfolder inside, labeled Macrium. You can safely delete the Macrium folder.
Slacker Sonny, With Win7 and Win8 I don't have a SRP. I've found things simpler without the partition and if you aren't using Bit Locker the SRP can be easily removed. But not by a simple delete. You have to copy the booting files to the Win7 or Win8 partition before you delete the SRP.
OK, well, I guess the boot folder on my C: drive was created when I installed Win 8.1, and all it contains is the Macrium Folder.
I've installed it under W8.1 and there is no "boot" folder on the OS drive... but the PE files downloaded are indeed on C: (ProgramData/Macrium)
I plan to do a clean install of Windows 10 when it arrives next month. Do I need to uninstall my Reflect license before doing that, or will it still be seen as the same PC? (this will be my first OS upgrade with Reflect)
Well, I do have a boot folder on my C: drive root. I do see the files in Programdata/macrium/reflect/windows kits/8.1/assessment and deployment. I "think I can remove it, and try again...still I will do an image before I start playing... Cover Me, I'm Goin in!
Yes, I have Win 8.1 64 bit installed and have 4 partitions on my GPT 512GB 850PRO SSD. And yes, it is UEFI.
An observation. I have a test Win8.1 installed in UEFI mode. The OS partition doesn't contain a boot folder, not even a hidden one. After installing Macrium 6 Free there is a visible boot folder, containing a macrium folder. It contains 208 MB of files and folders. C:\ProgramData\Macrium\...... contains winpe.wim. MPSAN, it looks like we have the same files and folders.
So, I CAN try to delete the boot/macrium and the assessment and deployment folders and see if it will let me rebuild.
