I have always used the pe version for the OS I'm running, on win 7 I used the win 7 pe, win 8.1 I used the win 8.1 pe & now I'm on windows 10 I was trying out the win 10 pe. All the other versions work fine, only the win 10 pe does nothing after showing the boot screen & seems to halt the entire system. I have to hit the reset button on the PC to reboot it.
Did you get to see the blue Windows flag? (I did not, an entirely blue screen with Windows 10 PE instead, while 5.0 works fine)
Yeah I see the windows boot screen that has the spinning dots underneath the slanted blue windows logo then the lights on my keyboard & mouse flash on & off, the screen then goes off as if the monitor has powered off & finally the screen comes back on but is just a black screen. I left it like that for 20 mins & tried to ctrl-alt-del to reboot the PC but it was frozen so I had to press the rest button on the PC case. I have never ever had any issues with previous reflect pe kits, the only one that doesn't work is the win 10 pe.
The problem with using WinPE 3.1 ["7"] in Windows 7 machines is that you have to add the USB 3.0 drivers. In my case, this doesn´t work with Macrium Free 6.1.871. The program apparently adds the drivers from the selected folder, and the process to create the ISO file finishes with no errors. But when I boot with the WinPE 3.1 UFD, the program doesn´t recognize the external USB disks connected to USB 3.0 ports. In past versions, it worked well. Macrium even added automatically the correct USB 3.0 drivers. Also, Macrium doesn´t search for drivers in the internet. The Terabyte WinPE/RE builder does this automatically for USB 3.0 drivers. WinPE 10 works well in my Windows 7 machine, no matter if it was built in the same machine or in a Win 10 laptop.
I wish it was that easy No, this is a hardware/timing interface with the SSHD. Since those disks use not only a high speed smaller cache (32mB), they also use a 4gB NAND FLASH cache in front of the spinner for speed with recurring reads, making it an SSD look-alike for common reads. It may be the internal NAND/spinner interface that's causing the output to hang when Windows wants more of that data. If they have the hardware, it should be easy to replicate. Then again there's an outside chance that only the drive I have is doing this very strange thing.
...and let's bring this to a close. The original problem was accidentally mis-described by my associate. To clarify... The original problem did not concern a Seagate SSHD, the real image holding disk was a WD BLACK 750mB 2.5" SATA III drive... SSHDs were never involved. Reaching back into my "closet" I found an exact same drive (same part #). I put them both in the original system, filled them up with Macrium images and re-ran the test with a Macrium PE10-based Recovery Media. The original failing disk continued to fail in the original manner, and the newly found twin ran perfectly, even in each other's SATA III ports. Folks, this is purly a single drive anomaly/failure using WinPE10... nothing more. Very sorry for the original mis-information.
I am having a lot of problems with 6.1.871. Firstly, my scheduled backups take a long time to complete (15 minutes for an incremental, used to be 2 minutes). Secondly, when I click the Restore tab, Reflect cannot find any of my images (some are on a NAS drive, some on a portable USB drive I have plugged in). I am not sure what to do. Strange! I removed the boot menu and its working again.
However, on a PC of a family member the Windows 10 PE image boots fine. This particular PC was identical to mine when we bought them. Over time we went for different SSD's, HD's, and monitors. Apparently that has influence on this? (The difference in partition maps?) Unfortunately both the image and the regular Windows application have a serious flaw which makes it impossible to clone the HD in this computer. I'm told to email a dump file to Macrium (which I will do, hoping that this will help solve this).
Windows on my own PC crashed this evening and left the PC in such a state that Windows was unable to correct the problem; Windows could no longer boot... Reflect's Rapid Delta Restore restored my system to a working state in less than 2 minutes. Nice!
Hello, A new update has been released, version 6.1.879: Download Page: http://www.macrium.com/Download.aspx?type=home Release Notes: http://updates.macrium.com/reflect/v6/v6.1.879/details6.1.879.htm
Question, have one full-backup, with 10 incrementals I updated to 6.1.879 and decided to change to PE 5 (windows7 64) after I read that this is a better version then 3.1. Do I have to make a new full backup due to the PE change?
Not at all. It's Macrium that needs to be compatible, not the OS it's running under. You should be just fine...
Wow.. That went to all hell. Situation: A few days ago updated to then latest version of Reflect, Enabled Incremental delta, made recovery and boot media with PE10, started a new chain... Made a full backup and then made incremental backups up until today, tried to restore the latest incremental backup.. finished in 8 seconds (Wat?) rebooted... Missing Operating System.. U wot? (Might I add that Reflect claimed it restored successfully?) Had to use rescue media and learned that the same happened with ALL incrementals, only full image restored correctly (even when not using rapid delta restore) Soo.. What now? Is there anyway I can restore to those incrementals or they F'ed forever?
I just tested on a chain I started since using the new 6.1 features. Restored an incremental in the middle of the chain and then came back to one from this morning. All worked fine. But I am still using Winpre 5.0. I am avoiding all things Windows 10. First thing I would do if I were you is remake the PE using 5.0 instead of 10 and see what happens. One thing I did note, is remembering the upside downside advantage of the new incremental index, I think I may go back to turning that off
SanyaIV, same experience as Pete. I will be leaving the new INCREMENTAL INDEXING feature in place due to the excessive amount of time consumed by my BACKUP (of the Backup) replication process due to having to re-process each INC modified using the old scheme (all their headers and content in the entire chain changed in that scheme for each INC taken).
I haven't tested with PE 5.0 and I don't really want to either since I've removed the old incrementals and remade all changes from the baseline and have now started a new chain with normal incrementals with delta indexes turned off, restored fine this time even with PE 10. Will be sending an e-mail to Macrium, don't really have any logs to share with them but maybe they can replicate.
What PE version are you using? Just wondering if it might be because I used PE 10 in combination with Delta Indexing. Also, I had reparse points to "Do not follow" which works fine with Delta Indexing turned off, may or may not be relevant to my issues, don't really feel like testing it anymore, will just leave Delta Indexing off.
I have a question: When downloading & creating a new WinPE for the boot recovery menu option where is that PE located (stored)?
Hi Sanya, When I updated Reflect to the current build (yesterday) I started using PE10 (I find it loads faster and has a more complete set of drivers than PE 3.1). But delta incrementals were working fine for me on build 871 and PE 3.1. Not sure I understand your comment about reparse points? Scott .
