Solved bcd/bcdedit problems and others after Acronis DD11

[front360]

Is the # entry the hidden System Reserved partition?

I wanted to clean things up. The F and G partitions were on an old HDD that I wiped, that used to have my old Win 7 installation, but has bad sectors so I removed it.

The D: is my DVD Drive, why are there 5 corressponding volumes??

 

[Kaktussoft]

Is the # entry the hidden System Reserved partition?

I wanted to clean things up. The F and G partitions were on an old HDD that I wiped, that used to have my old Win 7 installation, but has bad sectors so I removed it.

The D: is my DVD Drive, why are there 5 corressponding volumes??

Delete all keys under mounteddevices.
But don't touch Dosdevices\C:. You see be 38 11 50 after that. Look above, it's listed another time! Delete all except both keys. Post screenshot afterwards

 

[front360]

E: has my program files and is on same ssd as C: You said remove E: also?

What is the "#" entry?(looks like its on the ssd also...by looking at binary data, be 38 11)

 

[Kaktussoft]

Is the # entry the hidden System Reserved partition?

I wanted to clean things up. The F and G partitions were on an old HDD that I wiped, that used to have my old Win 7 installation, but has bad sectors so I removed it.

The D: is my DVD Drive, why are there 5 corressponding volumes??

Delete all keys under mounteddevices.
But don't touch Dosdevices\C:. You see be 38 11 50 after that. Look above, it's listed another time! Delete all except both keys. Post screenshot afterwards

After that reboot, assign drive letters in "disk management". And check system restore settings.

But why not concentrate on the error you have!!!??

 

[Kaktussoft]

E: has my program files and is on same ssd as C: You said remove E: also?

What is the "#" entry?

# I don't know but is useless. You want to clear so delete E as well

 

[front360]

Okay I cleaned up old unused mounteddevices, and my system restore points are still working and Not dissappearing, which is great but I dunno what fixed it.
I'll keep monitoring it I guess, correct?

 

[Kaktussoft]

Okay I cleaned up old unused mounteddevices, and my system restore points are still working and Not dissappearing, which is great but I dunno what fixed it.
I'll keep monitoring it I guess, correct?

Did you reboot after deleting mounteddevices registry stuff? Used diskmanagement to reassing drive letters?

 

[Kaktussoft]

vssadmin list writers
"waiting for completion" -> maybe normal(?)
Please monitor event every now and then

 

[Kaktussoft]

Thread closed. Google youself https://www.google.nl/#q=vss+list+writers+waiting+for+completion

 

[front360]

Yes I rebooted and all done reassigning.
After creating Restore Point, 5 writers show Waiting...
After reboot, all writers show Stable

 

[front360]

Why doesn't this look correct?(System Restore is OFF for E: but shows up when I run, vssadmin list shadowstorage

 

[Kaktussoft]

I have this 3 minutes after creaating a restore point:

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Opdrachtregelbeheerprogramma voor Volume Shadow Copy-servi
(C) Copyright 2001-2005 Microsoft Corp.
Naam schrijver: 'Task Scheduler Writer'
Schrijver-id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Id van schrijverinstantie: {1bddd48e-5052-49db-9b07-b96f96727e6b}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'VSS Metadata Store Writer'
Schrijver-id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Id van schrijverinstantie: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'Performance Counters Writer'
Schrijver-id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Id van schrijverinstantie: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'System Writer'
Schrijver-id: {e8132975-6f93-4464-a53e-1050253ae220}
Id van schrijverinstantie: {60b25a85-96d1-46d6-8c99-bb09d7a6e971}
Status: [5] Voltooien=>Means completing in english. So "waiting for completion"
Laatste fout: Geen fout
Naam schrijver: 'ASR Writer'
Schrijver-id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Id van schrijverinstantie: {57c87a3f-65d3-4a3a-b12d-1ec846bb982f}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'MSSearch Service Writer'
Schrijver-id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Id van schrijverinstantie: {68f9bd97-387c-4ae8-9649-aa67213e6311}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'Shadow Copy Optimization Writer'
Schrijver-id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Id van schrijverinstantie: {eb3908c5-c9ae-4b38-94c4-bedc5bc732ad}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'Registry Writer'
Schrijver-id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Id van schrijverinstantie: {2d34e0a2-96ae-41f4-8a43-c8aa0322945a}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'WMI Writer'
Schrijver-id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Id van schrijverinstantie: {561a1c5b-c1d7-48ed-8efb-aed8a1cd7417}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'COM+ REGDB Writer'
Schrijver-id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Id van schrijverinstantie: {45ad7c3e-064c-41dc-9ec7-6dfb1727fc1f}
Status: [5] Voltooien
Laatste fout: Geen fout
===================
After 10 minutes


