Windows 10: Macrium Reflect Backup Failures (problema resolutum est)

This is getting (or, more accurately, already is) complicated, along with the rest of everything. Yesterday, for example, I received a package, which contained a new front panel for my computer; what it was supposed to contain was a new USB module for the front panel, as the tech who handled my call, after some serious testing, decided that the fault was a hardware one. When I called back, the tech who answered the call was quite amused; a lower-weight package, presumably containing the proper part, was loaded on the truck for FedEx delivery just over an hour ago.

Anyway, on the subject, here is a screen shot; notice that Chkdsk does not have any logs in the top window, quite unlike the tutorial's images:

 

I started using Macrium 06Aug2016, to replace AOMEI, which had started to give me no-longer remembered problems; that was somewhat ironic, as I had installed AOMEI on my previous computer when Macrium gave me problems. Backupper was transferred from the old to the new machine, so I continued to use it.

Thus, I have good logs for eleven days. You ask for "the end of the log file": What do you mean by that?

It has been many years since I last studied mathematics, so I don't know if posting what it is that you want would be a form of "log-arithms".

 

Ah maybe I wasn't totally clear as it's not obvious how you access a file.

I was after the vss.log from one of the failed attempts- something like the picture although in my case it gets a green tick because it succeeded

Come to think of it, if you had a log from an earlier occasion when it worked, that would be a useful comparator to see as well.

 

First is VSS_Short, failed: Second is VSS_Long, good; Second, VSS_Long,failed (Forum software was somewhat confused, just as am I, failing to upload one file, putting them in different order);

 

Interesting... because the log file contains this error (or something like it - I didn't type all of it in):
Code: com call "m_pVSSObject->AddToSnapshotSet" failed HRESULT=0x8004230f VSS_E_UNEXPECTED_PROVIDER_ERROR[/quote] And when I searched for the last error on Macrium's website, it took me here:
http://knowledgebase.macrium.com/dis...party+software

Which is basically saying that, if it's the same scenario, something is left behind by some other backup software (AOMEI being a candidate) which stops VSS working. Although I do have AOMEI on my machine at the moment and it does seem to coexist OK with Macrium.

So the question would be, what do you have at this registry key? And is it the same as in that Macrium article:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers

Editing the registry is a dangerous business so I'd definitely think about doing that backup from bootable rescue media if you haven't already?

 

And when I searched for the last error on Macrium's website, it took me here:
http://knowledgebase.macrium.com/dis...party+software

Which is basically saying that, if it's the same scenario, something is left behind by some other backup software (AOMEI being a candidate) which stops VSS working. Although I do have AOMEI on my machine at the moment and it does seem to coexist OK with Macrium.

So the question would be, what do you have at this registry key? And is it the same as in that Macrium article:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\Providers

Editing the registry is a dangerous business so I'd definitely think about doing that backup from bootable rescue media if you haven't already?[/quote] I have only that which Macrium says that I should have for that Registry key, which does not surprise me given that Macrium worked correctly for eleven days after I removed BackUpper.

I've not gotten to creating any bootable rescue media, other things getting in the way, such as opening my second FedEx package, looking at what I got today, which,, while it is some sort of USB module, also has two round sockets, two cables instead of one, is 3-1/2" wide instead of 1" wide. I shall next reply to yesterday's email from the technician who sent the wrong module.

 

Thanks for checking that - yes - and on my machine Aomei and Backupper coexist in any case.

So my last hope is back at those reparse points, which I'm pretty sure shouldn't be there, at least not the ones with Unknown Target. So I think I'd try this next (once you've sorted issues with your delivery from FedEx).

... and post back what it says.[/quote]

 

I ran Junction, which did not seem to be doing anything, other than having a blinking cursor at the end of the command line. After a while, I decided to see what would happen if I were to press the enter key. That got the program's attention: It said "No reparse points found" and closed.

So, the reparse points that are there are not there, my new USB module is not here (in two different forms,) McGraw-Hill created a psychology textbook specifically for the University of New Mexico, complete with, on the special front cover, the location of UNM, "Albuquergue," wherever that might not be.

 

That might be my fault for not enclosing in quotes. Also you may need the -accepteula

Could you run these instead please and show a screenshot of what it says?
Code: c:\sysinternals\junction.exe -accepteula "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll" c:\sysinternals\junction.exe -accepteula "C:\WINDOWS\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\INetCache\Content.IE5"[/quote] Edit: you could also try:
Code: fsutil reparsepoint query "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll"[/quote] Also, while still in a command prompt, go to the c: drive, and type this, and show us the results
Code: C: cd \Windows dir /al /s[/quote] Which should show all the reparse points within c:\windows. (It will probably take a few minutes.)

 

I haven't read thru all 53 posts, but have you tried reinstalling Macrium? Let it repair any broken files and reg entries.

 

Edit: you could also try:
Code: fsutil reparsepoint query "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll"[/quote] Also, while still in a command prompt, go to the c: drive, and type this, and show us the results
Code: C: cd \Windows dir /al /s[/quote] Which should show all the reparse points within c:\windows. (It will probably take a few minutes.)[/quote] One thing accomplished today: I finally figured out what the wrong part was that was delivered today, it is the USB module for the top of the computer, whereas I need the one for the front.

Okay, here are results. The first command quickly replied that nothing was found, so I did not bother to take a screen shot. Drat: Forum software fouled up again. I listed three files, got only one.

 

Sadly, the result:

 

Ah that was the one I really wanted to see, especially as the second one of these two *should* have found a link, because it came up in the DIR command you ran later.

Code: c:\sysinternals\junction.exe -accepteula "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll" c:\sysinternals\junction.exe -accepteula "C:\WINDOWS\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\INetCache\Content.IE5"[/quote] There is also the Sysinternals program FindLinks which simrick mentioned, that might be worth trying too. I think usage would be something like.
Code: c:\sysinternals\findlinks.exe -accepteula "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll"[/quote] Just to check, does that cmitrust.dll file still show up as Unknown Target in RKILL?

Edit: Some more commands to try and report back on:
Code: vssadmin list shadowstorage vssadmin list shadows vssadmin list writers vssadmin list providers[/quote]

 

[/quote] The first command returned "nothing found,"

Second command:

[/quote]

No.

[/quote]



Here is today's submission of quite fascinating reading, much of which makes as much sense to me as does much of my reading of such obscure material as medieval manuscripts.

 

Ah so something we've done has perhaps changed (I hesitate to say 'fixed') that then?

Could you post the latest RKILL output as text in the same way you did before (in

Code:

tags) please?

This is also interesting because it does show an actual link on the file.

You'll note that
Code: C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.0_none_145e7a4159d239dd\cmitrust.dll[/quote] is linked to
Code: C:\WINDOWS\WinSxS\x86_microsoft-windows-s..icingstack-cmitrust_31bf3856ad364e35_10.0.14393.82_none_397264147e08b82f\cmitrust.dll[/quote] (if I typed that right.)

What happens if you try the same command on the next one on the original RKILL list:
Code: findlinks.exe -accepteula "C:\WINDOWS\WinSxS\x86_microsoft-windows-s..ingstack-base-extra_31bf3856ad364e35_10.0.14393.0_none_f05abb1521a8c58e\bcdeditai.dll"[/quote]

I could never get the hang of the 's's that looked like 'f's...