Failed getting protected volume configuration with error 1

Software | 2 comments | 18 March, 2015 | 0

I have been working with Windows Embedded Standard 7 (WES7) for quite a while for various projects. In most configurations, the WES7 resides on a SD card with Enhanced Write Filter turned on for System partition. In order to clone the SD cards with the system image, I do sector by sector copy and everything works on the cloned SD card.

However at one point, I had to do setup WES7 on Hard disk and image it. Now when I cloned the hard disk image to other hard disks, the Enhanced Write Filter wouldn’t work on the cloned Hard disks. When I issued the following ewfmgr command

– ewfmgr c:

I would get the following result:
– Failed getting protected volume configuration with error 1.

I tried various cloning software utilities without any success. After hours of troubleshooting, the solution that worked for me was to go to the following registry key:
– HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservices
EwfParametersProtectedVolume0

and change the value of DiskSignature to the disk signature of the disk running WES7.

Missing [HKEY_LOCAL_MACHINESYSTEMCurrentControlSet servicesEwfParameters] key

In another case, after deploying fresh WIM image of WES7, I didn’t get the [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesEwfParameters] key to begin with. In this case I exported the key from another WES 7 installation and imported it in the new installation. Following are the contents of the exported .reg file.

[text wraplines=”true”]
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSet
servicesEwfParameters]

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSet
servicesEwfParametersProtected]

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSet
servicesEwfParametersProtectedVolume0]
“DiskSignature”=dword:326b0b32
“PartitionOffset”=hex(b):00,00,10,00,00,00,00,00
“CompareBeforeAlloc”=dword:00000000
“Type”=dword:00000002
“Enabled”=dword:00000000
[/text]

After importing the key, I fixed the disk signature, restarted the WES7 system and found EWF to be working.

Источник

Содержание

Failed getting protected volume configuration with error 1
Asked by:
Question
All replies
Failed getting protected volume configuration with error 1
Missing [HKEY_LOCAL_MACHINESYSTEMCurrentControlSet servicesEwfParameters] key
Failed getting protected volume configuration with error 1
Asked by:
Question
All replies
Failed getting protected volume configuration with error 1
Asked by:
Question
All replies

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I created a Windows 7-64 image for an Ivy-Bridge VME card. The image contains EWF with RAM-REG.

The disk was divided into 2 partitions with the windows installer and the image was successfully installed.

As I’m using RAM-REG, all the disk was allocated.

After the image was installed I tried to run «ewfmgr c:» and got the current status.

Then I created a GHOST image and wrote the image on a new card with a clean disk.

After Windows booted, running «ewfmgr c:» gave:

Failed getting protected volume configuration with error 1

I found few threads on this issue but failed to understand what is the right solution.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Proposed as answer by Sean Liming MVP Tuesday, October 1, 2013 3:59 AM

I found some information that may help.

EMF is not configured correctly.

1. Distribute Disk Image
2. Run the following script after distribution of image
bcdedit /store c:bootBCD /set device boot
bcdedit /store c:bootBCD /set device PARTITION=C:
bcdedit /store c:bootBCD /set osdevice PARTITION=C:
3. Run the following script ewfcfg /install-configuration

4. Reboot the Client

5. Run the following script
ewfmgr c: -enable
6. Reboot the Client

This is modified from a Symantec document for their DS program.

Article URL http://www.symantec.com/docs/TECH163996

I created a ghost image after sysprep (/generalize /audit). When I burned this image, windows (and EWF) worked fine.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Oh, please don’t use Ghost, really, you have the perfectly good imagex already. (I don’t trust ghost at all, there are all these different versions and things too.)

This will fail for another reason. your new disk has a different serial number when it is formatted by diskpart.

1 — get the new serial

2 — open regedit, goto HKLMSYSTEMCurrentControlSetservicesEwfParametersProtected

In there, there should be a «Volume0» and in that you need to look at the value for

Set it to the same as the number you got from diskpart.

