Winre.wim in Windows 8.1
Hi,
I mounted install.wim from Windows 8.1 x64 enterprise evaluation , navigate to system32\Recovery
But couldn't find Winre.Wim
Is it normal in 8.1? What is default location?
N.A.Malik
Hi,
Based on my research, we can find winre.win in system32\Recovery folder.
I suggest you download the windows 8.1 Enterprise from the link below to check the result.
Download the Evaluation: Windows 8.1 Enterprise
http://technet.microsoft.com/zh-hans-cn/evalcenter/hh699156.aspx
Meanwhile, please refer to the following link to mount install. Win file.
Mount and Modify an Image Using DISM
http://technet.microsoft.com/en-us/library/hh824814.aspx
Regards,
Kelvin hsu
TechNet Community Support
Similar Messages
-
Hi Guys,
I'm currently working on a Windows 8.1 deployment where I'm trying to control my WinRE wim file. I'm having a problem figuring out where MDT/Windows Setup is sourcing those RE files from. I checked inside of my wim that I'm deploying and under
C:\Windows\System32\Recovery, no WIM exists. I also checked to make sure PrepareWinRE=NO, tried shutting off the extra active partition, even created a diskpart /s win8_uefi.txt based on IsUEFI=True with no recovery partition, and yet still WinRE finds
a way in. That being said, I can deal with this automatic deployment if I knew where it was placing those files from. Looking in BDD.log really just shows it making the partitions and then setup goes behind the curtains and performs its Winre magic
trick. Any assistance would be greatly appreciated, I really want to get the most out of this feature set. Thanks.
RyanHi,
Based on my research, we can find winre.win in system32\Recovery folder.
I suggest you download the windows 8.1 Enterprise from the link below to check the result.
Download the Evaluation: Windows 8.1 Enterprise
http://technet.microsoft.com/zh-hans-cn/evalcenter/hh699156.aspx
Meanwhile, please refer to the following link to mount install. Win file.
Mount and Modify an Image Using DISM
http://technet.microsoft.com/en-us/library/hh824814.aspx
Regards,
Kelvin hsu
TechNet Community Support -
Does anyone know how to install a full version of IE to a WinRE WIM? I need the browser to launch within RE. We have gone through the motions of copying the IE directory into the program files dir on the WIM, registering a few DLLs, and copying some of the reg hives. There has to be an easier way.... any ideas or tried and true steps?
You may follow the URL below to install IE to a WIM:
http://technet.microsoft.com/en-us/library/hh147968.aspx -
WIM - Chat window space --- Do we have any limit?
Hi folks,
I try to install WIM for the client, and they wonder whether there is any limit on chat window space. Does anyone know what limits chat window may have?
Thanks a lot
JooHyung LeeThere is setting "Chat - Agent Chat Message Maximum Length" at Department settings group, you can Use this setting to determine the maximum length of messages sent by agents to customers.
Setting "Chat - Automatic Session Closure Interval (Seconds)" defines maximum how long chat can stay on. By default it is 4 hrs.
Chat window is only one, agent has to switch between the assigned chats. chat reply pane is used for the chat which agent has selected in the inbox at that time. Agent can be assigned multiple chats. Setting "Chat - User Max Load" defines maximum chat activities that can be assigned to a user at a given moment. When an agent reaches the maximum number, new chats cannot be assigned to the agent.
Regards,
Ravindra Adhav
eGain Support -
How to create PBR functionality using WDS deployment
Dear sir/madam,
We are a Dutch OEM currently working on deployment and DIS. I have a question about deployment I’m hoping you can help us with.
We were tought to deploy images via USB using the following script:
dism /Apply-Image /ImageFile:%1 /Index:1 /ApplyDir:W:\
md T:\Recovery\WindowsRE
attrib -h -a -s W:\windows\system32\recovery\winre.wim
copy W:\windows\system32\recovery\winre.wim T:\Recovery\WindowsRE\winre.wim
W:\Windows\System32\bcdboot W:\Windows /s S:
W:\Windows\System32\reagentc /setreimage /path T:\Recovery\WindowsRE /target W:\Windows
Mkdir R:\RecoveryImage
Copy %2 R:\RecoveryImage\
W:\Windows\System32\reagentc /setosimage /path R:\RecoveryImage /target W:\Windows /index 1
This works perfectly for single systems. However, since we’re planning on building a lot of units we want to automate installation over network. We’re building a solution to deploy custom images on tablets, laptops and desktops based on
WDS. We currently have a working MS Server 2012 WDS server and several working custom images. The question we have is regarding the system recovery functions (PBR). I’ve managed to automate login to WDS, language choice and disk partitioning using WDSunattend
(see below). WinRE and Recovery Image partitions are created. We can manually select the image we want to deploy and it will successfully install to the Windows partition.
<?xml version="1.0" ?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
<WindowsDeploymentServices>
<Login>
<WillShowUI>OnError</WillShowUI>
<Credentials>
<Username>Administrator</Username>
<Domain>WDS.assemblage.com</Domain>
<Password>xxx</Password>
</Credentials>
</Login>
<ImageSelection>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>4</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
<DiskConfiguration>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>false</WillWipeDisk>
<CreatePartitions>
<CreatePartition>
<Order>1</Order>
<Size>540</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition>
<Order>2</Order>
<Size>260</Size>
<Type>EFI</Type>
</CreatePartition>
<CreatePartition>
<Order>3</Order>
<Size>128</Size>
<Type>MSR</Type>
</CreatePartition>
<CreatePartition>
<Order>4</Order>
<Size>20000</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition>
<Order>5</Order>
<Extend>true</Extend>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition>
<Order>1</Order>
<Format>NTFS</Format>
<Label>WinRE</Label>
<PartitionID>1</PartitionID>
<TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
</ModifyPartition>
<ModifyPartition>
<Order>2</Order>
<PartitionID>2</PartitionID>
<Label>System</Label>
<Format>FAT32</Format>
</ModifyPartition>
<ModifyPartition>
<Order>3</Order>
<PartitionID>3</PartitionID>
</ModifyPartition>
<ModifyPartition>
<Order>4</Order>
<PartitionID>4</PartitionID>
<Letter>C</Letter>
<Label>Windows</Label>
<Format>NTFS</Format>
</ModifyPartition>
<ModifyPartition>
<Order>5</Order>
<PartitionID>5</PartitionID>
<Label>Recovery</Label>
<Format>NTFS</Format>
<TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
<SetupUILanguage>
<WillShowUI>OnError</WillShowUI>
<UILanguage>en-GB</UILanguage>
</SetupUILanguage>
<UILanguage>en-GB</UILanguage>
</component>
</settings>
</unattend>
Here’s the problem: I can’t find any information on creating PBR functionality using unattend anywhere. Is this possible? If it is, can you help us find a solution?
Since I can’t find any info on creating PBR using unattend I’m assuming that we have to add PBR functionality using scripts after Windows setup is completed. How do we get this done using WDS?
With kind regards,
Frank Wessels.Hi,
We could use deploymenr scripts to configure the recovery partitions:
Samples: Applying Windows, System, and Recovery Partitions by using a Deployment Script
More information regarding Capture and Apply Windows, System, and Recovery Partitions, please check:
http://technet.microsoft.com/en-us/library/hh825041.aspx
Hope this may help
Best regards
Michael Shao
TechNet Community Support -
Can Convert-WindowsImage convert a .WIM from Command Prompt's "recimg" on Windows 8.1?
Hi Folks,
I have been trying to do this several times, including with the UI. The UI afforded a bit more info; it was complaining about the .WIM metadata:
Windows PowerShell transcript start
Start time: 20140121155929
Username : TammyLacey\Crysta T Lacey
Machine : TAMMYLACEY (Microsoft Windows NT 6.3.9600.0)
INFO : Launching UI...
INFO : Selected Working Directory is D:\Hyper-V\Virtual Hard Disks...
INFO : Scanning WIM metadata...
INFO : Scanning WIM metadata...
ERROR : You cannot call a method on a null-valued expression.
INFO : Log folder is C:\Users\CRYSTA~1\AppData\Local\Temp\Convert-WindowsImage\28986a7f-dc96-4ee6-91e2-b69b90a31153
INFO : Closing Windows image...
INFO : Done.
Windows PowerShell transcript end
End time: 20140121161513
With PowerShell:
PS C:\Windows\system32> Convert-WindowsImage -SourcePath "E:\@.RefreshImage\2014-01-18\CustomRefresh.wim" -VHDPath "D:\Hyper-V\Virtual Hard Disks\W 8.1 Pro 1.vhdx" -Edition Professional -VHDFormat VHDX -Verbose -db
Windows PowerShell transcript start
Start time: 20140121092326
Username : TammyLacey\Crysta T Lacey
Machine : TAMMYLACEY (Microsoft Windows NT 6.3.9600.0)
DEBUG:
using System;
using System.Collections.Generic;
using System.Collections.ObjectModel;
using System.ComponentModel;
using System.Globalization;
using System.IO;
using System.Linq;
using System.Runtime.InteropServices;
using System.Security;
using System.Text;
using System.Text.RegularExpressions;
using System.Threading;
using System.Xml.Linq;
using System.Xml.XPath;
using Microsoft.Win32.SafeHandles;
namespace WIM2VHD {
/// <summary>
/// P/Invoke methods and associated enums, flags, and structs.
/// </summary>
public class
NativeMethods {
#region Delegates and Callbacks
#region WIMGAPI
///<summary>
///User-defined function used with the RegisterMessageCallback or UnregisterMessageCallback function.
///</summary>
///<param name="MessageId">Specifies the message being sent.</param>
///<param name="wParam">Specifies additional message information. The contents of this parameter depend on the
value of the
///MessageId parameter.</param>
///<param name="lParam">Specifies additional message information. The contents of this parameter depend on the
value of the
///MessageId parameter.</param>
///<param name="UserData">Specifies the user-defined value passed to RegisterCallback.</param>
///<returns>
///To indicate success and to enable other subscribers to process the message return WIM_MSG_SUCCESS.
///To prevent other subscribers from receiving the message, return WIM_MSG_DONE.
///To cancel an image apply or capture, return WIM_MSG_ABORT_IMAGE when handling the WIM_MSG_PROCESS message.
///</returns>
public delegate uint
WimMessageCallback(
uint MessageId,
IntPtr wParam,
IntPtr lParam,
IntPtr UserData
public static void
RegisterMessageCallback(
WimFileHandle hWim,
WimMessageCallback callback) {
>>>>>>>>>>>>>>>>>> I have the rest of the DEBUG your interested but it is over 4000 lines<<<<<<<<<<<<<<<
#endregion Public Properties
#endregion VHD Interop
Confirm
Continue with this operation?
[Y] Yes [A] Yes to All [H] Halt Command [S] Suspend [?] Help (default is "Y"):
VERBOSE: isUserAdmin? True
VERBOSE: isWindows8? True
VERBOSE: Temporary VHDX path is : D:\Hyper-V\Virtual Hard Disks\e53a41bc-6a5e-4d85-9b77-33d0e48b40b8.vhdx
ERROR : You cannot call a method on a null-valued expression.
INFO : Log folder is C:\Users\CRYSTA~1\AppData\Local\Temp\Convert-WindowsImage\e53a41bc-6a5e-4d85-9b77-33d0e48b40b8
INFO : Closing Windows image...
INFO : Done.
Windows PowerShell transcript end
End time: 20140121093332
Thank You,
Best Regards,
Crysta
PhotM Phantom of the MobileI think there are a couple of Red Hariings are forming here. First, I am of the old IBM school where filetypes (extentions) were limited to 8 characters not 3 as in DOS in the 70's & 80's, therefore Executives were Exec but the same as .exe and were
text files. Second, this is not about recimg ability to run, it runs just fine but slow. Recimg is simply where the .WIM comes from.
This is about Convert-WindowsImage.ps1 a PowerShell Script processing that .WIM and converting it to a .vhdx.
Crysta
PhotM Phantom of the Mobile
Herrings dear - 'herrings'. Or are you thinking of "harangue-ings"... maybe "hangings'.
I am an extremely old IBM guy. Windows extensions can have as many characters as you need. There is no 3 character limit as any trained technician in IBM or Windows has known for many years.
If you have a real question post it to the location where you got the script. The script is from the Gallery.
We do not fix or write scripts on demand. You are free to write a script and post questions here. If you have issues with gallery scripts then post to the author of the script.
¯\_(ツ)_/¯ -
Windows version mis-match for Install.WIM, shows it as "Windows 8.1 Enterprise"
The 9926.0.150119-1648.FBL_AWESOME1501_CLIENTENTERPRISE_VOL_X64FRE_EN-US.ISO downloaded from Microsoft's server is showing the wrong version when I import it into MDT 2013.
I thought maybe MDT 2013 was reading the WIM file wrong, so I checked it myself and it showed the Install.WIM as "Windows 8.1 Enterprise".
I've redownloaded it twice since first noticing and still see the same version.
dism /Get-WimInfo /WimFile:E:\sources\install.wim /index:1
Deployment Image Servicing and Management tool
Version: 6.3.9600.17031
Details for image : E:\sources\install.wim
Index : 1
Name : Windows 8.1 Enterprise
Description : Windows 8.1 Enterprise
Size : 13,335,592,751 bytes
WIM Bootable : No
Architecture : x64
Hal : acpiapic
Version : 10.0.9926
ServicePack Build : 0
ServicePack Level : 0
Edition : Enterprise
Installation : Client
ProductType : WinNT
ProductSuite : Terminal Server
System Root : WINDOWS
Directories : 18977
Files : 90593
Created : 2015-01-20 - 9:51:18 AM
Modified : 2015-01-20 - 9:54:03 AM
Languages :
en-US (Default)
The operation completed successfully.Hi Derek,
Thank you for your feedback.
I tested at my side and see the same result:
The version is 10.0.9926, for teh description and the Name part, we may take use of Windows Feedback tool to submit this.
Best regards
Michael Shao
TechNet Community Support -
Factory recovery partition on windows 8 in Asus X551CALaptop
I purchased Asus x551CA notebook on 22nd Feb 2014. After about 45 days I formated hard disk partition
on which Activated Windows 8 operating systme was installed.I formatted an repartitioned HDD.
And I installed and uninstalled windows8 and windows 8.1 90 days enterprise evaluation edition. Because of
these link to factory recovery partition is broken.
I have created system image disks which are working to restore system. I forgot how I created these disks. May be
I did control panel>recovery>file history>windows 7 file recovery. So these disks should be System Image Backup.
I think these are not OEM recovery disks. When I insert these disks during reset and refresh I get a message
that "Media you inserted is not valid". And I am able to create system image on second partition of hard disk of
my laptop.I have also got product key of windows 8 by a program jellybean keyfinder.
To restore from discs created by me. I insert a repair disc then I go to UEFI settings. Then I change boot preferences to
boot from DVD. Then I go to Restore form images. Then computer asks me to insert my discs no from 1 to 4. One after the other. Then computer restore to windows 8. It looks alike as it was factory made.
-When I try to create a recovery drive by going to control panel> Recovery >create a recovery drive
Recovery drive dialog box appears but with grayed check box of "copy the recovery partition from PC
to the recovery drive". Please tell me how can it come with not grayed dialog box so that I can copy
recovery partition to USB pen drive? When notebook was new this check box was not grayed and I was able to
copy recovery partition on USB pen drive.
-Since I cannot copy recovery partition to USB therefore I also cannot reset and refresh windows 8 on
the basis of USB. It was working when notebook was new.
-And reset or refresh also not working on the basis of hidden recovery partition. How can it will start
working? It was working when notebook was new.
-I have tried diskpart command do make hidden recovery partition visible. But it becomes invisible
after restart. I used following command
1. Command Prompt Run as administer.
2. diskpart
3. list disk
4. select disk 0
5. list partition
6. select partition 6
7. assign letter z
by these commands hidden recovery partition becomes visible and again when I restart laptop it becomes invisible.
And I am not able to do anything with recovery partition E.G. copy the recovery partition to USB
When I created a system image using the following command I became able to refresh my PC. May be it was refreshing
on the basis of newly created image.
recimg /createimage D:\IMAGE81
recimg /setcurrent D:\IMAGE81
But it is also not working this time and it gives a message "Drive on which windows is installed is locked unlock it".
May because I installe AVG antivirus it locked the drive.
I also used REAgentC command
reagentc /setreimage /path F:\Recovery\WindowsRE\ /target C:\Windows /bootkey 4300
Maybe I executed above command once again I used D: instead of F:
And I was able to refresh PC but I was not able to Reset. And I was not able to copy recovery partition on USB
by going to control panel> Recovery >create a recovery drive.
Recovery drive dialog box appears but with grayed check box of "copy the recovery partition from PC
to the recovery drive".
((I am giving images of computer management in first_image no partition was created it was in factory made state. And
in second_Image I created an extra disk partition which is present on disk this time.)) I cannot give images because
of my account is not varified.
So I am giving output of diskpart command to understand disk partitions.
C:\>diskpart
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
Disk 0 Online 465 GB 1024 KB *
DISKPART> list volume
Volume ### Ltr Label Fs Type Size Status Info
Volume 0 E DVD-ROM 0 B No Media
Volume 1 C OS NTFS Partition 186 GB Healthy Boot
Volume 2 D DATA NTFS Partition 130 GB Healthy
Volume 3 F DOWNLOADS NTFS Partition 128 GB Healthy
Volume 4 SYSTEM FAT32 Partition 100 MB Healthy System
Volume 5 Recovery NTFS Partition 900 MB Healthy Hidden
Volume 6 Restore NTFS Partition 20 GB Healthy Hidden
in the beginnig instead of D: (130 GB) and F:(128 GB) there was only one partition D:(258 GB) 130+128 GB.
Please tell me answers of following quesions:-
1. Tell me how to regain the link to factory recovery drive.
2. Please tell me how can I refresh and reset PC on the basis of Hidden Factory Recovery Partition. And how can I copy Hidden Factory Recovery Partition on USB and DVDs. I have 16GB USB pen drive and a DVD writer. So I can use these two storage media
only and except these I have 500GB HDD on my laptop.
4. I want to know that Factory recovery partition is useful or not. Should I delete it.
3. I have DVDs as I said above. On the basis of these I can reinstall windows 8. When I created these discs windows 8 was present on laptop. Currently windows 8.1 is present on laptop. Please tell me how can I create my own hidden recovery partition for
windows 8. I have upgraded to windows 8.1. So please tell me can I create my own hidden recovey partition for windows 8.1.
5. Can I download contents of factory recovery partition from internet.
6. Should I go to shopkeeper. He repairs computers as well. Probably he will manage for me to get Recovery partition discs. In this case these DVDs may be different from my DVDs as I mentioned above. Maybe only thing I get from these discs that I will
able to reset and refresh computer.
7. Microsoft shoult create a program that can re-establish link to factory recovery partition. And this program should be able to create new hidden recovery partition as well. As I have upgraded to windows 8.1. So I think I should have a new hidden recovery partition
for Windows 8.1. I think I can above thing my other way. If I create new set of DVDs by going to control panel>recovery> file history>System Image Backup. It will create discs for windows 8.1. And I will able to restore system to windows
8.1 by these discs. And for windows 8 I have already discs. But these discs will only work by changing boot options(by choosing UEFI) and image recovery. And reset and refresh functions will not work then in such situation factory recovery partition
will become useless. Then such situation I should delete factory recovery partition as it is useless.
8. At beginnign I also tried AI recovery burner. After trying it for 2-3 days I came to know that AI recovery burner is not for windows 8. There should be a tutorial for these thing so that people like me not waste their time.I used a software named UNDELETE on my hidden recovery partition to recover it. I get some files by this software. Important thing is that I got a 2.84 GB file named 00eebc9d.rb in dir D:\recovered1\Files Detected by their Signatures\Unknown Application\.rb.
This file may be useful. Please suggest me how can I use these files to reset and refresh my OS. I used some dir commands as follows to get list of these files:
dir /s >f:\list.txt
dir /s /a:s >f:\list2.txt
Some files were system files so these file were not shown by first dir command. So I used second dir command.
Output of dir /s >f:\list.txt
Volume in drive D is DATA
Volume Serial Number is 9A82-D42B
Directory of D:\recovered1
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
29-07-2014 19:08 <DIR> $Extend
29-07-2014 19:06 <DIR> Files Detected by their Signatures
29-07-2014 19:06 <DIR> Recovery
29-07-2014 19:08 <DIR> System Volume Information
0 File(s) 0 bytes
Directory of D:\recovered1\$Extend
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
29-07-2014 19:08 <DIR> $RmMetadata
0 File(s) 0 bytes
Directory of D:\recovered1\$Extend\$RmMetadata
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
29-07-2014 19:08 <DIR> $TxfLog
0 File(s) 0 bytes
Directory of D:\recovered1\$Extend\$RmMetadata\$TxfLog
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
29-07-2014 17:36 65,536 $TxfLog.blf
29-07-2014 17:36 10,485,760 $TxfLogContainer00000000000000000001
18-04-2014 00:18 10,485,760 $TxfLogContainer00000000000000000002
3 File(s) 21,037,056 bytes
Directory of D:\recovered1\Files Detected by their Signatures
29-07-2014 19:06 <DIR> .
29-07-2014 19:06 <DIR> ..
29-07-2014 19:05 <DIR> Firefox
29-07-2014 19:05 <DIR> Internet Explorer
29-07-2014 19:05 <DIR> Pick an app
29-07-2014 19:05 <DIR> Unkown Application
29-07-2014 19:06 <DIR> Windows Photo Viewer
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Firefox
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:05 <DIR> .xml
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Firefox\.xml
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 18:59 1,091 00000150.xml
29-07-2014 18:59 1,336 005f05b0.xml
29-07-2014 18:59 1,091 005f05b8.xml
29-07-2014 18:59 488 015c7e34.xml
29-07-2014 18:59 472 015d68fd.xml
29-07-2014 18:59 472 015d6bc3.xml
6 File(s) 4,950 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Internet Explorer
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:05 <DIR> .gif
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Internet Explorer\.gif
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:01 2,428 003aca99.gif
29-07-2014 19:01 814 0047c75d.gif
29-07-2014 19:01 472 00b2846d.gif
3 File(s) 3,714 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Pick an app
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:05 <DIR> .cab
29-07-2014 19:05 <DIR> .ico
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Pick an app\.cab
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 18:59 17,317,845 000c98e2.cab
29-07-2014 18:59 92,631,005 0027defd.cab
29-07-2014 18:59 7,539 00334cf3.cab
29-07-2014 18:59 15,731 0066bf8e.cab
4 File(s) 109,972,120 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Pick an app\.ico
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 18:59 4,534 0027d8d6.ico
29-07-2014 18:59 4,534 0027d8df.ico
29-07-2014 18:59 766 0027d8eb.ico
29-07-2014 18:59 766 0027d8ee.ico
29-07-2014 18:59 766 0027d8f2.ico
29-07-2014 18:59 4,534 0027dbef.ico
29-07-2014 18:59 10,134 0027dbfb.ico
7 File(s) 26,034 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Unkown Application
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:05 <DIR> .ogg
29-07-2014 19:05 <DIR> .rb
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Unkown Application\.ogg
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 18:59 194,667 00369b71.ogg
29-07-2014 18:59 173,149 0036b2a1.ogg
29-07-2014 18:59 13,178 0036b527.ogg
29-07-2014 18:59 19,244 0036e009.ogg
29-07-2014 18:59 169,220 0036e18a.ogg
29-07-2014 18:59 114,800 0036f031.ogg
29-07-2014 18:59 22,325 0037003d.ogg
29-07-2014 18:59 42,628 003703fd.ogg
29-07-2014 18:59 319,493 00370bc2.ogg
29-07-2014 18:59 68,812 00373cfa.ogg
29-07-2014 18:59 89,541 00373e29.ogg
29-07-2014 18:59 65,697 00375384.ogg
29-07-2014 18:59 42,955 00376d11.ogg
29-07-2014 18:59 85,254 0037847f.ogg
14 File(s) 1,420,963 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Unkown Application\.rb
29-07-2014 19:05 <DIR> .
29-07-2014 19:05 <DIR> ..
29-07-2014 19:01 3,058,238,593 00eebc9d.rb
1 File(s) 3,058,238,593 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Windows Photo Viewer
29-07-2014 19:06 <DIR> .
29-07-2014 19:06 <DIR> ..
29-07-2014 19:06 <DIR> .jpg
29-07-2014 19:06 <DIR> .png
0 File(s) 0 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Windows Photo Viewer\.jpg
29-07-2014 19:06 <DIR> .
29-07-2014 19:06 <DIR> ..
29-07-2014 18:59 12,296 0027dbce.jpg
29-07-2014 18:59 41,093 003933da.jpg
29-07-2014 18:59 25,067 00396fae.jpg
29-07-2014 18:59 2,303 003c5891.jpg
4 File(s) 80,759 bytes
Directory of D:\recovered1\Files Detected by their Signatures\Windows Photo Viewer\.png
29-07-2014 19:06 <DIR> .
29-07-2014 19:06 <DIR> ..
29-07-2014 18:59 64,902 0035b639.png
29-07-2014 18:59 530 0039c185.png
29-07-2014 18:59 556 003be59e.png
29-07-2014 18:59 1,023 003ed468.png
29-07-2014 18:59 1,704 003f1ec0.png
29-07-2014 18:59 624 003f252a.png
29-07-2014 18:59 13,777 0043a2c0.png
29-07-2014 18:59 2,897 00441e87.png
29-07-2014 18:59 2,915 00442a6c.png
29-07-2014 18:59 2,973 00442b91.png
29-07-2014 18:59 468 004433ca.png
29-07-2014 18:59 363 00443501.png
29-07-2014 18:59 238 00443be0.png
29-07-2014 18:59 331 00443fd9.png
29-07-2014 18:59 457 004442ad.png
29-07-2014 18:59 2,868 004444a7.png
29-07-2014 18:59 268 004446af.png
29-07-2014 18:59 280 004448d1.png
29-07-2014 18:59 257 004449f1.png
29-07-2014 18:59 2,158 00b962d1.png
29-07-2014 18:59 54,191 016a8a54.png
29-07-2014 18:59 4,224 017350e3.png
29-07-2014 18:59 4,241 01735f08.png
23 File(s) 162,245 bytes
Directory of D:\recovered1\Recovery
29-07-2014 19:06 <DIR> .
29-07-2014 19:06 <DIR> ..
29-07-2014 19:08 <DIR> Logs
29-07-2014 19:08 <DIR> WindowsRE
0 File(s) 0 bytes
Directory of D:\recovered1\Recovery\Logs
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
0 File(s) 0 bytes
Directory of D:\recovered1\Recovery\WindowsRE
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
0 File(s) 0 bytes
Directory of D:\recovered1\System Volume Information
29-07-2014 19:08 <DIR> .
29-07-2014 19:08 <DIR> ..
0 File(s) 0 bytes
Total Files Listed:
65 File(s) 3,190,946,434 bytes
65 Dir(s) 178,172,325,888 bytes free
dir /s /a:s >f:\list2.txt
Volume in drive D is DATA
Volume Serial Number is 9A82-D42B
Directory of D:\recovered1
17-04-2014 23:37 2,560 $AttrDef
17-04-2014 23:37 0 $BadClus
17-04-2014 23:37 655,680 $Bitmap
17-04-2014 23:37 8,192 $Boot
17-04-2014 23:37 67,108,864 $LogFile
17-04-2014 23:37 262,144 $MFT
17-04-2014 23:37 4,096 $MFTMirr
17-04-2014 23:37 0 $Secure
17-04-2014 23:37 131,072 $UpCase
17-04-2014 23:37 0 $Volume
10 File(s) 68,172,608 bytes
Directory of D:\recovered1\$Extend
17-04-2014 23:37 0 $ObjId
17-04-2014 23:37 0 $Quota
17-04-2014 23:37 0 $Reparse
01-05-2014 09:24 0 $UsnJrnl
4 File(s) 0 bytes
Directory of D:\recovered1\$Extend\$RmMetadata
17-04-2014 23:37 0 $Repair
1 File(s) 0 bytes
Directory of D:\recovered1\$Extend\$RmMetadata\$TxfLog
17-04-2014 23:37 100 $Tops
1 File(s) 100 bytes
Directory of D:\recovered1\Recovery\Logs
30-04-2014 06:12 1,336 Reload.xml
1 File(s) 1,336 bytes
Directory of D:\recovered1\Recovery\WindowsRE
18-06-2013 20:38 3,170,304 boot.sdi
29-04-2014 17:13 1,091 ReAgent.xml
26-04-2014 23:06 255,077,005 Winre.wim
3 File(s) 258,248,400 bytes
Directory of D:\recovered1\System Volume Information
18-04-2014 00:19 20,480 tracking.log
1 File(s) 20,480 bytes
Total Files Listed:
21 File(s) 326,442,924 bytes
0 Dir(s) 178,172,325,888 bytes free
Kindly guide me how can I use my hidden recovery partition to reset and refresh by use of these files. -
Windows 8.1 apps freeze and minimise to tray
Hi!
I have a problem with my win 8.1 machine. All the windows 8.1 apps like the store, weather freeze on their splash screen when I start them and then they minimise to tray. If I try to maximise them again they minimise back again after a few seconds.
These apps never get past the splash screen and there are no swirling loading dots on them (There is a similar problem other people had but they had swirling loading dots and I don't. Also I tried all the solutions I could find for that problem and none
worked). Also my apps don't have an X in the tile corner (unlike an other similar problem) and the solutions to that one also don't work for me. I tried WSreset.exe too but it just threw back a "Application didn't run" error window. I downloaded
the windows store troubleshooter and it concluded that there was a problem with store cache that it couldn't fix.
I have ownership of app security set to SYSTEM.
I ran out of ideas and hope there someone here who can give me some pointers.Thanks for replying!
The powershell code doesn't seem to do anything. I copypasted it and ran it but absolutely nothing happened.
the dism.exe code in Admin CMD started running and froze at a line that said "Image Version: 6.3.9600.17031"
it stayed like that until I tried to restart the machine at which point it threw back an error code and made a log I posted at the end of this comment. ("Nincs elég hely a lemezen." is hungarian for "not enough space on disk." but I have
about 400GB free on C: so I don't know what this is supposed to mean.
Also "A fájlnév, a könyvtárnév vagy a kötetcímke szintaxisa nem megfelelő." means "File name or library name or volume label sintax is incorrect")
The log continues with a very long line of Chinese characters, I pasted all the english parts.
[1876] Caller did not request sparse mount
[1876] Mounting new image.
Wim: [\\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim]
Image Index: [1]
Mount Path: [C:\WINDOWS\TEMP\cf68910e-6a60-4f2c-b10b-e57e9af0a1e5]
[1876] Wimserv process started for guid c60200d8-6e99-4c3b-9919-420ed5dd15b8. Id is 1384
[1384] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1384] Mounted image at C:\WINDOWS\TEMP\cf68910e-6a60-4f2c-b10b-e57e9af0a1e5.
[1876] [0x8007007b] FIOReadFileIntoBuffer:(1415): A fájlnév, a könyvtárnév vagy a kötetcímke szintaxisa nem megfelelő.
[1876] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1876] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1876] [0x8007007b] FIOReadFileIntoBuffer:(1415): A fájlnév, a könyvtárnév vagy a kötetcímke szintaxisa nem megfelelő.
[1876] [0xc142011c] UnmarshallImageHandleFromDirectory:(511)
[1876] [0xc142011c] WIMGetMountedImageHandle:(2568)
[1876] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1876] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1876] ImageUnmarshallHandle: Reconstituting wim at \\?\GLOBALROOT\device\harddisk0\partition5\Recovery\WindowsRE\Winre.wim.
[1876] [0x80070070] ReadWriteDataInternal:(134): Nincs elég hely a lemezen.
[1876] [0x80070070] WriteDataCallback:(1143): Nincs elég hely a lemezen.
[1876] [0x80070070] AddCaptureNodeToImage:(4190): Nincs elég hely a lemezen.
[1876] [0xc144012e]
〲㌱ㄭⴰㄲㄠ㨲㠲㔺ⰴ䔠牲牯††††††††䐠卉⁍†䥄䵓圠䵉倠潲楶敤㩲倠䑉ㄽ㜸‶㩃坜湩潤獷呜浥屰晣㠶ㄹ攰㘭㙡ⴰ昴挲戭〱ⵢ㕥攷愹てㅡ㕥坜湩潤獷卜獹整㍭尲牤癩牥屳ㅳ甸楮祳䠨䕒啓呌〽㡸〰〷㜰⤰ⴠ䌠楗䵭湡条牥㨺楗偭潲楶敤䵲杳潌䍧污扬捡൫㈊ⴳ〱㈭‱㈱㈺㨸㐵牅潲††††††††䥄䵓†䐠卉⁍䥗⁍牐癯摩牥›䥐㵄㠱㘷䌠尺楗摮睯屳敔灭捜㙦㤸〱ⵥ愶〶㐭㉦ⵣㅢ戰攭㜵㥥晡愰攱尵楗摮睯屳祓瑳浥㈳摜楲敶獲獜〱㠱湵捩献獹⠠剈卅䱕㵔砰〸㜰〰〷 坃浩慍慮敧㩲场浩牐癯摩牥獍䱧杯慃汬慢正[1876] [0x80070070] ProcessWimQueueNode:(448):
Nincs elég hely a lemezen.
[1876] [0x80070070] DequeueWimData:(303): Nincs elég hely a lemezen.
[1876] [0x80070070] ImageWorkerThread:(550): Nincs elég hely a lemezen.
[1876] [0x80070070] GetImageErrorCode:(3701): Nincs elég hely a lemezen.
[1876] [0x80070070] ImageWorkerThread:(534): Nincs elég hely a lemezen.
[1876] [0x80070070] GetImageErrorCode:(3701): Nincs elég hely a lemezen.
[1876] [0x80070070] ResAddFromFileAndHandle:(4414): Nincs elég hely a lemezen.
[1876] [0xc144012e]
〲㌱ㄭⴰㄲㄠ㨲㠲㔺ⰴ䔠牲牯††††††††䐠卉⁍†䥄䵓圠䵉倠潲楶敤㩲倠䑉ㄽ㜸‶㩃坜湩潤獷呜浥屰晣㠶ㄹ攰㘭㙡ⴰ昴挲戭〱ⵢ㕥攷愹てㅡ㕥坜湩潤獷卜獹整㍭尲牤癩牥屳ㅳ㈰洹浧祳䠨䕒啓呌〽㡸〰〷㜰⤰ⴠ䌠楗䵭湡条牥㨺楗偭潲楶敤䵲杳潌䍧污扬捡൫㈊ⴳ〱㈭‱㈱㈺㨸㐵牅潲††††††††䥄䵓†䐠卉⁍䥗⁍牐癯摩牥›䥐㵄㠱㘷䌠尺楗摮睯屳敔灭捜㙦㤸〱ⵥ愶〶㐭㉦ⵣㅢ戰攭㜵㥥晡愰攱尵楗摮睯屳祓瑳浥㈳摜楲敶獲獜〱㤲杭瑭献獹⠠剈卅䱕㵔砰〸㜰〰〷 坃浩慍慮敧㩲场浩牐癯摩牥獍䱧杯慃汬慢正[1876] [0x80070070] AddFileNodeToImage:(2120):
Nincs elég hely a lemezen.
[1876] [0x80070070] EnumImageFiles:(1968): Nincs elég hely a lemezen.
[1876] [0x80070070] EnumImageFiles:(1986): Nincs elég hely a lemezen.
[1876] [0x80070070] EnumImageFiles:(1986): Nincs elég hely a lemezen.
[1876] [0x80070070] EnumImageFiles:(1986): Nincs elég hely a lemezen.
[1876] [0x80070070] WriteFileImage:(1931): Nincs elég hely a lemezen.
[1876] [0x80070070] GetImageErrorCode:(3701): Nincs elég hely a lemezen.
[1876] [0x80070070] WriteDirImage:(1702): Nincs elég hely a lemezen.
[1876] [0x80070070] ImageRecaptureDirectory:(657): Nincs elég hely a lemezen.
[1876] [0x80070070] WIMCommitImageHandle:(1201): Nincs elég hely a lemezen.
〲㌱ㄭⴰㄲㄠ㨲㠲㔺ⰵ䔠牲牯††††††††䐠卉⁍†䥄䵓圠䵉倠潲楶敤㩲倠䑉ㄽ㜸‶䥔㵄㘱㈵戠獡履瑮敳畴屰灯 -
Recover Windows 7 with Recovery Media from WXP
Created a Recovery Media from a preinstalled ThinkCentre (M58p) Windows 7. Stored on DVD including WINR.WIM total size 257 Mb. Installed Windows XP using Lenovo RnR DVD's. So far no problem.
Now wanting to know how I can recover the factory W7. Used the Recovery Media W7, Windows starts Product Recovery, selected method 'Restore to factory default state'.
Wizard asks for Product Recovery Disc 1.
I created the Recovery Media in assumption having the opportunity to restore the factory Windows 7.
Do I need the recovery disks of Lenovo for this? Does the Recovery Media only work in combination with W7 OS?
F11 starts RnR for the WXP. The recovery partition of W7 seems to be deleted by the recovery of WXP.
In the past (pre-ThinkVantage-period) I used Ghost for the original factory OS's, did work nicely.
Solved!
Go to Solution.Hi,
welcome to the forum.
Ok, so let's start from the scratch. What you have created while the Win7 was instaled was not an "image" nor a backup of your system. That was just a bootable "Rescue" disc, so that in case you cannot boot up into OS, you can boot from this CD and this will give you some options to save your date, etc.
Unfortunately on your protection I have to tell, that it is a bit harder to differ the two buttons, where one says "Create Rescue and Recovery disc" and the second one "Create recovery media". The one will create a disk, like you have. The second one will create you a new set of recovery CDs, that you could use for the restore of your system.
So in this situation, where also the original RnR Win7 partition is gone, Is the only chance to get back to Win7, to call support and ask for the Recovery CDs.
Let me know, if this post helps you. a bit.
Also feel free to asky any add question. I'll be happy to answer them if I know the correct answer
Cheers -
Windows Image Boot is a new Windows 8.1 update installation method for UEFI Windows Tablet PC and UEFI/SSD based PC. The entire operating system is one 2.5 GB compressed large image file and the system is booting from there.
I just inform you, WimBoot (Windows Image Boot) project accomplished for Toshiba Encore.
This is a step by step tutorial how to create a WimBoot image for your Toshiba Encore, or repair a non booting Encore device.
Here are the keywords:
- Boot from original Windows 8.1 update MSDN image
- Windows automatic activation from UEFI Microsoft Data Management table
- Offline activation (during HDD Recovery, Windows still remains activated)
- OOBE (Out of Box Experience)
- BayTrail drivers on kernel level
- Windows Image equal Recovery Image
- Usable for every 32-64 GB Toshiba Encore
- HDD Recovery and Full Factory Reset
- Min 22.2GB max. 24.5GB free space on 32 GB (hibernation off, swap file 512MB)
- 100% clean, no third party software
- Operation System only
- Easy install and partitioning from USB flash drive
Other:
- User may download and install Retail or OEM Office Home Student 2013, and activate with shipped key
Office 2013 Home Student
- User may find original Office files from Factory Toshiba Image also:
Install.wim\ProgramData\Microsoft\OEMOffice15\Office15\x86\15.0.4454.1510\
Remained task:
- We need create country specific images and upload for a server to share with other Toshiba Encore users. Microsoft experts reported this action is illegal at the moment, so we droped and canceled. Thanks for understanding.
Screenshoot:
A lucky Toshiba Encore with Windows 8.1 update MSDN HUN image boot.
EFI Partition size: 100MB
Windows C. Partition size: 26.18GB / 24.48 GB free
Windows Image and Recovery: 2.71GB
Total size: 29.00 GB
Step by Step instruction:
1. Download Section
2. Preparing Section
3. Creating Section
4. Deploying Section
Need a PC with Windows 8 or 8.1
Don not forget, run Windows ADK 8.1 update as administrator
Toshiba Encore is good for this job
1. Download section:
1. Download country specific Windows 8.1 with Update (multiple editions) (x86) DVD MSDN iso.
MSDN download, example:
pl_windows_8.1_with_update_x86_dvd_4048278.iso - Polish .2.86GB
hu_windows_8.1_with_update_x86_dvd_4048162.iso - Hungarian 2.86 GB
en_windows_8.1_with_update_x86_dvd_4065105.iso - English 2.86 GB
fi_windows_8.1_with_update_x86_dvd_4048107.iso - Finnish 2.86 GB
it_windows_8.1_with_update_x86_dvd_4048174.iso - Italian 2.86 GB
2. Dowload 32bit Windows 8.1 Update and put C:\MSU
Windows8.1-KB2919442-x86.msu 4.6 MB
Windows8.1-KB2919355-x86.msu 319.0 MB
Windows8.1-KB2932046-x86.msu 25.2 MB
Windows8.1-KB2934018-x86.msu 71.9 MB
Windows8.1-KB2937592-x86.msu 303 KB
Windows8.1-KB2938439-x86.msu 10.0 MB
3. Download Windows ADK 8.1 with update and install (adksetup.exe)
Windows ADK 8.1 2.8GB
4. Download BayTrail WinPE driver package and extract to C:\x86
Tablet input 4 MB
5. Download Toshiba Encore additional driver package and extract to C:\x86
Additional drivers 95 MB
6. Download WimBoot text files
WimBoot text files 5 Kb
7. Download and install 7-zip to easy extract ISO / WIM
7-zip 1 MB
2. Preparing Section:
Run ADK 8.1 update as administrator, and type:
copype x86 C:\WinPE_x86
Check dism version: 6.3.9600.17029 or higher need, type:
dism
Run 7-zip::
copy from MSDN iso\sources\install.wim to c:\WinPE_x86\media\sources\install.wim
copy from install.wim\2\Windows\System32\Recovery\WinRE.wim to c:\WinPE_x86\media\sources\WinRE.wim
Other Task:
Check your language code
Check everything again, are you ready to create?
All updates are: C:\MSU
All drivers are: C:\x86
Both Wim files are: C:\WinPE_x86\media\sources
- Encore with WimBoot -
Solved!
Go to Solution.4. Deploying Section
HDD Recovery
Congratulation, if you are here, you have to come Malta with your Malta devide.
So, just boot again from your USB Recovery drive
- go to Troubleshoot > Advanced options > Command prompt
Find your USB driver letter, mine was d:
type:
d:
cd toshiba
createBCD.bat
Now succesfully created your HDD Recovery boot store.
So, go back to your Windows,
open a command prompt as administrator.
type:
reagentc /enable
Now, you are a happy owner a fully functional Toshiba Encore WimBoot device with
- HDD Recovery option and
- minimum 22.2 GB free space.
If you want to do a full Factory Reset, just use HDD recovery option in Toshiba Encore Boot menu:
Shut down > Press and Hold Power and Volume +
Select HDD Recovery (screenshoot from padgett)
and do a Factory Reset:
Troubleshoot > Reset your PC >
I hope, you enjoyed this tutorial, and finaly became a happy WimBoot owner as me. Preparing a perfect WimBoot enviroment was very hard task to me, but at last just completed and no error. I created this WimBoot configuration and enviroment on my 32 GB Toshiba Encore, and deployed to my wife and children' devices. 64 GB Encore users reported, everything is fine on 64 GB Encore also, so we don't need to worry about 64 GB Encore anymore.
So, if you are happy WimBoot owner, and successfully recovered and deployed my WimBoot configuration in your Encore, then please share your opinion and experience with others. Thank you for Encore community and everyone here:
tataniko
Created Robert Hegedus (tataniko) from central Mediterranean sea, Gozo island, 2014. April 18. (EU, Malta)
https://www.facebook.com/zenrobi
1. createBCD.bat
@echo off
@rem ////// createBCD.bat \\\\\\
@rem Change your local from hu-HU to pl-PL example
@echo -------------------------------------------------------
@echo Create "HDD Recovery" option in Toshiba UEFI boot menu
@echo by tataniko from
@echo forums.toshiba.com/t5/Encore-Tablets/bd-p/brd_Encore
@echo -------------------------------------------------------
@pause
@echo -----------------------------------------
@echo Mounting EFI S: and Recovery Partition T:
@echo -----------------------------------------
@pause
diskpart /s mount.txt
@pause
@echo -----------------------------
@echo Make secondary boot for WinRe
@echo -----------------------------
@pause
mkdir S:\EFI\Toshiba
xcopy /e /h S:\EFI\Microsoft\* S:\EFI\Toshiba\
del /a S:\EFI\Toshiba\Boot\BCD
@echo ------------------------------------------------------
@echo Create new BCD store, configure entries for WinRE boot
@echo ------------------------------------------------------
@pause
bcdedit /createstore S:\BCD
bcdedit /store S:\BCD /create {bootmgr} /d "Windows Boot Manager"
bcdedit /store S:\BCD /set {bootmgr} device partition=S:
bcdedit /store S:\BCD /set {bootmgr} locale hu-HU
bcdedit /store S:\BCD /set {bootmgr} integrityservices Enable
bcdedit /store S:\BCD /create {11111111-1111-1111-1111-111111111111} /d "Windows Recovery" /device
bcdedit /store S:\BCD /set {11111111-1111-1111-1111-111111111111} ramdisksdidevice partition=T:
bcdedit /store S:\BCD /set {11111111-1111-1111-1111-111111111111} ramdisksdipath \Recovery\WindowsRE\boot.sdi
bcdedit /store S:\BCD /create {22222222-2222-2222-2222-222222222222} /d "Windows Recovery Environment" /application osloader
bcdedit /store S:\BCD /set {bootmgr} default {22222222-2222-2222-2222-222222222222}
bcdedit /store S:\BCD /set {bootmgr} displayorder {22222222-2222-2222-2222-222222222222}
bcdedit /store S:\BCD /set {default} device ramdisk=[T:]\Recovery\WindowsRE\winre.wim,{11111111-1111-1111-1111-111111111111}
bcdedit /store S:\BCD /set {default} path \Windows\System32\winload.efi
bcdedit /store S:\BCD /set {default} locale hu-HU
bcdedit /store S:\BCD /set {default} displaymessage "Recovery"
bcdedit /store S:\BCD /set {default} osdevice ramdisk=[T:]\Recovery\WindowsRE\winre.wim,{11111111-1111-1111-1111-111111111111}
bcdedit /store S:\BCD /set {default} systemroot \Windows
bcdedit /store S:\BCD /set {default} nx OptIn
bcdedit /store S:\BCD /set {default} bootmenupolicy Standard
bcdedit /store S:\BCD /set {default} winpe Yes
@echo -------------------------------------------------
@echo Move created BCD store to the secondary boot path
@echo -------------------------------------------------
@pause
xcopy /h /y S:\BCD* S:\EFI\Toshiba\Boot\.
del /a S:\BCD*
@echo ----------------------
@echo Check WinRe enviroment
@echo ----------------------
@pause
C:\Windows\System32\Reagentc /Info /Target c:\Windows
@echo -------------
@echo End of Batch
@echo -------------
@pause
2. Mount.txt
rem //// Mount.txt \\\\
sel disk 0
list vol
sel vol 1
assign letter=s
sel vol 2
assign letter=t
list vol
exit
- Encore with WimBoot - -
Reinstall of Windows 7 x64 on WD 750 HDD and set up of m-SATA Caching
I am sorry but non of the above have any answers to my question.
A Tech from my OEM ran Disk Part in 12/13 thinking that it was a bad image. Unfortunately now no one can fix the Window 7 x64 install as MBR disk using the UEFI Bios.
I have called Microsoft Answer Desk have a Prem account. And most of the time I am told that the only way to run the install is to use the system in AHCI.
This of course take out the Intel RST and I can not configure the m-SATA and use 64GB as a cashing device.
When I call Intel the gave me a case number but after two days they said that after before I run the OS install to change the BIOS from AHCI to Raid. Reset the drives from Control I then run the install from the OEM USB.
This is the guide they asked me to use:
1.Set the BIOS from with SATA mode to RAID
2. Install the Windows 7x64 from either the USB which as all Alien software or the Windows DVD
3. If installing from the DVD once Windows Installer comes up go to F6 and install the INf files for the Controller for the in order to load the drive Partitions.
4. Delete all the Partitions and run the Windows Install
Having the USB to install from I don't need to do the above process.
What no one is telling either from the OEM, Intel, or Microsoft is when I am in the BIO's where do I run the install from. Is it the Legacy cd/dvd or the Legacy USB.
Or do I use the UEFI DVD which clearly spells out the name and type of dvd,blue Ray drive I have.
Or do I use the UEFI USB which again spells out the type of drive it is.
Every time I use the UEF I DVD or UEFI USB the system will install the disks as GPT and this is a major mess.
There is one more option no one is explaining and that is if I install using the Legacy DVD or USB the is another line in the booting section of the BOIS that sets the system as a boot UEFI BIOS. This can be changed
to a legacy bios and I can still keep the OROM which is the Control I needed for Caching the m-sata.
CAN YOU PLEASE HELP. PLEASE SEND ME AN EMAIL AS TO WHICH PART I HAVE RIGHT AND WHICH PART I NEED TO CHANGE. IF EVERYTHING IS WRONG PLEASE SEND ME INSTUCTIONS AS TO THE CORRECT PROCESS.
I HAVE BEEN WORKING ON THIS SYSTEM FOR SO LONG NIGHT AND DAY. READ EVERYTHING I CAN FIND ON THIS FROM TECHNET TO INTEL AND SERVERAL TECH FORMS NO HAS THE ANSWER AND I HAVE A $3500 UNUSABLE SYSTEM
Thank you so much for letting my post.
[email protected]
Next go to the Control panel and run from the
The following is my system configuration:
Alienware 17
OS Windows 7 Ultimate x64
Bios is a UEFI Bios that can be set to legacy or UEFI
CPU: Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz Intel Haswell Revision 0/6
Intel Chipset version 9.4.2.1017,
Target PDH/Chipset xeon Processor E3-1200 v3 and v4 Intel 8 Series, C220
Intel Lynx Point HM87 v9.4.0.1017
Intel Rapid Storage: ver. 12.9.0.1001
Intel HD Graphics 4600 ver. 15.33.14.64.34.12
NVidia GeForce GTX 780M
Memory: DDR3 1600 MHz SODIMM - size each = 4GB x 4 = 16GB
Ethernet: QUALCOMM Killer e2201 Gigabit NDIS 6.20
Wi-Fi: Broadcom 802.11ac BCM 4352 BT 4.0
Storage Device For OS: WDC WD7500BPKX-75HPJT0 750.1 GB 7200 RPM SATA-600
Storage Device For Accelerated Cache: LITEONIT DMT-80M6M-11 mSATA 80GB SATA-600 TRIM Disabled
DVD Writer: LG Electronics HL-DT-ST DVDRWBD CA40N SCSI CdRom Blu-ray Read Only
System Must Have Supported Software: AlienwareRespawn Ver. 15 for Windows 7
Alienware Autosy = not a much have but nice to keep take of hardware issues and warranty
Alienware Command Center Includes: /Adrenaline Performance Monitoring and /Game Mode Also includes Fusion for Quick and Advanced Power Plan Settings Controls AlienFX with controls
Keyboard color display which can be connected to System State. Events, and
Applications Alienware On Screen Display = Includes EMSC.dll for NT Kern Driver or Embedded System Control for Hardware Properties DSubOSD Supports Display In HDMI
Sincerely, Frances SteeleDue to the Disagreement between a few OEM techs some of them insist that I install as UEFI with GPT and yet other insist I use Legacy. So the problem starts with setting up the BIOs correctly.
When the system was received in Oct 2013 the Boot options began with Windows Fast Boot = Disabled
I had both options at that time of Legacy or UEFI
I must admit I don't remember if OROM was enable or disabled.
I have both options and I can find am unable to clearly define which options is best.
So I have made many phone calls to the OEM requesting help with this set up.
I am certain of at this point is that when they sent me a USB that was for
Windows 7 with out SP1 the system installs and the drives are formatted as MBR. The best part of this USB is that it had the correct Alienware software (AlienAutopy & Alien Respawn) both import
to this type of system.
I am also certain that when I use the USB that Alienware sent me with
Windows 7 SP1 it is clearly installing as GPT using UEFI install. I found and have a copy of the master install script that shows this action. So what I find is that when I use the USB with out any action from
me the system is automatically installed in the way. This USB doesn't have any of my drivers nor did it have Alien Autopy or Alien Respawn.
I got so tired of the back of forth misinformation I have been receiving, that I request that I pay for a 1 TB completely Imaged drive that match my system.
I received it on 4/02/14 along with a the World Wide Tech service came to install it. My first question to this tech before he even touched the laptop was, do you understand that I had a m-SATA
installed and do you know how to set up the BIOs for this.
His answer was that this was not his job. So I asked him to please wait before he installed the drive and let me call Alienware to confirm that the BIOs was set correctly and what we needed to do in order for the Operating
System to be installed correctly.
His answer was that he didn't have time. I had to let him do his job and install the drive.
So I did. Right after the install I new something was not right so I began copying every file I could find that contained drivers, Sysprep, all logs the complete System 32 Windows files and SysWOW Files.
After the first reboot I found that Alienware Respawn was not installed. So because I knew were to get it from I downloaded it. After trying to install the software I received and error message that stated that since it could not find a Windows Recovery
Enjoinment that it would not install.
I noticed that the system was formatted with the disks as MBR (I checked this under Device Manager and clicked on the HDD under Properties it showed that is was MBR)
There was a 38MB OEM partition - a 750MB Recovery Partition - and the rest of the drive was for the Operating System.
Because I made a copy of all the logs and files before the reboot I was able to go back and find the under Panther the original I found the Setupact file it is 908 KB and I wish I could sent you an attached copy of it because it has a lot of information
that would help in how the drive was installed.
Remember I told you that the Tech only allowed me to make sure that OROM was enable and that SATA was set to RAID so I was unable to set the boot to Legacy or UEFI. So from this file as you will see there are a number
of errors it would seem that that the drive was installed as UEFI. (Although everything I have read on the subject states that a UEFI install automatically formats a disk to GPT) So this is why I am so very confused.
Because I can not attach the file here and am going to copy and past some of the items that give me this impression:
2014-04-02 16:56:23, Info [0x0601c1] IBS InstallWindows:Install Path = C:\Windows\system32\oobe
2014-04-02 16:56:23, Info [0x0601c2] IBS InstallWindows:Setup Phase = 4
2014-04-02 16:56:23, Info [setup.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE]
--> [IMAGE_STATE_UNDEPLOYABLE]
2014-04-02 16:56:23, Info [0x0601ee] IBS CreateSetupBlackboard:Successfully created/opened Setup black board path is [C:\Windows\Panther\SetupInfo]
2014-04-02 16:56:23, Info IBS InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [].
2014-04-02 16:56:23, Info IBS InstallWindows:Setup architecture is [x64]
2014-04-02 16:56:23, Info [0x0601d5] IBS InstallWindows:Starting with Empty Queue. Setup Phase = 4 callBack_DiagnosticDataGeneration: Setup was started from Phase 4. Disabling Diagnostics [DiagnosticDataGeneration]
in this scenario
2014-04-02 16:56:23, Info [0x060258] IBS GenerateName: Failed to read the Key UserData\FullName\Value from Blackboard defaulting to WIN
2014-04-02 16:56:23, Info [0x060259] IBS
GenerateName: Failed to read the Key UserData\OrgName\Value from Blackboard
2014-04-02 16:56:23, Info [0x06025d] IBS
list of function drivers from the critical device database (CDDB).
2014-04-02 16:56:24, Info SYSPRP Waiting for thread to exit...
2014-04-02 16:56:24, Info SYSPRP Status: Total = 0, Complete = 0, Progress = 0% (0%)
2014-04-02 16:56:24, Warning SYSPRP Installation was supposedly active, but status key doesn't exist?
2014-04-02 16:56:24, Info SYSPRP SPPNP: The device setup class for device ROOT\LEGACY_STORVSC\0000 is 8ecc055d-047f-11d1-a537-0000f8753ed1.
2014-04-02 16:56:24, Info SYSPRP SPPNP: Skipping device ROOT\LEGACY_STORVSC\0000 because it belongs to the legacy class.
2014-04-02 16:56:24, Info SYSPRP SPPNP: {Retrieving drivers used by device ACPI\PNP0C32\3}
2014-04-02 16:56:24, Info SYSPRP SPPNP: No device setup class has been specified for device ACPI\PNP0C32\3. We will not attempt to retrieve the device's class
filter drivers.
2014-04-02 16:56:24, Info SYSPRP SPPNP: No function driver specified for device ACPI\PNP0C32\3.
2014-04-02 16:56:24, Info SYSPRP SPPNP: No device upper filter drivers are specified for device ACPI\PNP0C32\3
2014-04-02 16:56:24, Info SYSPRP SPPNP: No device lower filter drivers are specified for device ACPI\PNP0C32\3
2014-04-02 16:56:24, Info SYSPRP SPPNP: {Retrieving drivers used by device ROOT\LEGACY_NTFS\0000}
2014-04-02 16:56:24, Info SYSPRP SPPNP: The device setup class for device ROOT\LEGACY_NTFS\0000 is 8ecc055d-047f-11d1-a537-0000f8753ed1.
2014-04-02 16:56:24, Info SYSPRP SPPNP: Driver isapnp was retrieved from the CDDB.
2014-04-02 16:56:24, Info SYSPRP Re-checking active
Now of course there is so much in the file I have skipped around and just pointed out the parts where I am hoping you will see installing legacy drivers and software were being skipped.
I called Alienware back and requested a level 2 tech I explained the situation and received a new 1 TB imaged hard drive today.
As I explained to the tech on the phone who again was uncertain if the BIOs should be set to UEFI or Legacy. I told him that we should try installing the drive with both USB's another possibility is to use Acronis Universal Restore and reinstall
from the backup that I made of the 1TB drive that is currently in the System now.
My worry (which I am most certain is valid) this that if we just drop the new drive in the system which making sure which BIOs setup is the most appropriate another Windows 7 x64 SP1 Ultimate will be destroyed. Because there is not
way to change the system from GPT to MBR or legacy to UEFI without having to reinstall the OS.
I have to admit that after 7 reinstalls on my own for one system I am really getting pretty sick and tired of working on this laptop. If I had the money I would make the purchase of an Origin PC in a heart beat but that would be $3200 that would match
the specs of this system.
I couldn't see the Recovery Partition so I Installed Acronis True Image 2014 Prem, and Backed up the disk. With this installed I was able to open the 750MB what I found was 1 folder for System 32 that has a folder with the name Recover but I am unable
to access it. was empty, 1 folder with the name Windowsre, in this folder there are 2 files one boot.sid and one winre.wim
I am not sure what you can do with any of this information but honestly any help would be most appreciated. Before Thursday 04/10/14 when I requested the tech who I spoke to today to return my call. At that time I am suppose to test out 3 or 4 difference
ways to install this drive and see if I can not find out what I am supposed to have in place for the BIOs before he helps me install the new 1TB HD. (which is the easy part)>
Sincerely, Frances Steele -
Cannot Create Recovery Media in Windows 7 Pro for x120e
You can have only one copy of the Microsoft Windows operation system. The Product Recovery Media Creator will exit now.
HI all. First, I have read "Creating Recovery Media in Windows 7" at http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-74040.
I get this message when attempting:
You can have only one copy of the Microsoft Windows operation system. The Product Recovery Media Creator will exit now.
What happened is that I blindly copied the recovery files to a USB and just copied to a folder on my desktop XP machine. So now my X120e is saying, sorry, you can't do that again. You already did it blockhead!
So how the heck do I undo this so I can create appropriate recovery media? System restore rollback? Registry key editing? Here are the files on my XP, I have no idea if I create Windows 7 pro recovery files from these.
Thanks all for any suggestions or known fixes,
chadnc
Root folder files & folders:
winRE.wim
usb.tag
Folder\factoryrecovery
Folder\Boot
Inside of Folder\factoryrecovery
sdrivebackup2.wim
cdrivebackup.swm
cdrivebackup2.swm
cdrivebackup3.swm
cdrivebackup4.swm
bcdinfo
RECOVERY
service_done
Inside of Folder\Boot
24 subfolders, starting with cs-CZ
BCD
boot.sdi
memtest
tag Hi chadnc
Have a look at the first bit of the post by The_Solutor in this thread :Making a usb stick with the Lenovo recovery partition bootable maybe that will help.
Like many things Microsoft, the "you can only burn recovery media once" limitation just inconveniences the honest users, but doesn't slow down the bad guys. Oh well....
Z.
The large print: please read the Community Participation Rules before posting. Include as much information as possible: model, machine type, operating system, and a descriptive subject line. Do not include personal information: serial number, telephone number, email address, etc. The fine print: I do not work for, nor do I speak for Lenovo. Unsolicited private messages will be ignored. ... GeezBlog
English Community Deutsche Community Comunidad en Español Русскоязычное Сообщество -
Looking for a way to solve permission problem in windows 7
one of the biggest problems i have with this windows that even that i'm an administrator and the owner of the computer i always have permission problems folders i get a no access errors with files and folders even thoughe i should have full permisions i belive system restore doesn't work for me because permissions problem and i don't know what to do anymore i'v used uac i'v disable uac i downloaded a registry file to take owernship on files and folders and still problems so what can i do to solve all this problems?
and to be honest i really don't like the way windows 7 behave with permisions this is my computer and i am an administrator why do i have to fight to access folders like System Volume Information,Recovery,Documents and Settings why do i get the lock icon when i take owenership and i'm on the users list but when i add users everyting is fine?
10x in advance.:)Hello,
This is by design. You cannot access the folder or files are protected by operation system even if your current user account is Administrator.
System Volume Information is a hidden and protected system folder that the System Restore tools uses to store it information and restore points.
In Recovery folder, there are two files: Winre.wim and boot.sdi. With these two files, you are able to boot the system to Windows Recovery Environment (WinRE) and do a repair without inserting a Windows 7 installation disc.
If you want to access the protected folders like “System Volume Information”, use the following method, but I do not recommend you do this. It may cause some potential problems:
1. Right click the System Volume Information folder and choose Properties.
2. In Security tab, click Edit and then click Add. Type in “everyone”(without quote) and click Ok.
3. Then “Everyone“ will be listed under ” Group or user names”, click Everyone, and check “allow” full control option.
As BurrWalnut said, the “Documents and Settings”, it is a junction. A junction point is also a protected operating system folder that points to another folder. The junction point is an important part of application compatibility and does not contain any data or other files. In Windows Vista and Windows 7, the “Documents and Settings” folder has been replaced with “Users” folder. All of your user profiles are saved in C:\Users\User name folder.
Thomas Lin -
Howdy,
I'm trying to enable my system with WinRE but all to no avail. What could be wrong?
The partition layout is as follows:
PS C:\Windows\system32> Get-Partition -DiskNumber 4
DiskId: \\?\scsi#disk&ven_msft&prod_virtual_disk#2&2e87576f&0&000002#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
PartitionNumber DriveLetter Offset Size Type
1 1048576 500 MB Recovery
2 525336576 100 MB System
3 630194176 128 MB Reserved
4 E 764411904 95 GB Basic
5 102769885184 4.29 GB Recovery
I formatted this 1st recovery partition into FAT32 and mounted the volume as R:
PS C:\Windows\system32> Get-Partition -DiskNumber 4 -PartitionNumber 1 | Format-Volume -FileSystem FAT32 -NewFileSystemL
abel RECOVERY -Force -Confirm:$false
Then I created the storage folder for the Recovery Environment on this R: volume:
PS C:\Windows\system32> mkdir "R:\Recovery\WindowsRE"
Directory: R:\Recovery
Mode LastWriteTime Length Name
d----- 13.01.2015 20:15 WindowsRE
And copied the WinRE.wim file from the storage folder on the Windows partition:
PS C:\Windows\system32> xcopy /H E:\Windows\System32\Recovery\Winre.wim R:\Recovery\WindowsRE\
E:\Windows\System32\Recovery\winRE.wim
1 File(s) copied
Finally, I attempted to enable the copied WinRE and registed it in Windows like that:
PS C:\Windows\system32> ReAgentc.exe /setreimage /path R:\Recovery\WindowsRE\ /target E:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk4\partition1\Recovery\WindowsRE
REAGENTC.EXE: Operation Successful.
However, checking the status with Reagent returns that WinRE is DISABLED:
PS C:\Windows\system32> ReAgentc.exe /info /target E:\Windows
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
And also:
PS C:\Windows\system32> .\ReAgentc.exe /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 6a7e9cfb-700d-11e4-95e0-00155d095900
Recovery image location: \\?\GLOBALROOT\device\harddisk3\partition4\RecoveryImage
Recovery image index: 4
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
Why is that? What am I doing wrong here?
How do I properly prepare OS for recovery?
Well this is the world we live in And these are the hands we're given...The target drive with location of WinRE.wim file MUST be NTFS formatted.
Here's what you need to do to enable WinRE.wim that is located on another partition (Partition 1 in my case):
1. Disable the current setup:
C:\Windows\system32>reagentc /disable
REAGENTC.EXE: Operation Successful.
2. Check the status:
C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
Recovery image location: \\?\GLOBALROOT\device\harddisk4\partition5\Recovery
Recovery image index: 1
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
3. Make sure that C:\Windows\System32\Recovery\ReAgent.xml contains zeroes in location elements.
This is a proper config:
<?xml version='1.0' encoding='utf-8' standalone='yes'?>
<WindowsRE version="2.0">
<WinreBCD id=""></WinreBCD>
<WinreLocation path="" id="0" offset="0"></WinreLocation>
<ImageLocation path="" id="0" offset="0"></ImageLocation>
<PBRImageLocation path="" id="0" offset="0" index="0"></PBRImageLocation>
<PBRCustomImageLocation path="" id="0" offset="0" index="0"></PBRCustomImageLocation>
<InstallState state="0"></InstallState>
<OsInstallAvailable state="0"></OsInstallAvailable>
<CustomImageAvailable state="0"></CustomImageAvailable>
<WinREStaged state="0"></WinREStaged>
<ScheduledOperation state="4"></ScheduledOperation>
<OperationParam path=""></OperationParam>
<OsBuildVersion path=""></OsBuildVersion>
<OemTool state="0"></OemTool>
</WindowsRE>
This is an incorrect config (this one demonstrates an already configured WinRE and OS Image configurations and cannot be reused to set another locations of WinRE and OSImage:
<?xml version='1.0' encoding='utf-8'?>
<WindowsRE version="2.0">
<WinreBCD id="{00000000-0000-0000-0000-000000000000}"/>
<WinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<ImageLocation path="\Recovery\WindowsRE" id="0" offset="1048576" guid="{a235fafb-a690-11e4-95dc-00155d095900}"/>
<PBRImageLocation path="\Recovery" id="0" offset="102769885184" guid="{a235fafb-a690-11e4-95dc-00155d095900}" index="1"/>
<PBRCustomImageLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}" index="0"/>
<InstallState state="0"/>
<OsInstallAvailable state="1"/>
<CustomImageAvailable state="0"/>
<IsAutoRepairOn state="1"/>
<WinREStaged state="1"/>
<OperationParam path=""/>
<OsBuildVersion path="9926.0.amd64fre.fbl_awesome1501.150119-1648"/>
<OemTool state="0"/>
<IsServer state="0"/>
<DownlevelWinreLocation path="" id="0" offset="0" guid="{00000000-0000-0000-0000-000000000000}"/>
<IsWimBoot state="0"/>
<ScheduledOperation state="4"/>
</WindowsRE>
4. Assign a drive letter to Partition 1.
C:\Windows\system32>diskpart
Microsoft DiskPart version 10.0.9926
Copyright (C) 1999-2013 Microsoft Corporation.
On computer: EH
DISKPART> list disk
Disk ### Status Size Free Dyn Gpt
Disk 2 Online 931 GB 0 B *
Disk 3 Online 930 GB 0 B *
Disk 4 Online 100 GB 0 B *
DISKPART> sel disk 4
Disk 4 is now the selected disk.
DISKPART> list part
Partition ### Type Size Offset
Partition 1 Recovery 500 MB 1024 KB
Partition 2 System 100 MB 501 MB
Partition 3 Reserved 128 MB 601 MB
Partition 4 Primary 95 GB 729 MB
Partition 5 Recovery 4390 MB 95 GB
DISKPART> sel part 1
Partition 1 is now the selected partition.
DISKPART> assign letter="R"
DiskPart successfully assigned the drive letter or mount point.
5. Remove existing Recovery folders on R:
R:\>rd Recovery /q /s
6. Prepare folder structure:
R:\>mkdir Recovery
R:\>mkdir Recovery\WindowsRE
7. Copy WinRE.wim image to WindowsRE:
R:\>xcopy /H C:\Windows\System32\Recovery\Winre.wim R:\Recovery\WindowsRE\
C:\Windows\System32\Recovery\Winre.wim
1 File(s) copied
8. Copy config file:
R:\>xcopy /H C:\Windows\System32\Recovery\ReAgent.xml R:\Recovery\WindowsRE
C:\Windows\System32\Recovery\ReAgent.xml
1 File(s) copied
4. Set WinRE recovery environment:
R:\>reagentc /setreimage /path R:\Recovery\WindowsRE /target C:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk4\partition1\Recovery\WindowsRE
REAGENTC.EXE: Operation Successful.
5. Check the status:
C:\Windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Disabled
Windows RE location:
Boot Configuration Data (BCD) identifier: 00000000-0000-0000-0000-000000000000
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
6. Enable the specified WinRE:
Here's what you'll get if your target partition (with volume labeled R: in this example) is not formatted in NTFS:
R:\>reagentc /enable
REAGENTC.EXE: Windows RE must be installed on a simple volume formatted using NTFS.
That's what you'll get if it is formatted into NTFS:
R:\>reagentc /enable
REAGENTC.EXE: Operation Successful.
7. Check the status:
R:\>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk4\partition1\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: e2b06021-6f56-11e4-82ee-abb7ebf625e8
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
Your Windows setup has just been enabled with WinRE pre-boot recovery environment located on the first partition of your drive:
8. Specify location of OS Image file (the install.wim one copied from Windows Setup DVD):
R:\>reagentc /setosimage /path \\?\Volume{A235FAFF-A690-11E4-95DC-00155D095900}\Recovery /index 1 /target C:\Windows
Directory set to: \\?\GLOBALROOT\device\harddisk4\partition5\Recovery
REAGENTC.EXE: Operation Successful.
9. Check the status:
R:\>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk4\partition1\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: e2b06021-6f56-11e4-82ee-abb7ebf625e8
Recovery image location: \\?\GLOBALROOT\device\harddisk4\partition5\Recovery
Recovery image index: 1
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
Your Windows Recovery Environment is now located on the 1st partition of 4th disk drive and recovery image file the can be used to re-image Windows installation from that WinRE environment is located on the 5th partition of the same 4th disk.
See also
Configuring Windows Recovery Using PowerShell
Proper Configuration of Partition Layout on a GPT Disk under UEFI
Deploy a System Recovery Image
Thank you, Michael for your help!
Well this is the world we live in And these are the hands we're given...
Maybe you are looking for
-
When i open reader two AcroRd32.exe*32 processes open and never close even after exiting the reader.
when i open reader two AcroRd32.exe*32 processes open and do not close after closing the reader. i have seen 10 AcroRd31.exe*32 processes open. do I have an undetectable virus or is the software just poorly written and tested. I am running Windows 7
-
My Apple ID is locked for 90 days and can't even purchase anything
I had my personal Apple ID and I made an second Apple ID for my business. I logged into my iphone6 with that second business apple ID - this apple ID has no credit card information at all. then I tried to log into my personal previous apple ID - this
-
Randomly Missing Text in PDF Created from FrameMaker
This problem relates to a structured FM document, but I suspect it might be a general issue and have posted it here in the general forum for that reason. I am generating PDFs that are missing text somewhat randomly throughout. I tried searching the f
-
Calendar Application System Configuration Assistant failed
Hi I'm a newbit to OCS and have been trying to installl OCS 10.1.2 on Red Hat ES4 on a HP DL385 box - 6 GB and got stuck at the Calendar Application System Configuration Assistant part. Retried it several times, both in Basic or Advanced installation
-
DO I NEED TO INSTALL ADOBE FLASH ON MY NEW MACBOOK PRO.... NOT SO SURE WHAT TO DO. PLEASE HELP