Problems removing a second Windows Folder

User discussion and information resource forum for BootIt Bare Metal.

Re: Problems removing a second Windows Folder

Postby TeraByte Support(PP) » Fri Aug 10, 2012 9:18 am

From the prompt path, it looks like you're using a standard Command Prompt. You need to open an Administrator Command Prompt (right-click on the Command Prompt item and select "Run as administrator" -- this in in Step #6). You won't have permission to make the changes when running as a regular user.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1109
Joined: Thu Aug 11, 2011 5:51 pm

Re: Problems removing a second Windows Folder

Postby thenoo » Fri Aug 10, 2012 1:29 pm

Sorry - I had UAC switched OFF.

Now in Cmd Prompt with Administrators Privileges but results still givving errors as below:-
--------------------------------------------------------------------------------------
Result Pt1 Step 8

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>reg unload HKLM\BCD00000000
The operation completed successfully.

C:\Windows\system32>robocopy f:\ c:\ bootmgr

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Fri Aug 10 21:00:21 2012

Source : f:\
Dest : c:\

Files : bootmgr

Options : /COPY:DAT /R:1000000 /W:30

------------------------------------------------------------------------------

1 f:\
Newer 383786 bootmgr
2012/08/10 21:00:21 ERROR 5 (0x00000005) Copying File f:\bootmgr
Access is denied.
Waiting 30 seconds... Retrying...
Newer 383786 bootmgr
2012/08/10 21:00:51 ERROR 5 (0x00000005) Copying File f:\bootmgr
Access is denied.
Waiting 30 seconds...
-----------------------------------------------------------------------------
Step9 Error

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>ROBOCOPY f:\Boot C:\Boot /S

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Fri Aug 10 21:19:23 2012

Source : f:\Boot\
Dest : C:\Boot\

Files : *.*

Options : *.* /S /COPY:DAT /R:1000000 /W:30

------------------------------------------------------------------------------

7 f:\Boot\
Newer 485760 memtest.exe
2012/08/10 21:19:23 ERROR 5 (0x00000005) Copying File f:\Boot\memtest.exe
Access is denied.
Waiting 30 seconds...
--------------------------------------------------------------------------
Finally result of Step10:-

RESULT OF STEP10

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>dir f:\ /ah
Volume in drive F has no label.
Volume Serial Number is 768A-8700

Directory of f:\

01/06/2012 17:34 <DIR> $AVG
12/10/2011 16:27 <DIR> $Recycle.Bin
04/06/2012 04:45 <DIR> Boot
20/11/2010 13:40 383,786 bootmgr
12/03/2011 02:57 8,192 BOOTSECT.BAK
14/07/2009 06:08 <JUNCTION> Documents and Settings [C:\Users]
01/08/2012 10:27 6,441,586,688 pagefile.sys
13/07/2012 13:26 <DIR> ProgramData
11/03/2011 19:33 <DIR> Recovery
09/08/2012 12:30 <DIR> System Volume Information
3 File(s) 6,441,978,666 bytes
7 Dir(s) 70,946,660,352 bytes free

C:\Windows\system32>
thenoo
 
Posts: 32
Joined: Fri Nov 25, 2011 7:09 am

Re: Problems removing a second Windows Folder

Postby TeraByte Support(PP) » Fri Aug 10, 2012 3:07 pm

Do you have any security programs running that might be blocking access to "bootmgr" and "\boot" on F:? I'm not seeing any access issues in my tests.

I assume the screenshot from post #1 is still correct and Windows 7 is still booting from the F: partition.

Can you delete the "bootmgr" file on C:? Can you delete the "C:\Boot" folder? In other words, do you have access to those files normally?

For example (from Administrator Command Prompt):
c:
cd \
attrib -h -s -r bootmgr
del bootmgr

rd /s c:\boot


If files are removed, then try running the robocopy commands again:
reg unload HKLM\BCD00000000
robocopy f:\ c:\ bootmgr /r:0
robocopy f:\Boot c:\Boot /s /r:0

The "/r:0" will elimate the retries and should let robocopy display the result summary (copied files, skipped files, etc.).

Otherwise, if you can't get access to the files on F:, you could mount a backup image of the F: partition and copy the files from there. Alternatively, you could boot into WinRE (or TBWinPE/RE) and do the copies from there.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1109
Joined: Thu Aug 11, 2011 5:51 pm

Re: Problems removing a second Windows Folder

Postby thenoo » Sat Aug 11, 2012 6:16 am

TeraByte Support(PP) wrote:
> Do you have any security programs running that might be blocking access to
> "bootmgr" and "\boot" on F:? I'm not seeing any access
> issues in my tests.