3 — save and reboot. The error will go away. (Unless of course, you managed to turn on EWF first ^^;)

The version of Ghost I have run works fine. The problem with imagex or dism is that they capture partitions rather than whole disks. I think they solved the problem by syspreping the image.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

The Problem is always Volumeid related (diskid)

Sysprep creates new bcd for the System. — Therefore it’s recommended to use sysprep (and SID and so on..) but if you’re lazy or don’t have Domain Controller and so on or always use physical seperated (better not Internet connected) machines you would be totaly fine with non-syspreped Images. You only Need updated/new bcd.

Captured wim has ‘old’ bcd (if there is no seperated MSR Partition) you can update this 3 entries within winpe and your Image will boot:

bcdedit /store c:bootBCD /set device boot
bcdedit /store c:bootBCD /set device PARTITION=C:
bcdedit /store c:bootBCD /set osdevice PARTITION=C:

(boot could also be Partition=c: or all entries could be boot — and /store is not needed as in winpe bcdedit automatically Redirects the commands into the other/System (found) bcd. But i always recommand to specify the bcd store you want to edit, like in this lines)

The definition of «C:» in this Parameter is ‘translated’ into volumeid/diskid. — So in the bcd is not «C:» it’s some DiskID.

Instead of the 3 entries you can just create a whole new bcd with updated volumeid/diskids. —> It would be enough to run bcdboot /s C: (or whatever the current boot (c:) Partition is.

EWF needs to be reconfigured as it also works with Volume/Diskids. So it needs additional command while running (online).

Источник

Failed getting protected volume configuration with error 1

I would get the following result:
– Failed getting protected volume configuration with error 1.

and change the value of DiskSignature to the disk signature of the disk running WES7.

Missing [HKEY_LOCAL_MACHINESYSTEMCurrentControlSet servicesEwfParameters] key

[text wraplines=”true”]
Windows Registry Editor Version 5.00

After importing the key, I fixed the disk signature, restarted the WES7 system and found EWF to be working.

Источник

Failed getting protected volume configuration with error 1

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I created a Windows 7-64 image for an Ivy-Bridge VME card. The image contains EWF with RAM-REG.

The disk was divided into 2 partitions with the windows installer and the image was successfully installed.

As I’m using RAM-REG, all the disk was allocated.

After the image was installed I tried to run «ewfmgr c:» and got the current status.

Then I created a GHOST image and wrote the image on a new card with a clean disk.

After Windows booted, running «ewfmgr c:» gave:

Failed getting protected volume configuration with error 1

I found few threads on this issue but failed to understand what is the right solution.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Proposed as answer by Sean Liming MVP Tuesday, October 1, 2013 3:59 AM

I found some information that may help.

EMF is not configured correctly.

4. Reboot the Client

5. Run the following script
ewfmgr c: -enable
6. Reboot the Client

This is modified from a Symantec document for their DS program.

Article URL http://www.symantec.com/docs/TECH163996

I created a ghost image after sysprep (/generalize /audit). When I burned this image, windows (and EWF) worked fine.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Oh, please don’t use Ghost, really, you have the perfectly good imagex already. (I don’t trust ghost at all, there are all these different versions and things too.)

This will fail for another reason. your new disk has a different serial number when it is formatted by diskpart.

1 — get the new serial

2 — open regedit, goto HKLMSYSTEMCurrentControlSetservicesEwfParametersProtected

In there, there should be a «Volume0» and in that you need to look at the value for

Set it to the same as the number you got from diskpart.

3 — save and reboot. The error will go away. (Unless of course, you managed to turn on EWF first ^^;)

The version of Ghost I have run works fine. The problem with imagex or dism is that they capture partitions rather than whole disks. I think they solved the problem by syspreping the image.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

The Problem is always Volumeid related (diskid)

Captured wim has ‘old’ bcd (if there is no seperated MSR Partition) you can update this 3 entries within winpe and your Image will boot:

bcdedit /store c:bootBCD /set device boot
bcdedit /store c:bootBCD /set device PARTITION=C:
bcdedit /store c:bootBCD /set osdevice PARTITION=C:

The definition of «C:» in this Parameter is ‘translated’ into volumeid/diskid. — So in the bcd is not «C:» it’s some DiskID.

Instead of the 3 entries you can just create a whole new bcd with updated volumeid/diskids. —> It would be enough to run bcdboot /s C: (or whatever the current boot (c:) Partition is.

EWF needs to be reconfigured as it also works with Volume/Diskids. So it needs additional command while running (online).

Источник

Failed getting protected volume configuration with error 1

This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.

Asked by:

Question

I created a Windows 7-64 image for an Ivy-Bridge VME card. The image contains EWF with RAM-REG.

The disk was divided into 2 partitions with the windows installer and the image was successfully installed.

As I’m using RAM-REG, all the disk was allocated.

After the image was installed I tried to run «ewfmgr c:» and got the current status.

Then I created a GHOST image and wrote the image on a new card with a clean disk.

After Windows booted, running «ewfmgr c:» gave:

Failed getting protected volume configuration with error 1

I found few threads on this issue but failed to understand what is the right solution.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Proposed as answer by Sean Liming MVP Tuesday, October 1, 2013 3:59 AM

I found some information that may help.

EMF is not configured correctly.

4. Reboot the Client

5. Run the following script
ewfmgr c: -enable
6. Reboot the Client

This is modified from a Symantec document for their DS program.

Article URL http://www.symantec.com/docs/TECH163996

I created a ghost image after sysprep (/generalize /audit). When I burned this image, windows (and EWF) worked fine.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

Oh, please don’t use Ghost, really, you have the perfectly good imagex already. (I don’t trust ghost at all, there are all these different versions and things too.)

This will fail for another reason. your new disk has a different serial number when it is formatted by diskpart.

1 — get the new serial

2 — open regedit, goto HKLMSYSTEMCurrentControlSetservicesEwfParametersProtected

In there, there should be a «Volume0» and in that you need to look at the value for

Set it to the same as the number you got from diskpart.

3 — save and reboot. The error will go away. (Unless of course, you managed to turn on EWF first ^^;)

The version of Ghost I have run works fine. The problem with imagex or dism is that they capture partitions rather than whole disks. I think they solved the problem by syspreping the image.

www.annabooks.com / www.seanliming.com / Book Author — Pro Guide to WE8S, Pro Guide to WES 7, Pro Guide to POS for .NET

The Problem is always Volumeid related (diskid)

Captured wim has ‘old’ bcd (if there is no seperated MSR Partition) you can update this 3 entries within winpe and your Image will boot:

bcdedit /store c:bootBCD /set device boot
bcdedit /store c:bootBCD /set device PARTITION=C:
bcdedit /store c:bootBCD /set osdevice PARTITION=C:

The definition of «C:» in this Parameter is ‘translated’ into volumeid/diskid. — So in the bcd is not «C:» it’s some DiskID.

Instead of the 3 entries you can just create a whole new bcd with updated volumeid/diskids. —> It would be enough to run bcdboot /s C: (or whatever the current boot (c:) Partition is.

EWF needs to be reconfigured as it also works with Volume/Diskids. So it needs additional command while running (online).

Источник

Failed getting protected volume configuration with error 1

calendar_today

Updated On:

Products

Deployment Solution

Issue/Introduction

After deploying an image of a Windows 7 Embedded client (WES7) you get the error message below:

failed getting protected volume configuration with error 1

Cause

EWF is not configured correctly.

Resolution

In order to resolve the issue please follow the steps below:

1. Distribute Disk Image
2. Run the following script in automation after distribution of image (Run script…)
bcdedit /store c:bootBCD /set {BOOTMGR.EN_US} device boot
bcdedit /store c:bootBCD /set {DEFAULT.EN_US} device PARTITION=C:
bcdedit /store c:bootBCD /set {DEFAULT.EN_US} osdevice PARTITION=C:
3. Run the following script in production (Run script…)
ewfcfg /install-configuration
Please ensure that error code 3010 (indicates that a reboot is required) is handled as success:

4. Reboot the Client (Power Control… -> Restart)
5. Run the following script in production (Run script…)
ewfmgr c: -enable
6. Reboot the Client (Power Control… -> Restart)

Applies To

DS 6.9 SP5
HP T5740e

Attachments

Feedback

thumb_up
Yes

thumb_down
No

Источник

I realize this question is old, but it came up in my search so I thought I would leave my answer.

When I encountered this error it was because I had restored an image using imeagex. I didn’t run sysprep before taking the backup image. I wiped and recreated the partition which updated the partition signature which confused EWF enough to make it not work.

EWF doesn’t have a nice tool to configure the protected volumes. So I wrote one. Here’s the source.

#define _WIN32_WINNT 0x0400

#include <windows.h>
#include <winioctl.h>
#include <tchar.h>

const TCHAR VOL_PATH[] = TEXT("SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume%i");

VOID Usage(){

    _tprintf(TEXT("Usage: ewfvoladd <Drive Letter> <Volume Number>n"));

}

INT _tmain(INT iArgCount, LPCTSTR pszArgVals[]){

    INT iReturn = 0;

    if (iArgCount == 3){

        TCHAR szDrive[MAX_PATH];

        _sntprintf_s(szDrive,MAX_PATH,TEXT("\\.\%s:"),pszArgVals[1]);
        szDrive[MAX_PATH-1] = 0;

        HANDLE hPartition = CreateFile(szDrive,GENERIC_READ,FILE_SHARE_READ | FILE_SHARE_WRITE,nullptr,OPEN_EXISTING,0,nullptr);

        if (hPartition != INVALID_HANDLE_VALUE){

            PARTITION_INFORMATION piPartInfo = {};

            DWORD dwSize = sizeof(piPartInfo);

            if (DeviceIoControl(hPartition,IOCTL_DISK_GET_PARTITION_INFO,nullptr,0,&piPartInfo,dwSize,&dwSize,nullptr)){

                dwSize = sizeof(DRIVE_LAYOUT_INFORMATION) + sizeof(PARTITION_INFORMATION) * 9;

                LPBYTE pbDrive = new BYTE [ dwSize ];

                ZeroMemory(pbDrive,dwSize);

                DRIVE_LAYOUT_INFORMATION *pdliDrive = (DRIVE_LAYOUT_INFORMATION*)pbDrive;

                if (DeviceIoControl(hPartition,IOCTL_DISK_GET_DRIVE_LAYOUT,nullptr,0,pdliDrive,dwSize,&dwSize,nullptr)){

                    TCHAR szVol[MAX_PATH];

                    _sntprintf_s(szVol,MAX_PATH,VOL_PATH,(INT)_ttol(pszArgVals[2]));
                    szVol[MAX_PATH-1] = 0;

                    HKEY hVol = nullptr;

                    LONG lRegErr = RegCreateKeyEx(HKEY_LOCAL_MACHINE,szVol,0,nullptr,REG_OPTION_NON_VOLATILE,KEY_WRITE,nullptr,&hVol,nullptr);

                    if (lRegErr == ERROR_SUCCESS){

                        const DWORD dwZero = 0,
                                    dwOne = 1,
                                    dwTwo = 2;

                        lRegErr = RegSetValueEx(hVol,TEXT("Type"),0,REG_DWORD,(LPCBYTE)&dwTwo,sizeof(dwTwo));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set Type: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("Enabled"),0,REG_DWORD,(LPCBYTE)&dwZero,sizeof(dwZero));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set Enabled: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("CompareBeforeAlloc"),0,REG_DWORD,(LPCBYTE)&dwOne,sizeof(dwOne));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set CompareBeforeAlloc: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("DiskSignature"),0,REG_DWORD,(LPCBYTE)&pdliDrive->Signature,sizeof(pdliDrive->Signature));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set DiskSignature: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("PartitionOffset"),0,REG_QWORD,(LPCBYTE)&piPartInfo.StartingOffset.QuadPart,sizeof(piPartInfo.StartingOffset.QuadPart));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set PartitionOffset: %in"),iReturn);

                        }

                        RegCloseKey(hVol);

                    }else{

                        iReturn = (INT)lRegErr;

                        _tprintf(TEXT("Failed to open registry key (%s): %in"),szVol,iReturn);

                    }

                }else{

                    iReturn = (INT)GetLastError();

                    _tprintf(TEXT("Failed to get disk info: %in"),iReturn);

                }

                delete [] pbDrive;

            }else{

                iReturn = (INT)GetLastError();

                _tprintf(TEXT("Failed to get partition info: %in"),iReturn);

            }

            CloseHandle(hPartition);

        }else{

            iReturn = (INT)GetLastError();

            _tprintf(TEXT("Failed to open drive: %in"),iReturn);

        }

    }else{

        iReturn = ERROR_INVALID_PARAMETER;

        Usage();

        _tprintf(TEXT("nNot enough parametersn"));

    }

    return iReturn;

}

