It appears that the problems being experienced by some users may possibly be related to improper UAC elevation handing by the v7.1.2638 update leading, in turn, to device class filter service installation issues. If that's the case, then you'd probably be okay if your Windows login itself gives you admin group privileges, but that's not entirely clear at this point. You'll definitely be okay if the "MIG" and "CBT" options are UNchecked in the installation dialog. Without them, v7.1 isn't really much different from v6.
Okay, thanks. If your installation includes those "CBT" and "MIG" filter service options, that would tend to confirm that at least some of the issues may originate in faulty UAC elevation handling with non-admin user accounts.
My account does have admin privileges. Also, after being off all night, I was able to boot into Windows. I hope they fix this soon!
I can't say I am completely understanding the issue where b2638 is causing the computer to not boot, and forgive me if I'm using improper nomenclature here... I am running Reflect v7.1.2638 on two computers, both Win10-64 Pro. My PC uses BIOS, my laptop UEFI. I have CBT and MIG installed and enabled on both. The user I log on with on the PC is NOT an admin account, and that which I use on the laptop IS an admin account. I can choose to shut down from the Windows "start menu" on both computers, shutting them off. I can then press the power button to boot both machines and they do so just fine, on the first try.
This morning after being off with AC removed (we have a power station) all night it did come back and boot into Windows OK. Yesterday it did not.
Hello, FYI: This conversation started on another thread here: SSD and IDE/AHCI? I am finally retiring my old system Friday after almost 10 years of service. My new system arrives Friday and of course will be UEFI. I will be transferring my install of Macrium 7 to the new system. I have absolutely no experience with UEFI BIOS mode as all I have ever used or been exposed to has been legacy BIOS. Will Macrium work out of the box on UEFI? Do the default settings work well? Anything different that I need to know about the Macrium boot option or creating rescue media? Does creating images and doing restores function the same or do I need to do anything different? I not only have these questions but I am sure that I will have more as I proceed... I am hoping that my transition to UEFI will go as smooth as possible and hope the community here that have experience with using Macrium on a UEFI system can help me with that. All advice, help, and knowledge on this will be greatly appreciated.
Just remove the old system's Reflect license so that you can reactivate it when you install Reflect on the new system. Other than that, the new system's start-up method (UEFI/GPT instead of BIOS/MBR) will have no effect whatever on any aspect of Reflect's functionality when booted to the regular Windows working environment. You will, of course, need to create new backup task definitions appropriate to the new drive layout. As for Reflect's rescue media, it's usually made capable of booting either way, but your new system will almost certainly be configured to choose only the right one which is important if you ever need to use Reflect's "Fix Windows Boot Problems" utility.
Hello @Arvy, Thanks for your reply as it helps to alleviate some of the anxiety relating to moving to a UEFI system. It is good to know that Macrium takes care of everything "behind the scenes" so I do not have to worry about changing any settings or any special procedures. It will work just the same as it did on my MBR system without me having to have any new knowledge of UEFI.
Operationally, once Reflect is up and running under the Windows operating system, it really doesn't care about how that OS was loaded by your machine from its HDD or SSD, nor that the start-up process may involve some special purpose partitions on that machine's HDD or SSD. Reflect will just go about its own business of backing up those drive partitions (or cloning or restoring them) in accordance with your instructions as it would any others that it's capable of handling. The same is true when booted to and running under the WinPE rescue environment which doesn't necessarily even have to be based on the same OS version.
Depends on what "the problem" you're referring to. Mr Sills has responded in the case of the external drive "release for eject" issue, but not in the case of other reported UAC elevation issues involving "MIG" installation. Nor is there any satisfctory explanation for your previous report that you could not start after a power off shutdown.
Well, I did not have any problem starting this morning. I was not able to do this after I installed the update and I did power down and unplugged from AC via the power panel I have. Anyway, I will see how it goes tomorrow!
WARNING!! It has been confirmed by many early adopters of the Windows FALL CREATORS EDITION (due out on 17Oct2017) that, once again, the update will most likely resize your RECOVERY PARTITION (if you're using one) upwards in size. This process may change the geometry of your System disk which will cause your scheduled Reflect backup process to create yet another new FULL backup (due to a geometry change in your backup specification), starting a new backup image chain if you're a Differential or Incremental image user. If this "update" process works as it has in the past, it will create a new, larger Recovery Partition, shrink your Windows System partition to accommodate the creation of this new partition, and leave your original Recovery Partition to waste in the desert of past useless recovery partitions (a process I call Partition Bubbling... like blowing bubbles with your child's bubble blower). Please prepare for the anomaly described above... and have a very exciting update
Thanks for the heads up. May need your help to delete past useless recovery partitions afterwards (will send or post a drive map then). Not good with this sort of thing, playing with partitions.
THIS LINK in the Macrium Forums should give you a good heads up on what to expect when doing this update. Although it relates primarily to v6 of REFLECT, it fully applies to the use of v7.
In almost every case, if a new partition is created to accommodate the new larger Recovery process, it will be the one located immediately after your Windows partition (C:\)... which will be in the new space created during the downsizing of your Windows partition to accommodate this new Recovery Partition.
...and for those using BitLocker protection on their Windows partitions, THIS ADDITIONAL INFORMATION will be extremely useful when doing the Windows 10 FALL CREATORS EDITION update.
Thanks for the information on resizing the recovery partition. Last time this happened it caused quite a lot of confusion (not Macrium's fault). Having a list of your partition sizes before and after the upgrade will help to check what actually happens.
I am not sure that's right. I had the problem with CBT installed and Unchecked (MIG is Checked). The problem goes away only if I uninstall the CBT driver. A fix is imminent anyway for those who do more than one incremental in each Windows session.
If both the "MIG" and "CBT" options are UNchecked in the update's installation dialog, the update process should remove any currently installed CBT driver and it should not install the new one. Are you saying that it doesn't do that and that you must uninstall the CBT component yourself afterward? If so, it sounds like they really messed up the v7.1.2638 update process quite badly. We can only hope that the promised "fix" gets it right.
I might have mis-read your post. I meant if CBT is installed (by checking CBT in the update dialog or install) but is not used (uncheck use CBT in Edit Defaults>Advanced>Advanced Incrementals) then the problem persists. Going into control panel>Programs>Programs and Features>Macrium Reflect>Change>Uncheck CBT will uninstall the driver and the problem disappears. When the driver isn't installed the option to use CBT in Advanced Incrementals is greyed out. This is probably how I will leave it even when the fix is applied.
Yes, possibly. It was in reply to a question about whether one could avoid the problems involved in running the v7.1.2638 update process itself. I think one can if one UNchecks the options for installing those kernel mode device class filters, or at least UNchecks the "CBT" option. The "Edit Defaults > ..." option to not use CBT merely prevents its usage during second and subsequent incremental or differential backups during a single Windows session. The Changed Block Tracking service itself remains in place and carries on its "built-in" device class filter activities regardless of that setting. The only way to avoid that is to either uninstall it or else not install it in the first place. Like any kernel mode driver, there is a potential for very serious problems (including boot problems) if there is any issue at all with either installation or uninstallation.
Bug Fixes v7.1.2646 - 13th October 2017: CBT causing a lock on removable drives The CBT driver could cause a permanent lock on external drives preventing safe ejection. This has been resolved. Image Guardian settings dialog hang When clicking 'OK', without changing any MIG settings, a progress bar would be displayed and the dialog would not closed. This has been resolved. Nothing on the reported issue about "MIG service cannot be stopped" which may or may not be related to UAC elevation handling.
