Windows 10: windows 10 marks directories as "read only" and i am unable to change

please see left to right. but top left to left bottom, then right top, to right bottom. maybe the xml file is too big, so it couldn't save the img file. but xml seems small. it almost seems like it tried to save the empty space or make another image after the full..

 

sorry, i thought i didn't post it already.. and tried to edit before posting. please see previous post.

 

How much room do you have on your external drive? Because you have less than 150GB total to backup, and it will be compressed by about 30-40%, so if you have 200GB free on the external, it should fit. Wonder if this is because of the read-only situation? Your thoughts @Kbird?

 

240 gb. is it because it also has a task to create image of partition to restore windows as task after create image of selected disk?

 

One complete image of the entire Disk 0 is all you have room for.

 

It stopped as there was no room on the Passport .....at least that is what it thinks , the Log file for the Backup may tell you more.

It appears you had 141GB to backup and there is 243GB Free on the Passport so I am not sure from the Pic why it did not complete, unless you changed some of Macrium's default settings , like Compression or you choose to do a Sector by Sector Backup (exact copy) vs an intelligent Sector Copy ? (intelligent only images the used space so takes less room)

KB.

 

compression is on medium..

log says:
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
- Excluding writer 'BITS Writer' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
- Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
- Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
- Add component \PerformanceCounters
* Writer 'Registry Writer':
- Add component \Registry
* Writer 'COM+ REGDB Writer':
- Add component \COM+ REGDB
* Writer 'WMI Writer':
- Add component \WMI
Creating shadow set {66f0b4e0-397b-4a78-bb20-a9be5c0d3e92} ...
- Adding volume \\?\Volume{f10821e2-5c01-4085-bec5-58d2759eaf2f}\ [C:\] to the shadow set...
- Adding volume \\?\Volume{c29f4f05-7a77-4f54-9398-add731caa9fa}\ [D:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set succesfully created.
Saving the backup components document ...


List of created shadow copies:




Querying all shadow copies with the SnapshotSetID {66f0b4e0-397b-4a78-bb20-a9be5c0d3e92} ...


* SNAPSHOT ID = {0b3d41e8-844b-4fc8-ad8e-f69304789ea3} ...
- Shadow copy Set: {66f0b4e0-397b-4a78-bb20-a9be5c0d3e92}
- Original count of shadow copies = 2
- Original Volume name: \\?\Volume{f10821e2-5c01-4085-bec5-58d2759eaf2f}\ [C:\]
- Creation Time: 9/30/2016 10:05:20 PM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
- Originating machine: LAPTOP-
- Service machine: LAPTOP-
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential


* SNAPSHOT ID = {3050c61e-dfdd-4b65-b83b-aec57d562a77} ...
- Shadow copy Set: {66f0b4e0-397b-4a78-bb20-a9be5c0d3e92}
- Original count of shadow copies = 2
- Original Volume name: \\?\Volume{c29f4f05-7a77-4f54-9398-add731caa9fa}\ [D:\]
- Creation Time: 9/30/2016 10:05:20 PM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy6
- Originating machine: LAPTOP-
- Service machine: LAPTOP-
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential

does that mean that it tried to make a full backup, then differential right after?

 

No it looks like you accidently included D: in the backup ( the 2nd Snapshot mentions D:\) and either it can't backup to a Drive it is imaging or there was simply not enough space as the Pic you posted seemed to mention.

When you image it this time make sure the checkbox in front of D:\ ie MBR Disk 2 is unchecked and try again.



edit:
Actually looking at Page #5 Pic .........d: is the HP recovery partition so should be okay , G:\ is your WD Passport.

The 1st page of the Log at the bottom may tell more on why it stop? the VSS log above doesn't show the Error or why it stopped as it is only the Volume Shadow Service Report (VSS Log)

mine from Thursday night

 

it said it was out of memory, so I stopped it. but I don't know why it was out of memory. since it technically should have only been imaging the hard drive which was less than 150 GB. I had set it to save the XML file. I don't think that was supposed to take up very much memory.

I personally think that the only explanation is that it tried to make a differential copy or it tried to do the boot media as well, but I don't think I set it to do the boot media. how can I check to see what might have caused it to do that? also, yours doesn't say shadow copy, but mine does. could that make a difference?


in WIndows' log, it says this:

Date 9/30/2016 10:05:12 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.

.

 

Memory and HDD capacity (GB's) are two different things , if the laptop only have 4GB of RAM and Virtual memory is not set to System managed or the HDD is nearly full it may so a low memory error. The Virus you got may have of course gotten deeper than we thought too? so a Clean install is likely still the Best way to fix all this.

XML file is very small

if it tried to make a differential after a full the diff. file would be tiny as there would be no changes for a diff. to record, though i don't think it is trying to do this.

Make the bootdisk is a different operation than a backup image , Macrium can't do both at the same time.

If your Passport Drive is Read only perhaps Macrium can not write the Image file to it ? can you save new files to the Passport? make a new text file and save it to G:\ you Passport to test it.


KB.

 

No problem saving text file.. but the external drive had like 10 gb or something free when i stopped it. so i don't know what it was doing. it was like it kept trying to write after 142 gb. That doesn't make sense to me. The picture i posted earlier shows (from my understanding), that a shadow copy of the C drive was completed. Following that, it tried to make an image, then it failed, because of the memory. but the memory it was referring to was the hard drive space. it showed 10 gb of the drive left. it was asking for a new one.. but as was mentioned earlier, if i have over 200, and 142 is all that is necessary, that doesn't make any sense.

 

I am not sure either , it should not even be 142GB as with compression it should save 15-25% on that too.

Have a look in the Macrium Other Tasks>View Windows VSS Events and see if there are errors ?

You may need to "fix" the VSS Errors 1st ( other tasks) or perhaps run Macrium without VSS ( in Options/Defaults)

Even after the image is made Macrium will (should) Verify the image , so it may appear to Run longer than just making the Image.

You may need to now delete other macrium attempts to backup to the Passport manually to make room for another attempt , which shouldn't be an issue since it looks like there should be roughly 240gb on the Passport free.

KB

 

it says

Date 9/30/2016 10:05:12 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.
.

note: after I stopped it, it deleted the attempt automatically. by the way, the driver directory in windows 10 only has system permissions (trusted installer) by default. not even administrator permissions.

 

The (Shadow) System Writer Object mentioned is the VSS Service AFAIK which is why i suggested a backup without VSS enabled to see if you can get around that Error.

#513 error is here and it is the VSS (Shadow Copy System Writer)
Event ID 513 — Shadow Copy System Writer Functionality

*** edit just Try the Verify Part at the bottom of the Tech Writeup , the rest may not be Win10?
ie

• In the command prompt window, type vssadmin list writers.
• Ensure that Writer Name: 'System Writer' is displayed in the list.

Ok I wasn't sure if it crashed you were able to just stop it nicely and it had cleaned up after itself. .....

 

so basically, here is a problem.. I don't know right now, but originally when I set my main account as administrator, I was not part of administrators group for some reason.. I am probably not in administrators group now, or I might be, but it is likely that due to what you are saying, that it kept trying to make shadow copies, but failed. I thought the picture I had attached said it was successful, but I know that it kept writing, and it also said that error occurred the same time that the shadow copies are notated.
it was a hectic thing to try to change permissions last time, and then after that, all of my system got read only, and supposedly a virus.. so.. do I need to try and go without VSS, or try to follow the thing above from probably another version of windows?