So, if you only have 1 partition and it’s the C: drive you would run the following and reboot.

ewfvoladd c 0

Then you should be able to enable EWF like so

ewfmgr c: -enable

Reboot again and you’re done.

Источник

EWF for Win7, 3 steps made easy (works with RTM!)

Discussion in ‘Windows’ started by eleme, Mar 24, 2009.

eleme

Joined:

Sep 5, 2008

Messages:

16

Likes Received:

0

I got tired of sifting through all the EWF posts/info, so I thought I’d make a simple thread for everyone to enjoy!

*EDIT: Forgot to mention this before, but I’m using build 7048; although it should work on any build.

Step 1
First you need to make a few registry entries:

Key name: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesewf (the ewf key is not there by default, you have to make it)

Name: ErrorControl
Type: REG_DWORD
Value: 0x00000001 (1)

Name: Group
Type: REG_SZ
Value: System Bus Extender

Name: Start
Type: REG_DWORD
Value: 0x00000000 (0)

Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)

Key Name: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesewfParametersProtectedVolume0 (the ParametersProtectedVolume0 keys are not there by default, you have to add them)

Name: Enabled
Type: REG_DWORD
Value: 0

Name: Type
Type: REG_DWORD
Value: 0x00000001 (1)

Name: ArcName
Type: REG_SZ
Value: multi(0)disk(0)rdisk(0)partition(2) ***see note below***

