How to use bcdedit to change a ramdisk entry

[bit_slinger]

Hi,

I am new here and hope the good folks here can help me out. I am having a problem editing and entry using bcdedit.

I want to free up a drive that got 'hooked' doing a fresh win 7 install. I was able to change 4 others easy enough but this one has me scratching my head.

I want to change this:

Windows Boot Loader
-------------------
identifier {b6532332-7ee1-11e5-ad15-d657ceb9f79c}
device ramdisk=[C:]\Recovery\b6532332-7ee1-11e5-ad15-d657ceb9f7
9c\Winre.wim,{b6532333-7ee1-11e5-ad15-d657ceb9f79c}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice ramdisk=[I:]\Recovery\b6532332-7ee1-11e5-ad15-d657ceb9f7
9c\Winre.wim,{b6532333-7ee1-11e5-ad15-d657ceb9f79c}
systemroot \windows
nx OptIn
winpe Yes
custom:46000010 Yes

to this:

Windows Boot Loader
-------------------
identifier {b6532332-7ee1-11e5-ad15-d657ceb9f79c}
device ramdisk=[C:]\Recovery\b6532332-7ee1-11e5-ad15-d657ceb9f7
9c\Winre.wim,{b6532333-7ee1-11e5-ad15-d657ceb9f79c}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice ramdisk=[C:]\Recovery\b6532332-7ee1-11e5-ad15-d657ceb9f7
9c\Winre.wim,{b6532333-7ee1-11e5-ad15-d657ceb9f79c}
systemroot \windows
nx OptIn
winpe Yes
custom:46000010 Yes

 

[bit_slinger]

I should mention that what I tried was:

bcdedit /set {b6532333-7ee1-11e5-ad15-d657ceb9f79c} osdevice ramdisk=[C:]\Recovery\b6532332-7ee1-11e5-ad15-d657ceb9f79c\Winre.wim,{b6532333-7ee1-11e5-ad15-d657ceb9f79c}

which resulted in..

The element data type specified is not recognized, or does not apply to the
specified entry.
Run "bcdedit /?" for command line assistance.
Element not found.

 

[boyans]

You can use Visual BCD Editor and change drive or any other part of device and os device elements for recovery loader. The tool allows complete editing of BCD on every object or element.

For editing you select loader and double-click on element to edit.

You could backup BCD first (always have a BCD backup so you can restore if you are not happy with changes/editing).

{b6532333-7ee1-11e5-ad15-d657ceb9f79c} is the GUID of the corresponding device options object which should also point to drive c:!

Interesting for me would be - how this loader got messed up with different device and os device (usually they are the same as they should point inside of the same wim!)

 

[bit_slinger]

Norton thinks that dbr is unsafe.

 

[boyans]

Thanks for info about Norton.
I am not sure Norton can think

Are you checking with a local Norton antivirus or you checked on Norton web?

It is interesting that some "security checkers" give false positives which reflect website and author credibility!

My site was never flagged as insecure by Google.
Lately I have implemented https access.
That is all I could say.

 

[boyans]

https://safeweb.norton.com/report/s...IS&version=22.5.2.15&lang=0901&source=toolbar

Nothing.

Scanned dbr-1.3 with Norton Internet Security (just installed latest version) - NOTHING!

My dear "bit-slinger" would you post more data about "Norton thinks that dbr is unsafe" - it would be interesting to know.

 

[TrainableMan]

Some virus software may warn you about PUPs (Potentially Unwanted Program); that does not mean it is dangerous, it merely means it COULD be dangerous because it is relatively unknown or new software that has not gotten a rating yet. It is always a good idea to be wary of software you download. If you are uncomfortable with a piece of software or a website then try something different.

 

[boyans]

Norton thinks that dbr is unsafe.

The statement is about "Norton", not "any" or "some" ANTI virus software.

Thinking is impossible for today's personal computer hardware+software.

The statement could be "Norton Antivirus found 'whatever' in that software".

I am interested in what findings Norton reports exactly for "that software" on OP's machine.

My statement is: latest Norton Internet Security (version 22.5.2.15) reports "0" findings for dbr version 1.3 on my machine.

Please refrain from posting what "Norton" thinks, feels or smells

 

[bit_slinger]

This is what I see after unzipping dbr-1.3.0.0.zip

 

[boyans]

Norton File Insight is a special beast that eats software created by individuals and small companies which cannot afford to pay for a Symantec Code Signing Certificate (about $700 a year for .NET applications).

You cannot expect a developer to pay $700 to sign his free software.

More - a developer seems to be obliged to check every antivirus product (at least 50 of them) if they do not report something BAD about his software (in this case one particular version of a product, other versions not impacted). Happy coding and checking!

See this thread on Norton.com about Dual-boot Repair v1.3 whitelisting process if interested:

https://community.norton.com/en/forums/application-marked-wsreputation1-bad-how-remove

It seems things are getting better, slowly.

Thanks go to bit_slinger for reporting that such a beast as "Norton File Insight" exists.

 

[TrainableMan]

Looks like you are really having to jump through a lot of hoops there with Norton, boyans. good luck with all that.

Personally I'm not a fan of Norton because it gives too many false positives and even if I personally add an exception for programs I am confident are clean, Norton eventually finds a way to delete them anyway; I haven't used Norton for years because of this. On the other hand it comes free from my brother's ISP so he has it on all his computers and for the basic web surfers like his family, it works perfectly well. Most computer users are probably better off with overly cautious, but if you are a person that is actually inside your computer, manually changing boot records, then you are not the "normal" PC user and may have to live a little more on the dangerous edge of software.

So, let's try to get this thread back on topic...
Bit Slinger, if you did not find another solution then it might be worth it to you to back up your machine (always a good idea in case anything goes wrong), create a restore point, disable your Norton, and give Boyans software a try.

I can't say for certain, as with any software there is some risk but, I will say Boyans strikes me as sincere and proud of his software.

 

[boyans]

After latest update of Norton today:

Thank you TrainableMan for trusting me.
There is always a risk with any software as programming errors can lead to undesirable results. Software is still made by humans.