Solved bcd/bcdedit problems and others after Acronis DD11

[front360]

(How many shadows on E: )Did you tell me to run this "list shadows"?

Contents of shadow copy set ID: {29f656b2-d033-4ab0-978c-e1253c926aba}
Contained 1 shadow copies at creation time: 7/14/2012 1:53:27 PM
Shadow Copy ID: {a26ecbc4-ffb9-435a-8c0f-bf996b66d3d8}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {eb01be74-536a-4e1d-9a5a-0a34de5c110f}
Contained 1 shadow copies at creation time: 7/14/2012 3:27:00 PM
Shadow Copy ID: {979f0921-be2c-4b35-9886-a1d76bd7ff1f}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy2
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {35849cdb-e93a-4851-8ec0-b50158122b06}
Contained 1 shadow copies at creation time: 7/14/2012 3:28:05 PM
Shadow Copy ID: {55e622e1-f32a-4ea6-978b-99037b5a1438}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy3
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {40a611c8-e132-4c50-bade-9e3227be9ef5}
Contained 1 shadow copies at creation time: 7/14/2012 3:29:22 PM
Shadow Copy ID: {f89ff839-d0fd-43b4-8f73-400a744528e3}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {e8aaf540-6331-40c1-940f-2b4860e7c7b8}
Contained 1 shadow copies at creation time: 7/14/2012 3:32:41 PM
Shadow Copy ID: {d88bc514-4cd5-4a17-9112-614399cdf328}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy5
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {5df54f6b-8b9f-4917-b324-d8e0868cf860}
Contained 1 shadow copies at creation time: 7/14/2012 4:05:40 PM
Shadow Copy ID: {5260c32f-2a66-46e2-b200-9d012dbcf1cc}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy7
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {ac981ac5-ace0-4aba-8a17-53a804fe5edb}
Contained 1 shadow copies at creation time: 7/14/2012 5:57:56 PM
Shadow Copy ID: {bbf7a374-379b-44de-9b38-c5312072ff36}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy8
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