Key Name: HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{71A27CDD-812A-11D0-BEC7-08002BE2092F}

Name: UpperFilters (you have to make this one too)
Type: REG_MULTI_SZ
Value: EWF

***the note below***
Only set this to 2 if you did a standard Win7 install that included the 200MB partition, otherwise set it to 1.

Step 2
Now, you need this ISO here: http://www.microsoft.com/downloads/…ea-a37e-4d25-83df-aabbaa78914f&displaylang=en

Mount the ISO (I used d-tools) and open xpefp2007.exe with a archive program (I used winrar). In the «rep» directory get the files: ewf.sys & ewfmgr.exe

ewf.sys goes in windowssystem32drivers
ewfmgr.exe goes in windowssystem32

Check that you made all the correct entries.
Check them again!
Reboot! (to insure you didn’t f-up)

Step 3
Once back into windows, open a command prompt and type the following:

ewfmgr c: -enable

It’ll spit out something (can’t remember exactly) but close your prompt and… Reboot!

If all’s well and you did everything correctly, EWF should be enabled and your Win7 AAO should now be blazin’ fast!

Good luck, and have fun!

Questions/comments? Post!

Advertisements

BrandonMB

Joined:

Jul 22, 2008

Messages:

51

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Holy Mother of …..

EWF in Windows 7,.. thanks a million dude!