C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Opdrachtregelbeheerprogramma voor Volume Shadow Copy-service
(C) Copyright 2001-2005 Microsoft Corp.
Naam schrijver: 'Task Scheduler Writer'
Schrijver-id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Id van schrijverinstantie: {1bddd48e-5052-49db-9b07-b96f96727e6b}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'VSS Metadata Store Writer'
Schrijver-id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Id van schrijverinstantie: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'Performance Counters Writer'
Schrijver-id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Id van schrijverinstantie: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'System Writer'
Schrijver-id: {e8132975-6f93-4464-a53e-1050253ae220}
Id van schrijverinstantie: {60b25a85-96d1-46d6-8c99-bb09d7a6e971}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'ASR Writer'
Schrijver-id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Id van schrijverinstantie: {49a45f9d-6dbd-468c-b2f7-2f1e66f3458e}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'WMI Writer'
Schrijver-id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Id van schrijverinstantie: {561a1c5b-c1d7-48ed-8efb-aed8a1cd7417}
Status: [5] Voltooien
Laatste fout: Geen fout
Naam schrijver: 'Registry Writer'
Schrijver-id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Id van schrijverinstantie: {f9aa69da-816a-463d-bc62-6dbf5c8a2af5}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'Shadow Copy Optimization Writer'
Schrijver-id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Id van schrijverinstantie: {ea552744-c298-4f87-8cfc-62847930b09a}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'COM+ REGDB Writer'
Schrijver-id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Id van schrijverinstantie: {e40f97fa-ec84-49f2-b0d8-aaca3dd8b985}
Status: [1] Stabiel
Laatste fout: Geen fout
Naam schrijver: 'MSSearch Service Writer'
Schrijver-id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Id van schrijverinstantie: {68f9bd97-387c-4ae8-9649-aa67213e6311}
Status: [5] Voltooien
Laatste fout: Geen fout

 

[Kaktussoft]

Why doesn't this look correct?(System Restore is OFF for E: but shows up when I run, vssadmin list shadowstorage
View attachment 221547

Shadow sets are not only for system restore!!!

What is on E??? Backups?

 

[front360]

E: has all program files and data
Yes, it's set like post below.
How should it be set?

 

[SIW2]

Perhaps because you have it set that way, like this:

 

[Kaktussoft]

Why doesn't this look correct?(System Restore is OFF for E: but shows up when I run, vssadmin list shadowstorage
View attachment 221547

Shadow sets are not only for system restore!!!

What is on E??? Backups?

vssadmin delete shadows /for=e:

strange... you did it the right way!

 

[front360]

Mine shows these as "Waiting..." after a few minutes.

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {9f71f64d-769b-44da-a33f-b849347d7881}
State: [5] Waiting for completion
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {ff567ad4-24cc-4af8-b194-bcec883416fb}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {0b357dce-fb91-419b-aa4a-0484d3b52f26}
State: [5] Waiting for completion
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {b5b1860f-f4c6-4cb6-9bae-451848bd9df8}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {2fd930b1-8d6c-4ad7-b78a-bc0827e6b919}
State: [5] Waiting for completion
Last error: No error

 

[Kaktussoft]

Same here! Quite normal!

Mine shows these as "Waiting..." after a few minutes.

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {9f71f64d-769b-44da-a33f-b849347d7881}
State: [5] Waiting for completion
Last error: No error

Writer name: 'MSSearch Service Writer'
Writer Id: {cd3f2362-8bef-46c7-9181-d62844cdc0b2}
Writer Instance Id: {ff567ad4-24cc-4af8-b194-bcec883416fb}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {0b357dce-fb91-419b-aa4a-0484d3b52f26}
State: [5] Waiting for completion
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {b5b1860f-f4c6-4cb6-9bae-451848bd9df8}
State: [5] Waiting for completion
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {2fd930b1-8d6c-4ad7-b78a-bc0827e6b919}
State: [5] Waiting for completion
Last error: No error

 

[front360]

Do I need to delete those shadows? Is it incorrect to have it show the E: storage when I run "list shadowstorage"?

 

[Kaktussoft]

Do I need to delete those shadows? Is it incorrect to have it show the E: storage when I run "list shadowstorage"?

I think it's normal... not sure

vssadmin list shadows

How many shadows on E?

Delete them as explained a few minutes before