I have AVG Free a/v Zone Alarm Free firewal v. 10.1.101.000
>
> I assume the screenshot from post #1 is still correct and Windows 7 is
> still booting from the F: partition.

The screenshot has not changed from post #1.
To answer your question as to whether Windows 7 is booting from the F:\ partition I'm afraid I don't know enough about my sytem to reassure you on this fact.
I have BIBM installed on the hard drive and , after the usual BIOS screen appears on bootup , I get the BIBM choices appearing. I usually click here on BOOT.Since I , supposedly , removed the dual xp_win7 bootup, I have a black screen appearing at this point offering two choices :-

#1 Windows 7 and
#2 Windows7 Amended
Whether the #2 choice appeared on removal of the Dual Boot I now cannot remember.
The #1 choice is always highlighted and , if I do nothing , the pc will boot into that and always produce the WIN 7 Error Page. This error is not solved by using my WIN 7 Repair Disk.
If , however, I select the second choice here "Windows 7 Amended" the PC boots and works normally in Win 7.
This situation has been like that for many months and I can only explain my tolerance for this situation to the fact that , although I have been using both BIBM and BING before that , I only ever use them for the creation of Image Files and don't really understand anything deeper in BIBM than that.

Before I start trying to remove any files from C:\ I am reluctant to do this in case the "Windows 7 Amended" choice is booting from C:\ and would then be inoperable also !

Would you like to comment on this before I start deleting from the C:\
thenoo
 
Posts: 32
Joined: Fri Nov 25, 2011 7:09 am

Re: Problems removing a second Windows Folder

Postby TeraByte Support(PP) » Sat Aug 11, 2012 1:31 pm

For the screenshot, just verify that F: is still "System, Active" (like it shows there). This means it's still booting from that partition.

Have you tried disabling the AV software to see if you can then run the robocopy commands? You can disconnect your internet connection first (e.g. unplug the network cable) if you don't want it accessible while disabled.

As mentioned in my previous post, you could also try copying the files from a mounted backup image. Do you have a current image of the F: partition? If so, mount it using TBIMount and then use that drive letter in the robocopy commands instead of F:. You won't need to run the "reg unload" command since the file on the mounted partition won't be loaded into the registry.

It may also help if I can see the BCD file contents. Can you run the following command from an Administrator Command Prompt and then attach the "bcdout.txt" file to a post?
bcdedit /enum all > c:\bcdout.txt
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1109
Joined: Thu Aug 11, 2011 5:51 pm

Re: Problems removing a second Windows Folder

Postby thenoo » Sun Aug 12, 2012 8:18 am

TeraByte Support(PP) wrote:
> For the screenshot, just verify that F: is still "System, Active" (like it
> shows there). This means it's still booting from that partition.

Yes - just checked that again - the F:\ Partition is still showing "System, Active"
>
> Have you tried disabling the AV software to see if you can then run the robocopy
> commands? You can disconnect your internet connection first (e.g. unplug the network
> cable) if you don't want it accessible while disabled.

Have done this . The robocopy results are unchanged - i.e both are showing "Access denied"
>
> As mentioned in my previous post, you could also try copying the files from a mounted
> backup image. Do you have a current image of the F: partition?

Yes

If so, mount it using
> TBIMount and then use that drive letter in the robocopy commands instead of F:. You
> won't need to run the "reg unload" command since the file on the mounted
> partition won't be loaded into the registry.

Have done this - the new drive letter is now "X" and the results of the robocopy commands using "X" instead of "F" are still giving "Access denied"
>
> It may also help if I can see the BCD file contents. Can you run the following
> command from an Administrator Command Prompt and then attach the
> "bcdout.txt" file to a post?

Tried to run this command . This failed to produce any result .
> bcdedit /enum all > c:\bcdout.txt
thenoo
 
Posts: 32
Joined: Fri Nov 25, 2011 7:09 am

Re: Problems removing a second Windows Folder

Postby TeraByte Support » Sun Aug 12, 2012 9:00 am

send a screen shot with the command prompt open showing the output produced
by:
bcdedit /enum all




TeraByte Support
 
Posts: 2332
Joined: Thu May 05, 2011 3:37 pm

Re: Problems removing a second Windows Folder

Postby thenoo » Sun Aug 12, 2012 11:12 am

TeraByte Support wrote:
> send a screen shot with the command prompt open showing the output produced
>
> by:
> bcdedit /enum all