Two quick tips that I found though…. You have to have UAC turned off in order to run EWFMGR properly, if you try to run ewfmgr c: -enable before turning off UAC, you end up with an error like unable to access target device //./c error (5) or something like that.

Turning off UAC in Windows 7 is about the same as in Vista, but if you need a refresher, click here:
http://www.mydigitallife.info/2008/12/3 … windows-7/

One thing I noticed though is that with UAC off, you no longer can add Gadgets to the desktop… working on getting that sorted out now, will advise.

Thanks again!

Advertisements

BrandonMB

Joined:

Jul 22, 2008

Messages:

51

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Hmm, that was easy research…

Here is the info to get Gadgets and Sidebar working with UAC off, I downloaded and ran the .reg file, seemed to work fine for me. Enjoy!

http://www.mydigitallife.info/2009/01/2 … -properly/
eleme

Joined:

Sep 5, 2008

Messages:

16

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Yea good call on the UAC, but I didn’t turn my off, I just set the slider to its lowest setting. That way gadgets still work and you don’t have to worry about erros when you use ewfmgr. I’m using 7048 so the gadget issue might be for other builds.
BrandonMB

Joined:

Jul 22, 2008

Messages:

51

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Actually, the slider at the bottom is turning UAC off.

I am working on getting the winsxs directory moved to the SD card at the moment. The Vista procedures don’t seem to work because the TrustedInstaller service has a higher level of protection than in Vista. If I can figure it out, that’ll get us another 3GB of space.. will see how that goes and will report back.
Rizzo