Contents of shadow copy set ID: {2db8f532-5c08-4392-9706-9541ec3e8e47}
Contained 1 shadow copies at creation time: 7/14/2012 6:33:05 PM
Shadow Copy ID: {3c514b88-33aa-4548-93dc-8e6b14943479}
Original Volume: (C\\?\Volume{e48e74b2-b1e2-11e1-8a02-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy9
Originating Machine: LAPTOP
Service Machine: LAPTOP
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessibleWriters
Attributes: Persistent, Client-accessible, No auto release, Differential, Auto recovered

 

[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

You only have a C and E drive (and dvd=D and syetem reserved)?

 

[front360]

Currently, yes Correct. and F: is MicroCard

 

[Kaktussoft]

shadows are fine!! vssadmin is normal!

 

[SIW2]

Did you miss my post?

That is why max storage is showing even tho you have it turned off for E

135

 

[front360]

Is it bad if I don't run "vssadmin delete shadows /for=e:"
Does that cmd only delete shadows on e: to make room for more?

 

[front360]

Did you miss my post?

That is why max storage is showing even tho you have it turned off for E

135

Yes, thanks do I have to delete shadows on the e: ?

 

[SIW2]

No.

You can leave it as it is - doesn't matter.

That screenie is of my G drive - sys prot is off , but max storage slider is not at 0.

All it is doing is reflecting where you have the slider. Makes no difference if you aren't using that space.

 

[front360]

Kaktussoft, I went to dinner and when I returned my computer was on an 0xF4 BSOD. I tried to reboot a bunch of times, but found out my SSD was not being recognized by the BIOS. I remembered how to "power cycle" my Crucial M4 SSD and an hour later it was recognized by BIOS and I was able to boot again. What happened? Anything I need to do/know? Thanks to anyone who helps.

 

[front360]

...and no matter how many times I delete from registry, the mounted dosdevices\f: and it's corresponding volume, it reappears on reboot. I don't want this to cause issues because the f: drive is my old HDD that used to have Windows 7, but is removed from my laptop(via device manager) because it's dead. Is there a way to permanently get rid of this so windows boot manager/loader etc. doesn't "get confused" for lack of better words? Thanks.

 

[Kaktussoft]

...and no matter how many times I delete from registry, the mounted dosdevices\f: and it's corresponding volume, it reappears on reboot. I don't want this to cause issues because the f: drive is my old HDD that used to have Windows 7, but is removed from my laptop(via device manager) because it's dead. Is there a way to permanently get rid of this so windows boot manager/loader etc. doesn't "get confused" for lack of better words? Thanks.

Are you very sure you deleted those registry entries? Do it again and reboot.
They are back on reboot? Also the dosdevices/E?
Disk management shows the drive letters?
Elevated command prompt:

diskpart
list volumes
exit

Now reassign drive letters using disk management

 

[Kaktussoft]

...and no matter how many times I delete from registry, the mounted dosdevices\f: and it's corresponding volume, it reappears on reboot. I don't want this to cause issues because the f: drive is my old HDD that used to have Windows 7, but is removed from my laptop(via device manager) because it's dead. Is there a way to permanently get rid of this so windows boot manager/loader etc. doesn't "get confused" for lack of better words? Thanks.

#143 F is microcard??

 

[Kaktussoft]

Kaktussoft, I went to dinner and when I returned my computer was on an 0xF4 BSOD. I tried to reboot a bunch of times, but found out my SSD was not being recognized by the BIOS. I remembered how to "power cycle" my Crucial M4 SSD and an hour later it was recognized by BIOS and I was able to boot again. What happened? Anything I need to do/know? Thanks to anyone who helps.

BSOD 0xF4 is most likely due to SSD not accessible anymore. Do you remember event ID 9 "disk controller not responding" (or something like that) in event log?

Did you already make a full backup as told you before?
disk controller failed, ssd not connected firmly, sata cable failing, disk is dying.

"power cycle" my Crucial M4 SSD=> How did you do that?

 

[front360]

F: is my microcard, sorry it used to be H: I forgot I changed it. So that is okay now, no problem anymore.

To power cycle my M4 in my laptop:
1)Boot to Bios, leave idle there for 20 minutes.
2)Shutdown and remove power and battery for 30 seconds.
3)Repeat steps 1 and 2, once more.

Desktop instructions included here->http://forum.crucial.com/t5/Solid-S...ecognize-crucail-m4-SSD-64GB/m-p/64485#M19896

If it's my Sata cable in my laptop, I would need to tear down my laptop to get to it I believe, correct?(Asus G73JH)

 

[front360]

"BSOD 0xF4 is most likely due to SSD not accessible anymore. Do you remember event ID 9 "disk controller not responding" (or something like that) in event log?"

I have not had any Event ID 9's since I uninstalled the Intel RST 10.8 driver and installed the ms msachi driver around four days ago.

 

[front360]

Guess what.. I just looked and my restore points are Gone again. Why...

And 0x0f4 bsod again after I left pc idle for 15 minutes. When I returned, screen was blue and bottom middle of laptop was so hot to the touch.

 

[Kaktussoft]

SSD is dying! Or damaged sata cable. Or disk controller. Make a new threat for that cause original problem has been solved

 

[front360]

If you run vssadmin list, the volume listed at top of mine, even though volume path doesn't show it, I tracked down, and it's "system reserved". Is that standard on yours also??
And does vssadmin list providers, Only show- Provider name: 'Microsoft Software Shadow Copy provider 1.0'??

 

[Kaktussoft]

If you run vssadmin list, the volume listed at top of mine, even though volume path doesn't show it, I tracked down, and it's "system reserved". Is that standard on yours also??
And does vssadmin list providers, Only show- Provider name: 'Microsoft Software Shadow Copy provider 1.0'??

C:\Windows\system32>vssadmin list providers
vssadmin 1.1 - Opdrachtregelbeheerprogramma voor Volume Shadow Copy-service
(C) Copyright 2001-2005 Microsoft Corp.
Providernaam: 'Microsoft Software Shadow Copy provider 1.0'
Providertype: Systeem
Provider-id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Versie: 1.0.0.7

C:\Windows\system32>

your ssd is dying!
And I don't have "system reserved". But I think it's normal