Speaking of undocumented behavioural quirks, does anyone know or want to take a wild guess regarding this RunOnce operation that the Macrium ReflectMonitor (v7.1.2646) has decided it should drop into my Windows registry's HKCU hive completely unannounced: [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce] "Application Restart #1"="C:\\Program Files\\Macrium\\Common\\ReflectMonitor.exe /RestartByRestartManager:30A6A7F8-6767-46ac-8EB6-0C648D5B7913 /RestartByRestartManager: 319D470D-991F-4076-BC04-61D356355EDC /RestartByRestartManager: DC278043-C06D-45fa-8E4D-70C74E5D74F1 /RestartByRestartManager:484A9827-D79C-46f4-92DF-4A9412DC0FB8" It's a bit puzzling as I've done nothing at all with Reflect during the current Windows session and none of its optional features (neither CBT nor MIG nor viBoot) is installed.
Hm, no such key on my Windows 7 system. It's strange that it's located in HKCU and not HKLM. It might not be that important?
At this point, I haven't even a foggy notion about its unprecedented (or at least never before noticed) HKCU inclusion. My "barebones" Reflect v7.1 installation included both "Macrium Service" [HKLM\SYSTEM\CurrentControlSet\Services\MacriumService] and "Macrium Reflect UI Watcher" [HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] to start automatically by default. But I've not seen that HKCU RunOnce inclusion during any previous Windows session. It was removed after execution by a system restart as one would expect for any RunOnce item, but I now see a new single error in my Windows 10 v1709 event log that may or may not be related: Log Name: Microsoft-Windows-Kernel-EventTracing/Admin Source: Microsoft-Windows-Kernel-EventTracing Date: 2017-10-19 12:17:00 Event ID: 2 Task Category: Session Level: Error Keywords: Session Description: Session "" failed to start with the following error: 0xC0000022
A guess. There was supposed to be a Window pop-up to allow the user to review/enable/disable MiG settings. This never happened on my system even though I enabled MiG during the update install. This might explain the single error in event viewer. This should not happen again after subsequent reboots.
Your guess is certainly as good as mine. I don't have MIG installed, but on the other hand, Macrium's peripheral activities don't seem to pay much attention to what's installed and what isn't. Those GUIDs (319D470D-991F-4076-BC04-61D356355EDC, DC278043-C06D-45fa-8E4D-70C74E5D74F1, 484A9827-D79C-46f4-92DF-4A9412DC0FB8 ) appear nowhere else in the Windows registry nor do they identify any system files or folders. The RunOnce command itself hasn't reappeared after several system restarts, but the new Windows event log error now shows up each time. It may be just coincidental, but unless someone else has a better idea than I do, I'll have to try tracking that down. Mysterious RunOnce commands appearing in my Windows registry are not something that I am able to dismiss easily as being of no consequence. __ P.S.: Tried this MS support item but it didn't stop the error showing up on each reboot. I'm not surprised that wasn't the answer as there has been no system change or other event involving NT AUTHORITY\NETWORK SERVICE permissions that would account for it in the first place.
C:\WINDOWS\system32>reagentc /info Windows Recovery Environment (Windows RE) and system reset configuration Information: Windows RE status: Enabled Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE Boot Configuration Data (BCD) identifier: 8beed7df-b463-11e7-9195-affa61f758bd Recovery image location: \\?\GLOBALROOT\device\harddisk0\partition6\RecoveryImage Recovery image index: 1 Custom image location: Custom image index: 0 REAGENTC.EXE: Operation Successful. It refers to Disk 0 partition 5 (WindowsRE) and 6 (RecoveryImage). There is most likely an OEM Lenovo partition for Windows 8.1, the original OS of this laptop. So if that is partition 6, I suppose that can go now. To recover this I suppose I use the instructions in #5731 (though I must say I am uncomfortable with this stuff - don't want to mess up)? I guess MR will then create a new full image because the 'system geometry' has changed? I also don't know what the first 1GB partition is but I thought I remember reading here that it is normal (for Win 10?).
Paul, can you post a screenshot of Disk Management? I'll get back to you. The partition numbering in Disk Management is different from diskpart due to the MSR. Edit....A screenshot of the diskpart list par screen would be helpful too.
Paul, As you can see, diskpart shows 6 partitions and Disk Management shows 5. So HD0\partition5 is the 809 MB partition in "list par". Not the 5th partition in Disk Management. The 1000 MB partition is your original RE. The 809 MB partition is a new RE. You have enough Free Space in your Windows partition so a very reasonable option is "do nothing". It's fine. Or you could do the full monty and... delete partition1 delete the 11.92 GB partition (you don't need it. You have Macrium) slide the 809 MB RE to the end of the drive resize the Windows partition to make it 12 GB larger I doubt you will want to do this. Keep what you have. No worries. Edit... You could just delete the 11.92 GB partition. This will make your Macrium Disk Images smaller.
Maybe I will do nothing, but just out of interest how would I do the above? Via Disk Management itself or do I need a 3rd party tool?
You should be able to delete the 11.92 GB partition with Disk Management but sliding will require a third party tool. Let me know if or when you change your mind.
How? I don't see that option in DM? Also - would MR start afresh (new full backup) as described by RBF earlier in this thread?
Right click the partition, Delete volume. But it might not have Delete volume. I can't answer for MR.
OK. If you want help with the trial BIBM, just ask. I think you would be comfortable deleting the final partition and if you feel brave we can talk through the rest. You have a disk image so you can't lose anything.
Thanks Brian. I would like to, but can we leave it till a bit later? Having a few issues after FCU ...
Can anybody confirm that MR v6 and v7 correctly image and restore locally stored OneDrive files and folders in the Fall Creators Update (FCU)? OneDrive Files On-Demand (the latest version of which might or might not be included in your FCU download) looks to be well done and likely quite useful.
What kind of problem are you seeing with your MR backup images? They should include any files that actually exist in (have been downloaded to) the OneDrive folder on your hard drive. However, they won't include any "files on demand" that actually exist only in your OneDrive account in "the cloud" and not on your PC, of course.
I guess I inadvertently implied that I was. I haven't installed the Fall Creators Update yet and just wanted to know if what I was intending to do would work with MR. You've answered my question nevertheless, absent any isolated problems someone might have had. Thanks Arvy.
No problem that I've seen myself so far. There are so-called "placeholders" for those cloud-only "files on demand", but not the files themselves.
My specific use case is a person I support wanting to attach files located on an unattended office computer to e-mails he's writing in hotel rooms. I intend to set OneDrive to keep copies of all OneDrive files on that office computer for automated MR imaging, while providing an elegant solution to my use case.
Paul, I know you aren't ready for partition shifting yet as you have other issues. But if you ever want to move the 1000 MB of space at the start of the drive into the Windows partition, it can be done. After deleting the 1000 MB partition... slide the ESP to the start of the drive you can't slide the MSR but you can image it, then delete it and restore the image immediately following the ESP now there is 1000 MB of Free Space following the MSR so you can slide the Windows partition up to the MSR which puts the Free Space after the Windows partition. Sliding the Windows partition might take an hour. We've already discussed the partition changes to the right of the Windows partition.
Sure Brian. I'll let you know when ... . First I need to sort out the following on my secondary machine ... I am currently grappling with the following Macrium error : 'Backup aborted! - Unable to read from disk - Error code 21 - The device is not ready'. This happens on full and differential backups. DELL-XPS-15 task is waiting for user interaction. Description: Information: Failed to read data from the disk. Details: Failed to read from sector '430 493 132' of hard disk '1'. Try to repeat the operation. If the error persists, check the disk using Check Disk Utility and create a backup of the disk. Failed to read the snapshot. (0x10C45A) Unknown status. (0x9) The device is not ready (0xFFF0) AOMEI full backup worked though. Starting with a 'chkdsk' - not quite sure if 'hard disk 1' refers to my system drive or external USB drive. (HD Sentinel reports C: as 100% but there are backup drive E: is dodgy, with bad sectors).