Joined:

Aug 26, 2008

Messages:

9

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

I have to post a thx for this thread. my AAO has seen many OS changes and EWF mod in the past. But after my battrey did in the middle of a -commit shutdown and sent my xp to the graveyard, i went back the stock acer linux out of frustration. after running w7 on my desktop i thought it was time for a switch. i then put on w7 with a vlite diet, and it seemed faster the both xp and vista without the ewf. but after comming across your ewf posting i thought if might be time to give is a shot.

the result is a w7 OS that has the fell of my quad core desktop, THIS THING FLYS. whats the point of of a ewf xp setuo when w7 runs just as fast if not faster with all the bells and whistles?

i still dont know the future of my AAO in my current system lineup. once a dual core atom with nvidia’s ion chipset comes along my AAO will be off my lap for good, but until then, this is it.
forumlurker

Joined:

Jan 16, 2009

Messages:

13

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

I have followed the instructions to the dot, but when I go to cmd prompt and type ewfmgr c: -enable, I get the error message «failed getting protected volume configuration with error 1».
Does anyone know what I am doing wrong?
Torro

Joined:

Sep 25, 2008

Messages:

23

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Never tried this before. Is this the correct report?

C:UsersAspireOne>ewfmgr c: -enable
*** Enabling overlay

Protected Volume Configuration
Type RAM (REG)
State DISABLED
Boot Command ENABLE
Param1 0
Param2 0
Volume ID 4F B8 4E 5B 00 00 90 0C 00 00 00 00 00 00 00 00
Device Name «DeviceHarddiskVolume2» [C:]
Max Levels 1
Clump Size 512
Current Level N/A

Memory used for data 0 bytes
Memory used for mapping 0 bytes

Edit: After a reboot, I get this:

C:UsersAspireOne>ewfmgr
RAM (REG) Configuration
Device Name «DeviceHarddiskVolume2» [C:]
HORM Not supported
eleme

Joined:

Sep 5, 2008

Messages:

16

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

You need to type «ewfmgr c:» to show its status.
eleme

Joined:

Sep 5, 2008

Messages:

16

Likes Received:

0

Re: EWF for Win7, 3 steps made easy

Shameless bump for those having ewf issues.

Btw, I updated to the RC, then the RTM and this still works.
Toastytwo

Joined:

Aug 3, 2009

Messages:

4

Likes Received:

0

