Hmm, there's nothing in the Release Notes pointing to need for new PE. Do I need PE v7.1.2722. Why do I need to rebuild PE again. Not debating with you. Just want to know why I need to rebuild PE with each program update when Release Notes does not indicate need for PE rebuild. Do I need to run full installer for each patch. I'd rather go back to v6 where I ran the full installer only once and only rebuilt PE when advised by Release Notes. I'm not gonna run full installer and rebuild PE for each patch. Bug Fixes v7.1.2722 - 21th November 2017: Bug Fixes v7.1.2718 - 20th November 2017: Bug Fixes v7.1.2697 - 10th November 2017: Bug Fixes v7.1.2695 - 10th November 2017:
That's why I said "if you want to". I updated mine because I don't completely trust Macrium's current series of release notes to mention each "bug fix" specifically and, just looking at file sizes alone, there appeared to me to be a significant difference between the WAIKfiles package versions. However, it is neither my place nor my intention to tell anyone else what they should or shouldn't do. Just providing some facts that may be relevant in response to what others post here. The issues underlying those facts are not of my making and what you do about them, if anything, is entirely up to you.
Hmm, well since I'm not qualified to judge. I'd have to err on the side of caution. Sorry, "if you want to" was missed by me as I focused on "you'd need to". My bad. Does v6 carry this bad Macrium mojo too. I'll retest my PE and pull full installer. Thanks
Not a problem. My only concern is to avoid any possibility of being mistaken here as an advocate, "gatekeeper", "fanboi" or any other kind of spokesman for any particular cause ... whether noble or otherwise. I encountered no similar issues with v6 up to v6.3.1835 after which my curiosity and the v7.1 component installation options finally convinced me to make the switch. With the v7.1 WAIKFiles packages, on the other hand, extraction and binary comparisons confirmed my preliminary assessment that changes had been made to the major executable files contained in those packages and I've seen one or two reports (unconfirmed) about subsequent WinPE performance issues. Beyond that, I can't really say how significant those changes might be in practical terms. You'll just have to use your own best judgement. I certainly don't have all the answers.
So, is the WAIKFiles package supposed to update version number, size with each patch update? Admitting, I've never looked at WAIKFiles version number, size with v6.
I have recently installed the fall creators update for win 10. With it, I uninstalled avast and began using Windows Defender as my anti virus. Today when I attempted to make an image with Mac. Refl ver 6.3, I received an error stating that "an error occurred when saving XML file to C:user/jim/doc etc., Followed by "an error occurred saving the backup definition". I tried to make a folder on the desktop and then save the XML file to that but that would not work either. I suspect that this has something to do with Windows Defender. I tried to disable real time protection which didn't work. Tried to repair reflect - to which I got an error. Tried to add an exclusion for Macrium Reflect exe. to Defender - also didn't work. (Also I noticed after I uninstalled version 6.3 and installed ver 7 it was not able to create a desk top shortcut. The backup begins to run but I would but I would like to have the xml file saved. Does anyone have any ideas.
If you missed it, you can browse to a location where you want your XML file saved. I save mine in the same folder (on an external hard drive) where I save my images.
To the best of my recollection, the WAIKFiles package file version has always matched the Reflect application version and it still does when installed or updated using Reflect's full installer download. It's only some "Check for updates" patch processes that have recently omitted updates for the WAIKfiles package thus resulting in the version mismatches under discussion. That is not to say, however, that every package file update is significant. That's where it becomes a matter of judgement. You mentioned erring on the side of caution. That's what I do too when there's any doubt.
Ahh. Okay. The WAIKFiles package file version has always matched the Reflect application version. Aha!. Now, I'm on the same page (closer anyway). Thanks.
More likely to be a folder permissions issue than an AV issue IMO. Although Reflect should always run with elevated privileges, I'd take a minute to check the permissions on that folder (C:user/jim/doc or whatever it is) just the same. __ P.S.: What Win10 edition and, if Pro or Enterprise, did you activate its "Fall Creators Update" protected folders feature?
It was quite a while after v6.3.1835 that I "upgraded" to v7.1 and I "waffled" a few times after doing it.
Arvy - not sure I understand. I run as administrator, and the MR stores the name of the xml files in C:\Users\Jim\Documents\Reflect. I checked and the the folder has full permissions for the system, read, write, modify etc. Is this what you meant?
Yes, that's what I meant and that is where Reflect saves its backup task definition files by default ... not just their names but the actual XML files. So are you saying that you run Reflect as "Jim" and that "Jim" is a member of the Administrators group and can create and modify files in that C:\Users\Jim\Documents\Reflect folder manually? If so, that pretty much blows my theory out of the water.
AlphaOne - right I created a new folder and tried to save it there but I still get that error message effectively stating -error occurred saving the backup definition
I just finished running the image - it seems fine but it has no name - just a date of creation, and full, no password, etc
You mean that you log into Windows as Jim (a member of the Administrators group) to run Reflect? I'm not being "picky"; it's an important distinction. And, when thus logged in have you actually tried creating a file in that folder manually? Not being able to save your backup task definition wouldn't prevent you from running the backup task manually from within Reflect's user interface. If the backup image file can be verified successfully, that is all okay. Strange situation. No other details (e.g. an error number) in that error message when attempting to save the task definition? Anything relevant in the Reflect logs or in the Windows event logs Security section?
yes nothing relevant in the logs - under file name it has this : D:\70FD346C56141654-00-00.mrimg. no message just an error occurred saving c:jim/doc/xml (something like that) then it will not respond until I hit "ok" - then I get a message saying "an error occurred saving the backup definition file" and again the program will not respond unless I hit "ok" again - then it starts right into the image. I could possibly work around it by using the comments section when I make the first "Full" image. Then I was going to make two or three differentials, before my next full. I guess I could go with the dates they were created and the descriptor of "differential" they will have. As I understand it - the only way I can make a differential off of a full image with the free edition is to select the Full image and then "other actions" and then" "differential" When this is done, It starts right into the image, and doesn't give you the option to name the differential anyway. right, I could make it work I guess - it just kind of annoys me that it doesn't work as it's supposed to and something is blocking it. I used Avast previously, and had no problem with MR but the other variable is the Fall Creator update 1709
I was mistaken I found this message when I opened the VSS log Date 11/25/2017 7:25:08 PM Type Error Event 513 Source Microsoft-Windows-CAPI2 Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object. Details: AddLegacyDriverFiles: Unable to back up image of binary Microsoft Link-Layer Discovery Protocol. System Error: Access is denied. .
Well, that "saving c:jim/doc/xml (something like that)" message is at the heart of the issue and it really needs more precise verbatim clarification. First of all, the default folder in which it's trying to save any task definition XML file for user "Jim" should be "C:\Users\Jim\Documents\Reflect" precisely as you said above. Secondly, the task definition file should have its own full individual file pathname, not just "xml", specified in the Backup Save Options dialog box in order to be saved properly anywhere. The default task definition filename is "My Backup.xml", but it can be edited. See screenshot below. As for that Event 513 CAPI2 error, it's innocuous. See this KB article.
Yes that screenshot is exactly what I have, (I'm an old guy and I couldn't remember the exact phrasing) When I click "ok" I get this: an error occurred saving c:/Users\Jim\Documents\Reflect\My Backup.xml then it will not respond until I hit "ok" - then I get a message saying "an error occurred saving the backup definition file" and again the program will not respond unless I hit "ok" again - then it starts right into the image. Yes I managed to find that also but in may case I cannot save the xml file along with the name I subscribe to it. Also this all started when I tried to update MR when it notified me there was one when I opened the program. That update failed also (and unfortunately I don't remember the code ). So I uninstalled 6.3 and installed version 7. So I wouldn't be surprised if when the next update arrives it will fail again. I could see if I can find that code. edit - don't seem to find anything in the widows event log.
@jima It sure sounds like WD Security Center>Virus & threat protection>Virus & threat protection settings>Controlled folder access is 'On', which would most likely prevent Macrium writing the .xml to the Documents folder. This would also explain why the Macrium install can't create a shortcut to the desktop. Try setting that to 'Off'? If you do want to use Controlled folder access, you would have to make exceptions for Macrium ... Apologies if this has been discussed already, above.
that did it! Thank You! Would you know by any chance what files and folders I would have to exclude to continue using controlled folder access? If not, I will run with it off. Thanks Again.