Ok - This time there were results - unlike before ! . Here they are :-

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=F:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
displayorder {default}
{current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {0048fdc8-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0048fdcc-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0048fdcf-cf74-11df-ae5a-f34a80ad44b1}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {0048fdd0-cf74-11df-ae5a-f34a80ad44b1}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {0048fdce-cf74-11df-ae5a-f34a80ad44b1}
nx OptIn

Windows Boot Loader
-------------------
identifier {0048fdd0-cf74-11df-ae5a-f34a80ad44b1}

Windows Boot Loader
-------------------
identifier {default}
device partition=F:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {0048fdd4-cf74-11df-ae5a-f34a80ad44b1}
recoveryenabled Yes
osdevice partition=F:
systemroot \Windows
resumeobject {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
nx OptIn

Windows Boot Loader
-------------------
identifier {0048fdd4-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[F:]\Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[F:]\Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {d0f70ad9-adad-11e1-8278-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {0048fdd7-cf74-11df-ae5a-f34a80ad44b1}
device ramdisk=[C:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44
b1\Winre.wim,{0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {0048fdce-cf74-11df-ae5a-f34a80ad44b1}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {0048fdd2-cf74-11df-ae5a-f34a80ad44b1}
device partition=F:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=F:
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {d0f70ad9-adad-11e1-8278-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=F:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {0048fdc9-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdcd-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdcc-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd1-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\0048fdd0-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd5-cf74-11df-ae5a-f34a80ad44b1}
description Ramdisk Options
ramdisksdidevice partition=F:
ramdisksdipath \Recovery\0048fdd4-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

Device options
--------------
identifier {0048fdd8-cf74-11df-ae5a-f34a80ad44b1}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\0048fdc8-cf74-11df-ae5a-f34a80ad44b1\boot.sdi

C:\Windows\system32>
thenoo
 
Posts: 32
Joined: Fri Nov 25, 2011 7:09 am

Re: Problems removing a second Windows Folder

Postby TeraByte Support(PP) » Sun Aug 12, 2012 10:47 pm

Try using Backup mode with robocopy (add the /b switch):
reg unload HKLM\BCD00000000
robocopy f:\ c:\ bootmgr /r:0 /b
robocopy f:\Boot c:\Boot /s /r:0 /b

If that doesn't work, you could try using TBIView and copying bootmgr and \Boot out of the backup image. Otherwise, you may need to take ownership of bootmgr and \Boot and make sure the permissions are set correctly before you'll be able to access them.
Paul Purviance
TeraByte Support
TeraByte Support(PP)
 
Posts: 1109
Joined: Thu Aug 11, 2011 5:51 pm

Re: Problems removing a second Windows Folder

Postby thenoo » Mon Aug 13, 2012 6:47 am

TeraByte Support(PP) wrote:
> Try using Backup mode with robocopy (add the /b switch):
OK
> reg unload HKLM\BCD00000000
robocopy f:\ c:\ bootmgr /r:0 /b

N.B. ! I ignored the negative reply to "reg unload" this time as I assumed the BCD was already unloaded.
> robocopy f:\Boot c:\Boot /s /r:0 /b. here is the reply to the bootmgr command:-
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>reg unload HKLM\BCD00000000
ERROR: The parameter is incorrect.

C:\Windows\system32>
C:\Windows\system32>robocopy f:\ c:\bootmgr /r:0 /b

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Mon Aug 13 14:14:20 2012

Source : f:\
Dest : c:\bootmgr\

Files : *.*

Options : *.* /COPY:DAT /B /R:0 /W:30

------------------------------------------------------------------------------

2012/08/13 14:14:20 ERROR 123 (0x0000007B) Accessing Destination Directory c:\bo
otmgr\
The filename, directory name, or volume label syntax is incorrect.

C:\Windows\system32>

Here is the reply to the f:\Boot command

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>f:\Boot c:\\Boot /s /r:0 /b
'f:\Boot' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>robocopy f:\Bootb c:\\Boot /s /r:0 /b

-------------------------------------------------------------------------------
ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Mon Aug 13 14:25:42 2012

Source : f:\Bootb\
Dest : c:\Boot\

Files : *.*

Options : *.* /S /COPY:DAT /B /R:0 /W:30

------------------------------------------------------------------------------

2012/08/13 14:25:42 ERROR 2 (0x00000002) Accessing Source Directory f:\Bootb\
The system cannot find the file specified.

C:\Windows\system32>
>
> If that doesn't work, you could try using TBIView and copying bootmgr and
> \Boot out of the backup image. Otherwise, you may need to take ownership of
> bootmgr and \Boot and make sure the permissions are set correctly before
> you'll be able to access them.

The problem here is that , although I can use TBIView to Copy these items , when I then click on the f:\Partition there is nowhere where the command "PASTE" appears.
thenoo
 
Posts: 32
Joined: Fri Nov 25, 2011 7:09 am

PreviousNext

Return to BootIt Bare Metal