Hi everyone,
no one having this strange non commit reboot issue… «Windows did not start properly» or something?
Ok, redid my Win7 today, one partition, RTM without any changes (ok, german language pack, but thats not the problem for sure. )
Will now add exactly (and only) the reg entrys posted here and see if my prob returns.
I’m not the only one having this and some Guys in this forum shared their thoughts bout this.

In my reg-file i had some entrys more, but maybe they are only neccessary when using XP… (like replacing ntldr)
Will submit my result later…

greets, TT
Toastytwo

Joined:

Aug 3, 2009

Messages:

4

Likes Received:

0

NOOOOOOOOO,
I dit it EXACTLY how you explained it in your first Post, -enable — reboot — EWF works — reboot — Windows could not start screen with repair option highlighted. When i choose to start Windows normaly it works like a charm, but i couldn’t get rid of this error screen apearing EVERYTIME I boot without having comitted on last shutdown.
Think before EWF starts some bootlog is written or something…
Any Ideas?

greets TT
raffaele

Joined:

Oct 19, 2008

Messages:

13

Likes Received:

0

Location:

Taranto

You have to delete the file «bootstat.dat» (hidden file)
adrianaitken

Joined:

Oct 5, 2008

Messages:

148

Likes Received:

0

Does anyone know if this works for 64 bit Windows 7 (my Lenovo laptop runs it not my Acers) ?

Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You’ll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.

Источник

Я понимаю, что это старый вопрос, но он возник в моем поиске, поэтому я подумал, что оставлю свой ответ.

Когда я столкнулся с этой ошибкой, это произошло потому, что я восстановил изображение с помощью imeagex. Я не запускал sysprep перед созданием образа резервной копии. Я стер и воссоздал раздел, который обновил подпись раздела, что запутало EWF настолько, что он не работал.

У EWF нет удобного инструмента для настройки защищенных томов. Итак, я написал один. Вот источник.

#define _WIN32_WINNT 0x0400

#include <windows.h>
#include <winioctl.h>
#include <tchar.h>

const TCHAR VOL_PATH[] = TEXT("SYSTEM\CurrentControlSet\Services\ewf\Parameters\Protected\Volume%i");

VOID Usage(){

    _tprintf(TEXT("Usage: ewfvoladd <Drive Letter> <Volume Number>n"));

}

INT _tmain(INT iArgCount, LPCTSTR pszArgVals[]){

    INT iReturn = 0;

    if (iArgCount == 3){

        TCHAR szDrive[MAX_PATH];

        _sntprintf_s(szDrive,MAX_PATH,TEXT("\\.\%s:"),pszArgVals[1]);
        szDrive[MAX_PATH-1] = 0;

        HANDLE hPartition = CreateFile(szDrive,GENERIC_READ,FILE_SHARE_READ | FILE_SHARE_WRITE,nullptr,OPEN_EXISTING,0,nullptr);

        if (hPartition != INVALID_HANDLE_VALUE){

            PARTITION_INFORMATION piPartInfo = {};

            DWORD dwSize = sizeof(piPartInfo);

            if (DeviceIoControl(hPartition,IOCTL_DISK_GET_PARTITION_INFO,nullptr,0,&piPartInfo,dwSize,&dwSize,nullptr)){

                dwSize = sizeof(DRIVE_LAYOUT_INFORMATION) + sizeof(PARTITION_INFORMATION) * 9;

                LPBYTE pbDrive = new BYTE [ dwSize ];

                ZeroMemory(pbDrive,dwSize);

                DRIVE_LAYOUT_INFORMATION *pdliDrive = (DRIVE_LAYOUT_INFORMATION*)pbDrive;

                if (DeviceIoControl(hPartition,IOCTL_DISK_GET_DRIVE_LAYOUT,nullptr,0,pdliDrive,dwSize,&dwSize,nullptr)){

                    TCHAR szVol[MAX_PATH];

                    _sntprintf_s(szVol,MAX_PATH,VOL_PATH,(INT)_ttol(pszArgVals[2]));
                    szVol[MAX_PATH-1] = 0;

                    HKEY hVol = nullptr;

                    LONG lRegErr = RegCreateKeyEx(HKEY_LOCAL_MACHINE,szVol,0,nullptr,REG_OPTION_NON_VOLATILE,KEY_WRITE,nullptr,&hVol,nullptr);

                    if (lRegErr == ERROR_SUCCESS){

                        const DWORD dwZero = 0,
                                    dwOne = 1,
                                    dwTwo = 2;

                        lRegErr = RegSetValueEx(hVol,TEXT("Type"),0,REG_DWORD,(LPCBYTE)&dwTwo,sizeof(dwTwo));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set Type: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("Enabled"),0,REG_DWORD,(LPCBYTE)&dwZero,sizeof(dwZero));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set Enabled: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("CompareBeforeAlloc"),0,REG_DWORD,(LPCBYTE)&dwOne,sizeof(dwOne));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set CompareBeforeAlloc: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("DiskSignature"),0,REG_DWORD,(LPCBYTE)&pdliDrive->Signature,sizeof(pdliDrive->Signature));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set DiskSignature: %in"),iReturn);

                        }

                        lRegErr = RegSetValueEx(hVol,TEXT("PartitionOffset"),0,REG_QWORD,(LPCBYTE)&piPartInfo.StartingOffset.QuadPart,sizeof(piPartInfo.StartingOffset.QuadPart));

                        if (lRegErr != ERROR_SUCCESS){

                            iReturn = (INT)lRegErr;

                            _tprintf(TEXT("Failed to set PartitionOffset: %in"),iReturn);

                        }

                        RegCloseKey(hVol);

                    }else{

                        iReturn = (INT)lRegErr;

                        _tprintf(TEXT("Failed to open registry key (%s): %in"),szVol,iReturn);

                    }

                }else{

                    iReturn = (INT)GetLastError();

                    _tprintf(TEXT("Failed to get disk info: %in"),iReturn);

                }

                delete [] pbDrive;

            }else{

                iReturn = (INT)GetLastError();

                _tprintf(TEXT("Failed to get partition info: %in"),iReturn);

            }

            CloseHandle(hPartition);

        }else{

            iReturn = (INT)GetLastError();

            _tprintf(TEXT("Failed to open drive: %in"),iReturn);

        }

    }else{

        iReturn = ERROR_INVALID_PARAMETER;

        Usage();

        _tprintf(TEXT("nNot enough parametersn"));

    }

    return iReturn;

}

Итак, если у вас есть только 1 раздел и это диск C:, вы должны запустить следующее и перезагрузиться.

ewfvoladd c 0

Тогда вы сможете включить EWF вот так

ewfmgr c: -enable

Перезагрузитесь снова, и все готово.

Источник

Missing [HKEY_LOCAL_MACHINESYSTEMCurrentControlSet servicesEwfParameters] key

Failed getting protected volume configuration with error 1

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Asked by:

Question

Failed getting protected volume configuration with error 1

Missing [HKEY_LOCAL_MACHINESYSTEMCurrentControlSet servicesEwfParameters] key

Failed getting protected volume configuration with error 1

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Asked by:

Question

Failed getting protected volume configuration with error 1

<img decoding="async" onError="javascript: wp_broken_images = window.wp_broken_images || function(){}; wp_broken_images(this);" src="https://i1.social.s-msft.com/globalresources/Images/trans.gif" />

Asked by:

Question

Failed getting protected volume configuration with error 1

Updated On:

Products

Issue/Introduction

Cause

Resolution

Attachments

Feedback

EWF for Win7, 3 steps made easy (works with RTM!)

eleme

Advertisements

BrandonMB

Advertisements

BrandonMB

eleme

BrandonMB

Rizzo

forumlurker

Torro

eleme

eleme

Toastytwo

Toastytwo

raffaele

adrianaitken

Advertisements

Want to reply to this thread or ask your own question?