Professional Documents
Culture Documents
16 comentarios:
1.
Paso 8: Pulse ALT + CTRL + SUPR para reiniciar con fuerza el sistema.
Paso 9: Espere a que el sistema para localizar de forma automática y hacer la reparación.
Responder
2.
no me funciono yo tengo ese problema pero al intalar el windows 8 pero cuando ya va inicial
el untimo paso me ocurre ese error 0x0000001 y no me permite aceder al cistema lo que
quiero decir el sistema queda colgado y no arranca intente con intalacion windows 7 pero
me lo tumbo dedes el sistema iniciado nadamas se reinicio y se tumbo el sistema una
solucion q me puedas desir q windows intalo a y otra cosa esta bloquido o mas bien tiene
seguridad gpt el disco rigido o duro eso ya se como sulucionarlo pero tendra algo q ver ????
Responder
3.
4.
5.
6.
buanas noches le dejo esta informacion para el Error Code: 0xc0000001. este error se debe
a problemas con las o la memoria RAM, quiten sus memorias y prueben con otras. espero q
les sea de ayuda
Responder
7.
Solucion: a mi me ocurrio lo mismo varias veces leyendo por alli de varios foros, vi el
comentario de que resetera la BIOS de la PC, lo hice desconecte el cable de corriente y sque
la bateria de la tarjeta madre por unos 15 Segundos. y kluego la inserte conecte el cble de
corriente inicie con el disco e instalo el Sistema Operativo Perfectamente
Responder
Respuestas
1.
Cesar Palacios25 de noviembre de 2015, 21:53
8.
hola, muchachos a mi lo que me paso fue lo siguiente: cuando iva completar la instalacion,
me encontraba con este problema, entonces le di a la opcion 4 la de iniciar en modo seguro,
entonces me dio el mensaje de que Windows no podia completar la instalacion en modo
seguro, asi que reinicié y para mi sorpresa se completo !
Otra cosa que deberian tener en cuenta es que no esten instalando un sistema de 32 bit
sobre un micro de 64bit, quizas eso sea lo genera este lio,
Responder
Respuestas
1.
lakes009 Polo24 de diciembre de 2015, 10:30
por que la gente habla sin entender el de 32 bits es si tienes menos 4gb de ram y el
de 64 bits si tienes mayor que 4gb de ram
no tiene nada que ver con el micro xd
2.
por que la gente habla sin entender el de 32 bits es si tienes menos 4gb de ram y el
de 64 bits si tienes mayor que 4gb de ram
no tiene nada que ver con el micro xd
Responder
9.
10.
Hola como están yo tengoel mismo error y no se que hacer ya hice de todo y nada la pantalla
se quedo iniciando con gettind ready
Responder
11.
Hola como están m pueden ayudar en este problema q tengo. Al tratar de. Instalar windows
10 a través de una USB. M. Sale directo este error status: 0x0000001 y no m. Deja instalar
nada solo. M. Redirige a esa. Ventana windows failed todo estar
Responder
12.
me ocurrio y lo que hice cambiar el boot de legacy a uefy y todo se instalo correctamente
Responder
APC_INDEX_MISMATCH Error de pantalla azul siempre se produce debido al controlador
del sistema incompatible. En general, el error APC_INDEX_MISMATCH ocurre cuando los
principales controladores del sistema, como los gráficos y el audio, se dañan, corrompen o quedan
obsoletos.
Existen varias otras razones disponibles que pueden desencadenar un error de pantalla azul
APC_INDEX_MISMATCH en el sistema Windows 10.
Aquí en este blog, discutiremos sobre cómo deshacerse del error APC_INDEX_MISMATCH
BSoD.
Este error se activa debido a una falta de coincidencia en el “Índice de estado de APC”. Es un
mensaje de error muy complicado que puede aparecer en cualquier sistema Windows 10 que
contenga un controlador mal programado.
Causas de los errores de pantalla azul APC_INDEX_MISMATCH
Antes de aplicar cualquier arreglo a continuación, primero debe iniciar su sistema en modo
seguro. Debido al error de pantalla azul, no puede iniciar su sistema normalmente. Así que visite:
Cómo iniciar Windows 10 en modo seguro y aplicar los pasos dados para iniciar su sistema en
modo seguro.
Lea también: Cómo corregir el código de error 0x7E y autorun.dll está ausente
1. Abra el cuadro de diálogo ejecutar presionando la tecla Windows + tecla R al mismo tiempo.
3. Marque Eliminar el software del controlador para este dispositivo y luego haga clic en
Aceptar.
4. Vuelva a abrir el cuadro de diálogo Ejecutar (Win + R), escriba msconfig y presione la tecla
Entrar.
5. Toque el panel de Inicio y luego desmarque Inicio seguro y haga clic en Aceptar.
Ahora su sistema se reiniciará normalmente e instalará el controlador gráfico automáticamente.
Una vez que alguno de los controladores del sistema se vuelva incompatible, el sistema
comenzará a mostrar los errores BSoD. Por lo tanto, asegúrese de que todos los dispositivos
instalados tengan el último controlador.
4. Este proceso llevará algún tiempo, así que espere un tiempo y podrá observar la descarga e
instalación del controlador.
1. Abra el cuadro de diálogo ejecutar con privilegio de administrador para hacer esto; presione
la tecla de Windows y escriba cmd -> haga clic con el botón derecho en el cmd y haga clic en
Ejecutar como administrador
2. Ahora, debe escribir sfc / scannow en la ventana del símbolo del sistema y presionar la tecla
Enter para ejecutar este comando
1. Abra el símbolo del sistema con privilegio de administrador. Presione la tecla de Windows y
escriba cmd -> haga clic con el botón derecho en el cmd y haga clic en Ejecutar como
administrador. Si aparece algún mensaje de UAC, debe hacer clic en Sí.
2. Ahora escriba chkdsk / f en el símbolo del sistema y presione la tecla Enter.
3. Este comando escaneará su disco duro en busca de cualquier tipo de daño que pueda ser la
causa del APC_INDEX_MISMATCH con problema de BSOD.
Después de completar este comando, es posible que deba reiniciar la PC con Windows 10.
Solución automática
Después de corregir el error APC_INDEX_MISMATCH, se sugiere escanear su sistema con
un escáner profesional de errores de PC. Esto es necesario para evitar y corregir todos los
demás errores del sistema que son imposibles de corregir manualmente.
No necesita experiencia profesional para operar esta herramienta, ya que es muy simple de
instalar y aplicar.
mekklos - 21 feb 2014 a las 23:50 - Última respuesta: Paxel - 18 mar 2014 a
las 09:17
Hola, alguien me pueda ayudar tengo un problema con me potable hp650 es qué me salí
error0xc0000001 ygracias.
Error 0xc0000001
0xc0000001 - Mejores respuestas
Ayuda, error:0xc0000001 en windows 8 - Foros - Windows 8
No me arranca codigo de error 0xc0000001 - Foros - Windows 10
Error 0xc00007b - Fichas prácticas - Windows
Error 204 atube catcher ✓ - Foros - Software
Error 8002a537 ps3 - Fichas prácticas - PS3
3 respuestas
Comenta la respuesta de mekklos
mekklos8 mar 2014 a las 14:01
-1
Gracias
gracias paxel muy agradecido ya esta arreglado pero por un colega que es un genio
Comenta la respuesta de Paxel
Gracias
de nada Suerte!!
Denunciar Comenta la respuesta de Paxel
-4
Gracias
Parece ser un problema con el archivo del sistema operativo que se podría haber dañado a
causa de falta de energía eléctrica. Usted puede seguir los pasos a continuación e intentar la
reparación del sistema operativo.
Apague la computadora
Reinicie el sistema. En la pantalla de logotipo del sistema inmediatamente presione y sostenga
'SHIFT' y pulse la tecla "F8" para entrar en 'recuperación' y seleccione 'Ver opción de
reparación avanzada ".
Ahora, al 'inicio de Windows Setting' click 'Reiniciar' y permitir que su sistema termine con el
proceso. Lo hará la reparación sin hacer ningún cambio a sus carpetas importantes.
Qué necesitamos
Con Rufus podemos copiar fácilmente una ISO de Windows 10, tan
solo necesitamos una memoria USB que tenga una capacidad de 8 GB
(recomendable). En muy pocos pasos tendremos nuestro USB de
arranque con el sistema operativo de Microsoft.
Solo tienen que estar marcadas las siguientes casillas: formateo rápido,
crear disco de arranque y añadir etiquetas extendidas e iconos. El
siguiente paso es pulsar el botón Empezar. El proceso llevará unos
minutos, dependiendo de la velocidad de la memoria USB.
Una vez finalice la copia solo tenemos que reiniciar nuestro equipo y
hacer que arranque desde la memoria USB. Muchos ordenadores lo
hacen de forma automática, en otros hay que pulsar cierta tecla para
elegir el dispositivo de arranque justo al encender el PC.
COMPARTIR0 TWITTEAR
¿Os acordáis de esos tiempos dónde la disquetera de tu PC era tu mejor amigo? Sí, en aquella
época las cosas eran un poco más limitadas que ahora, y cualquiera de nosotros debía sacarse
un poco las castañas del fuego a la hora de trastear más de lo debido. Los CDs y DVDs eran el
novamás, y el USB lo revolucionó todo.
Y ya si nos ponemos nostálgicos, seguro que recordaréis cuando había que reformatear nuestro
ordenador y recurríamos al informático de la calle vecina, o a nuestros CD con un sistema
operativo para poder reinstalar todo lo que teníamos. Eso, con el USB se acabó. Con su llegada,
se nos abrió un mundo de posibilidades y solucionó muchos problemas logísticos, sobre todo
con los pequeños y ya difuntos notebooks que no tenían compatibilidad para PC y un virus
nos hacía la tarde.
Pero ahora, con un lápiz de memoria USB, maña, y paciencia –sobre todo a la hora de descargar
los archivos– podemos tener cualquier sistema operativo listo para su instalación en nuestro
bolsillo y disponible para emergencias. Y aunque hay miles de herramientas disponibles, os
hablaré de una que destaca –para mi gusto– por su sencillez y versatilidad: Universal USB
Installer.
¡Pincha aquí, quizás te interese!: Trabaja de forma sencilla con archivos de formato .iso
1. Tras descargar la herramienta aquí ejecutamos el archivo .exe, y se abrirá una interfaz,
sin ningún tipo de instalación.
3. Elegimos el directorio donde tengamos guardado ISO para instalar. Cabe destacar que,
al ser un programa dedicado a particiones Linux, podemos seleccionar el servidor de
descarga y el gestor se ocupará de absolutamente todo.
Sin duda es una herramienta muy útil y sencilla para poder solucionar de raíz cualquier problema
relacionado con nuestros sistemas operativos. Es de destacar la gran variedad de sistemas que
nos da a elegir este programa, puesto que incluso podemos instalar ISOs de Windows, desde
7 hasta 10. Y por supuesto descargar un ISO de Windows 10 puede ser incluso más fácil.
Quién sabe qué nos depara el futuro de la tecnología. Yo, personalmente, confío en que si las
cosas son así de sencillas ahora, nos augura un futuro brillante. ¿No creéis?
¿Conocías esta herramienta? ¿La has usado alguna vez? ¡Exprésate en la caja de comentarios!
l realizar este proceso tu usb queda preparada para bootear windows 7, windows 8,
windows 8.1 o Windows 10 solo hay que borrar los datos que hay en la memoria y luego
copiar los de la imagen iso que quieras instalar. 1. Conecte la unidad flash USB al
ordenador, por supuesto. 2. Abra Símbolo del sistema con derechos de administrador.
3. Escriba "diskpart" (sin comillas) para iniciar la utilidad incorporada diskpart. Y
escribe "list disk" (sin Comillas) y observa en el numero de disco para la unidad USB. 4.
Escriba los siguientes comandos para formatear correctamente la unidad flash.
Reemplace # con el actual # que tienes desde el paso 3 anterior. select disk # clean
create partition primary format fs=fat32 quick active assign exit 5. Ahora cierre la
ventana del símbolo del sistema y abra el Explorador de archivos, busque donde se
encuentra guardado el archivo de imagen ISO de instalación de Windows 8, 8.1 o 10 6.
Monte el archivo ISO haciendo clic derecho en el archivo ISO y seleccionando montar;
O montar con otros programas especializados. 7. Seleccionar todo en el archivo ISO, y
copiarlos en la unidad USB formateada anteriormente 8. Tendrá que copiar un archivo
llamado BOOTX64.EFI (el link de descarga esta a continuación) a la carpeta efi \ boot en
una unidad USB BOOTX64.EFI https://mega.nz/#!Nlh1mTia!nsLAuDj3IW... Y por si no lo
tienes W 8.1 pro x64 https://mega.co.nz/#F!lp5QzKSQ!kYjVaH... Acerca de UEFI
bcd-estado-error-0xc000000f"
title="\Boot\ bcd Estado: error 0xc000000f"
itemprop="name">\Boot\ bcd Estado: error
0xc000000f
Preguntado el 5 de Agosto, 2013
90245 visitas
5 Respuestas
abierta
Windows failed to start. A recent hardware of software change might be the cause
. To fix the problem
1. Insert your Windows installation disc and restart the computer.
2. Choose your language settings, and then click "Next".
3. Click "Repair your computer."
If you do not have this disc, contact your system administrator or computer manu
facturer for assistance.
File: \Boot\bcd
Status: 0x000000f
He buscado en google sobre el error, y el mensaje parece que necesito para arrancar mi
ordenador portátil desde el disco de instalación de Windows.
Mi laptop tiene Windows 7 Professional SP1 x86 instalado, pero cuando intento insertar
Windows 7 Professional x86 me sale el mismo error. ¿Necesito un SP1 disco? Hice la
instalación de la unidad CD/DVD como primero en el orden de arranque, pero yo todavía
tengo el mismo error.
También, ¿qué otras opciones debo intentar llegar a la de Windows 7 Sistema de Reparación
de la Pantalla, de modo que yo pueda reparar o reconstruir el archivo bcd?
Respuestas
¿Demasiados anuncios?
6
SamBCPuntos 13
Parece que tu Windows 7 disco se rompió y usted debe tratar de crear una nueva.
Crear un USB de arranque
Si usted tiene una buena conexión a internet, entonces usted puede descargar su
versión windows 7 aquí (usted todavía necesita un legit clave, por supuesto).
A continuación, puede utilizar Microsoft propia herramienta para hacer un disco de
arranque de windows 7 USB.
Cuando esté hecho, usted debe tener un trabajo de arranque de Windows 7 USB
Los mismos pasos que se utilizan para la creación de un DVD, sólo tienes que
seleccionar el DVD en lugar de en el dispositivo USB.
bcd Reparación
Windows ya tiene una herramienta para este propósito, llamado BCDboot.
cpintoPuntos 51
Tuve este mismo problema e hice lo que la mayoría de la gente que era de google
para una respuesta y esperar lo mejor. El win 7 instalar el disco tiene una reparación
de computadoras opción que permite a algunos automático de error de inicio de las
revisiones a ser implementado. A veces esto funciona, pero esta vez no lo hizo. bcd-
0xc000000f-windows-7/" rel="nofollow" target="_blank">Pensar como un equipo que
tenía un blog post que terminó siendo la gracia salvadora.
Pero para hacer corta una historia larga, aquí es lo que yo hice después de que me
dieron el 'windows no pudo iniciar el' error:
1. de arranque de win 7 DVD o una memoria usb, preferiblemente con la misma
versión y el tipo de windows que tenemos en el objetivo de la unidad de
arranque. Para memoria usb, utilice el puerto usb 2.0 (3.0 puede causar
errores inesperados)
2. Después de elegir el idioma, seleccione "Reparar el equipo' (no instale win7!)
3. Seleccione " utilizar las herramientas de recuperación que puede ayudar a
arreglar los problemas de inicio de Windows...'
4. Selecciona " Símbolo del sistema (CMD) para iniciar CMD con privilegios de
administrador.
5. tipo "diskpart" (sin las comillas) y pulse enter para abrir utilidad DISKPART:
o en la lista "tipo de disco" para obtener una lista de los discos físicos
instalados. Identificar qué disco ha partición de arranque de windows.
o tipo select disk 0 , donde 0 = disco # con Win7 partición de arranque
o tipo list partition. Win 7 tiene un 100 o 200MB de arranque tamaño
de la partición y primaria.
o tipo " select partition 1` where 1 = partición de arranque #
o tipo detail partition y comprobar para ver si la partición está activa. Si
se activa, vaya al siguiente paso.
para hacer de arranque de la partición activa, escriba active y
cuando CMD informes de la partición está activa, reinicie el
equipo en la recuperación/modo de reparación (win7 disco de
instalación de nuevo) y volver a la consola CMD.
o tipo exit para salir de la utilidad DISKPART
6. tipo c: para llegar a la partición de arranque de la unidad de la carpeta root.
(c: es la letra de unidad de la partición de arranque
Mi copia de win7 era más reciente (2014) y había una opción adicional para las
herramientas de recuperación que incluye el explorador de windows. Yo que además
de la consola CMD para ver que la partición tiene carpeta de instalación de windows.
Esta reparación truco también puede funcionar para win 8 y/o win2k8/2012 ediciones
de servidor. Lo que no funcionó: Tratando el uso bcdedit para reparar o reconstruir el
archivo bootloader. Me 'elemento no encontrado errores. También, cambiar el orden
de arranque de los discos en la bios no hacer nada.
liorlevi1974Puntos 11
1. inicio de DOK
2. diskpart
3. lista de discos
4. select disk 0
5. lista de particiones, para verificar todas las particiones están ahí
6. seleccione la parte 1, este es el 100m de la partición de arranque
7. detalle de la partición, para obtener la partición Ltr (en mi caso es c:) y para
comprobar que está activo
8. salir, salir de diskpart
ahora después de saber la partición de windows y la partición de arranque de cartas
que puede usar bcdboot a la revisión de la partición de arranque. este comando copia
los archivos de arranque necesario para el proceso de arranque de la partición de
windows a la partición de arranque.
1. bcdboot d:\windows /s c:
2. ahora puedo reiniciar y proceso de inicio de trabajo
Buena suerte
TheFoOLPuntos 23
Antes de hacer todo esto, revisa tu bios. En mi situación, mi matrices RAID cambiado
debido a la formación de una nueva matriz enel volumen del sistema. La orden de
inicio se ha cambiado y por lo tanto windows no puede cargar. Después de actualizar
el bios, windows se inicia sin problemas.
Ray MassPuntos 1
O usted puede hacer lo que yo hice, he usado mini windows para buscar c:\boot y
eliminados "bcd", el archivo que yo recuerde fue de 32 kb. reiniciar y ... aquí estamos
con un sistema de trabajo.
Fuente: https://www.enmimaquinafunciona.com/pregunta/69592/boot-bcd-estado-error-
0xc000000f
Quita la cubierta del Compartimiento del Disco duro y asegúrate que esté bien
conectado.
Ubicación de archivos
En Windows y en el %WINDIR%\System32\BCDBoot.exe
Entorno de preinstalación
de Windows (WinPE)
BCDBoot puede copiar archivos del entorno de arranque desde imágenes de Windows 10,
Windows 8.1, Windows 8, Windows 7, Windows Vista, Windows Server 2016 Technical Preview,
Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 R2 o
Windows Server 2008.
Funcionamiento
Para configurar la partición del sistema, BCDBoot copia un conjunto pequeño de archivos del
entorno de arranque de la imagen de Windows instalada en la partición del sistema.
BCDBoot puede crear un almacén de datos de la configuración de arranque (BCD) en la
partición del sistema con la versión más reciente de los archivos de Windows:
BCDBoot crea un almacén de BCD nuevo e inicializa los archivos del entorno de arranque de
BCD en la partición del sistema, incluido el Administración de arranque de Windows, mediante
el archivo %WINDIR%\System32\Config\BCD-Template.
Novedad en Windows 10: durante una actualización, BCDBoot conserva las demás entradas de
arranque de existentes, como debugsettings, al crear el almacén nuevo. Usa la opción /c para
omitir la configuración anterior y empezar de cero con un nuevo almacén de BCD.
Si ya existe una nueva entrada de arranque para esta partición de Windows, de forma
predeterminada, BCDBoot borra la entrada de arranque anterior y sus valores. Usa la
opción /m para conservar los valores de una entrada de arranque existente al actualizar los
archivos del sistema.
De manera predeterminada, BCDBoot mueve la entrada de arranque de la partición de
Windows seleccionada a la parte superior del orden de arranque del Administrador de
arranque de Windows. Usa la opción /d para conservar el orden de arranque existente.
En equipos con UEFI, BCDBoot puede actualizar las entradas de firmware de NVRAM del
dispositivo:
Opción Descripción
Si la partición del sistema se ha dañado, puedes usar BCDBoot para volver a crear los archivos
de la partición del sistema usando las copias nuevas de estos archivos en la partición de
Windows.
1. Arrancar tu PC en una línea de comandos. Por ejemplo, arranca en el disco de instalación de
Windows y presiona Mayús+F10 o arranca en Windows PE (WinPE: crear unidad USB de
arranque).
2. Usa Diskpart para determinar qué letra de unidad contiene tu partición de Windows y la
partición del sistema (diskpart, list vol, exit).
3. (Opcional) Formatear la partición del sistema: format (drive letter of your system
partition) /q
4. Agrega una entrada de arranque para la partición de Windows:bcdboot D:\Windows.
5. Reinicia el equipo. Windows debería aparecer.
Configurar o reparar el menú de arranque en un equipo de arranque dual
Cuando se configura un equipo para que arranque en más de un sistema operativo, a veces
puedes perder la capacidad de arrancar en uno de los sistemas operativos. La opción BCDBoot
te permite agregar rápidamente opciones de arranque para un sistema operativo Windows.
Para configurar un equipo con arranque dual:
1. Instala una unidad de disco duro diferente o prepara una partición diferente para cada sistema
operativo.
2. Instala los sistemas operativos. Por ejemplo, si el equipo tiene Windows 7, instala Windows 10
en la otra unidad de disco duro o partición.
3. Reinicia el equipo. Los menús de arranque deben mostrar ambos sistemas operativos.
Si no aparecen ambos sistemas operativos:
a. Abre una línea de comandos, ya sea como administrador desde dentro de Windows o
arrancando en una línea de comandos con los medios de instalación de Windows y
presionando Mayús+F10, o arrancando en Windows PE (WinPE: crear unidad USB de
arranque).
b. Agregar opciones de arranque para un sistema operativo Windows.
c. bcdboot D:\Windows
d. Reinicia el equipo. Ahora, el menú de arranque mostrará ambas opciones de menú.
Solución de problemas
Para información sobre cómo reparar los archivos de arranque en un equipo con Windows XP y
una versión más reciente de Windows, como Windows 7, consulta el artículo de la Knowledge
Base de Microsoft 2277998.
Temas relacionados
BCDedit
DiskPart Commands
06/17/2014
2 minutes to read
Applies To: Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows
Vista
DiskPart commands help you to manage your PC's drives (disks, partitions,
volumes, or virtual hard disks). Before you can use DiskPart commands, you must
first list, and then select an object to give it focus. When an object has focus, any
DiskPart commands that you type will act on that object.
You can list the available objects and determine an object's number or drive letter
by using the list disk, list volume, list partition, and list vdisk commands. The list
disk, list vdisk and list volumecommands display all disks and volumes on the
computer. However, the list partition command only displays partitions on the
disk that has focus. When you use the list commands, an asterisk (*) appears next
to the object with focus.
When you select an object, the focus remains on that object until you select a
different object. For example, if the focus is set on disk 0 and you select volume 8
on disk 2, the focus shifts from disk 0 to disk 2, volume 8. Some commands
automatically change the focus. For example, when you create a new partition, the
focus automatically switches to the new partition.
You can only give focus to a partition on the selected disk. When a partition has
focus, the related volume (if any) also has focus. When a volume has focus, the
related disk and partition also have focus if the volume maps to a single specific
partition. If this is not the case, focus on the disk and partition is lost.
DiskPart commands
diskpart
Important
You can run the following commands in the Diskpart command interpreter:
Active
Add
Assign
Attach vdisk
Attributes
Automount
Break
Clean
Compact vdisk
Convert
Create
Delete
Detach vdisk
Detail
Exit
Expand vdisk
Extend
Filesystems
Format
GPT
Help
Import
Inactive
List
Merge vdisk
Offline
Online
Recover
Rem
Remove
Repair
Rescan
Retain
San
Select
Set id
Shrink
Uniqueid
Additional references
Chkdsk
04/17/2012
6 minutes to read
Checks the file system and file system metadata of a volume for logical and
physical errors. If used without parameters, chkdsk displays only the status of the
volume and does not fix any errors. If used with the /f, /r, /x, or /b parameters, it
fixes errors on the volume.
Important
<Volume> Specifies the drive letter (followed by a colon), mount point, or volume name.
[<Path>]<FileName> Use with file allocation table (FAT) and FAT32 only. Specifies the location
and name of a file or set of files that you want chkdsk to check for
fragmentation. You can use the ? and *wildcard characters to specify multiple
files.
/f Fixes errors on the disk. The disk must be locked. If chkdsk cannot lock the
drive, a message appears that asks you if you want to check the drive the next
time you restart the computer.
/v Displays the name of each file in every directory as the disk is checked.
/r Locates bad sectors and recovers readable information. The disk must be
locked. /r includes the functionality of /f, with the additional analysis of
physical disk errors.
/x Forces the volume to dismount first, if necessary. All open handles to the drive
are invalidated. /x also includes the functionality of /f.
/i Use with NTFS only. Performs a less vigorous check of index entries, which
reduces the amount of time required to run chkdsk.
/c Use with NTFS only. Does not check cycles within the folder structure, which
reduces the amount of time required to run chkdsk.
/l[:<Size>] Use with NTFS only. Changes the log file size to the size you type. If you
omit the size parameter, /l displays the current size.
/b NTFS only: Clears the list of bad clusters on the volume and rescans all
allocated and free clusters for errors. /b includes the functionality of /r. Use
this parameter after imaging a volume to a new hard disk drive.
Parameter Description
Remarks
If you want chkdsk to correct disk errors, you cannot have open files on the
drive. If files are open, the following error message appears:
Copy
If you choose to check the drive the next time you restart the
computer, chkdsk checks the drive and corrects errors automatically when
you restart the computer. If the drive partition is a boot
partition, chkdsk automatically restarts the computer after it checks the drive.
You can also use the chkntfs /c command to schedule the volume to be
checked the next time the computer is restarted. Use the fsutil dirty
set command to set the volume's dirty bit (indicating corruption), so that
Windows runs chkdsk when the computer is restarted.
You should use chkdsk occasionally on FAT and NTFS file systems to check
for disk errors. Chkdsk examines disk space and disk use and provides a
status report specific to each file system. The status report shows errors found
in the file system. If you run chkdsk without the /f parameter on an active
partition, it might report spurious errors because it cannot lock the drive.
Because repairs on FAT file systems usually change a disk's file allocation table
and sometimes cause a loss of data, chkdsk might display a confirmation
message similar to the following:
Copy
If you press Y, Windows saves each lost chain in the root directory as a file
with a name in the format File<nnnn>.chk. When chkdsk finishes, you can
check these files to see if they contain any data you need. If you press N,
Windows fixes the disk, but it does not save the contents of the lost allocation
units.
If you do not use the /f parameter, chkdsk displays a message that the file
needs to be fixed, but it does not fix any errors.
If you use chkdsk /f on a very large disk or a disk with a very large number of
files (for example, millions of files), chkdsk /f might take a long time to
complete.
Use the /r parameter to find physical disk errors in the file system and
attempt to recover data from any affected disk sectors.
If you specify the /f parameter, chkdsk displays an error message if there are
open files on the disk. If you do not specify the /f parameter and open files
exist, chkdsk might report lost allocation units on the disk. This could happen
if open files have not yet been recorded in the file allocation table.
If chkdsk reports the loss of a large number of allocation units, consider
repairing the disk.
The following table lists the exit codes that chkdsk reports after it has
finished.
Exit
code Description
2 Performed disk cleanup (such as garbage collection) or did not perform cleanup
because /fwas not specified.
3 Could not check the disk, errors could not be fixed, or errors were not fixed
because /f was not specified.
If you want to check the disk in drive D and have Windows fix errors, type:
Copy
chkdsk d: /f
chkdsk *.*
Chkdsk displays a status report, and then lists the files that match the file
specifications that have noncontiguous blocks.
Additional references
Sfc
04/17/2012
2 minutes to read
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2008
R2 with SP1, Windows Vista
Scans and verifies the integrity of all protected system files and replaces incorrect
versions with correct versions.
/scannow Scans the integrity of all protected system files and repairs files with problems when
possible.
/verifyonly Scans integrity of all protected system files. No repair operation is performed.
/scanfile Scans integrity of the specified file and repairs the file if problems are detected, when
possible.
Parameter Description
/verifyfile Verifies the integrity of the specified file. No repair operation is performed.
/offwindir Specifies the location of the offline windows directory, for offline repair.
/offbootdir Specifies the location of the offline boot directory for offline
Remarks
sfc /verifyfile=c:\windows\system32\kernel32.dll
To setup offline repair of the kernel32.dll file with an offline boot directory set
to d: and offline windows directory set to d:\windows, type:
Copy
Shutdown
04/17/2012
3 minutes to read
Applies To: Windows Server 2000, Windows Server 2003, Windows Server 2003 R2,
Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server
2008, Windows Server 2008 R2, Windows Vista
Enables you to shut down or restart local or remote computers one at a time.
/i Displays the Remote Shutdown Dialog box. The /i option must be the first
parameter following the command. If /i is specified, all other options are
ignored.
/l Logs off the current user immediately, with no time-out period. You cannot
use /lwith /m or /t.
/a Aborts a system shutdown. Effective only during the timeout period. To use /a,
you must also use the /m option.
/p Turns off the local computer only (not a remote computer)—with no time-out
period or warning. You can use /p only with /d or /f. If your computer does not
support power-off functionality, it will shut down when you use /p, but the
power to the computer will remain on.
/h Puts the local computer into hibernation, if hibernation is enabled. You can
use /honly with /f.
Parameter Description
/e Enables you to document the reason for the unexpected shutdown on the target
computer.
Caution
/t <XXX> Sets the time-out period or delay to XXX seconds before a restart or shutdown.
This causes a warning to display on the local console. You can specify 0-600
seconds. If you do not use /t, the time-out period is 30 seconds by default.
/d Lists the reason for the system restart or shutdown. The following are the
[p|u:]<XX>:<YY> parameter values:
XX Specifies the major reason number (positive integer less than 256).
YY Specifies the minor reason number (positive integer less than 65536).
/c "<Comment>" Enables you to comment in detail about the reason for the shutdown. You must
first provide a reason by using the /d option. You must enclose comments in
quotation marks. You can use a maximum of 511 characters.
/? Displays help at the command prompt, including a list of the major and minor
reasons that are defined on your local computer.
Remarks
Users must be assigned the Shut down the system user right to shut down a
local or remotely administered computer that is using
the shutdown command.
Users must be members of the Administrators group to annotate an
unexpected shutdown of a local or remotely administered computer. If the
target computer is joined to a domain, members of the Domain Admins
group might be able to perform this procedure. For more information, see:
o Default local groups
o Default groups.
If you want to shut down more than one computer at a time, you can
call shutdown for each computer by using a script, or you can
use shutdown/i to display the Remote Shutdown Dialog box.
If you specify major and minor reason codes, you must first define these
reason codes on each computer where you plan to use the reasons. If the
reason codes are not defined on the target computer, Shutdown Event
Tracker cannot log the correct reason text.
Remember to indicate that a shutdown is planned by using the p: parameter.
Omitting p:indicates that a shutdown is unplanned. If you type p: followed by
the reason code for an unplanned shutdown, the command will not carry out
the shutdown. Conversely, if you omit p:and type in the reason code for a
planned shutdown, the command will not carry out the shutdown.
Examples
To force applications to close and restart the local computer after a one-minute
delay with the reason "Application: Maintenance (Planned)" and the comment
"Reconfiguring myapp.exe" type:
Copy
To restart the remote computer \\ServerName with the same parameters, type:
Copy
Bcdboot
04/17/2012
2 minutes to read
Updated: April 17, 2012
Enables you to quickly set up a system partition, or to repair the boot environment
located on the system partition. The system partition is set up by copying a simple
set of Boot Configuration Data (BCD) files to an existing empty partition.
source Specifies the location of the Windows directory to use as the source for copying boot
environment files.
/s Specifies the volume letter of the system partition. The default is the system partition
identified by the firmware.
Bcdboot
04/17/2012
2 minutes to read
Enables you to quickly set up a system partition, or to repair the boot environment
located on the system partition. The system partition is set up by copying a simple
set of Boot Configuration Data (BCD) files to an existing empty partition.
For more information about BCDboot, including information on where to find
BCDboot and examples of how to use this command, see the BCDBoot Command-
Line Options topic.
Syntax
Copy
source Specifies the location of the Windows directory to use as the source for copying boot
environment files.
/s Specifies the volume letter of the system partition. The default is the system partition
identified by the firmware.
Nota:
1. Este metodo es valido solo para Windows 8/8.1 y algunos datos se pueden
perder.
2. Si no ha resuelto el problema de arranque,por favor contacte con el
Soporte Tecnico de ASUS.
Problema de arranque
Windows 8 - Introduccion de
herramienta de reparacion
WinPE
Última actualización : 2015/06/16 19:06
SENT TO YOUR EMAIL ABRIR EN SU TELÉFONO INTELIGENTE
Nota :
a. Este metodo es valido solo para Windows 8/8.1 y algunos datos se pueden
perder.
b. Si no ha resuelto el problema de arranque,por favor contacte con el
Soporte Tecnico de ASUS.
Nota : Los passos indicados a continuacion sera para formatear el USB drive.
9. Digitar "MakeWinPEMedia /UFD C:\WinPE_amd64 E:" a continuación,
pulse la tecla Enter.
* La letra marcada en amarillo debera corresponder a la letra asignada al
drive USB.
10. Haga click en "Y" para hacer la instalacion .
11. Cuando la herramienta de reparacion WinPE este instalada en el USB
drive, podrá seguir los pasos indicados a continuacion para reparar el
sistema.
Problema de arranque Windows 8 - Como utilizar el comando
CHKDSK en WinPE?
Problema de arranque Windows 8 - Como utilizar el comando
BCDBOOT en WinPE?
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
(WinPE) Windows PE 5.0 (WinPE) is a small operating system used to install, deploy,
and repair Windows 8, Windows Server 2012 R2, and other Windows operating
systems. From Windows PE, you can:
To get Windows PE, use the installer built into the Windows Assessment and
Deployment Kit (Windows ADK). For more info, see WinPE: Create USB Bootable
drive, WinPE: Create a Boot CD, DVD, ISO, or VHD, or see the Demo: Installing
Windows PE on a USB Drive.
Support for many Windows features
Windows PE runs the Windows command line environment, and supports these
Windows features:
Batch files and scripts, including support for Windows Script Host (WSH),
and ActiveX Data Objects (ADO), and optional support for PowerShell.
Applications, including Win32 application programming interfaces (APIs) and
optional support for HTML Applications (HTA).
Drivers, including a generic set of drivers that can run networking, graphics,
and mass storage devices.
Image capturing and servicing, including Deployment Image Servicing and
Management (DISM).
Networking, including connecting to file servers using TCP/IP and NetBIOS
over TCP/IP via LAN.
Storage, including NTFS, DiskPart, and BCDBoot.
Security tools, including optional support for BitLocker and the Trusted
Platform Module (TPM), Secure Boot, and other tools.
Hyper-V, including VHD files, mouse integration, mass storage and network
drivers that allow Windows PE to run in a hypervisor.
Hardware requirements
No hard drive is required. You can run Windows PE entirely from memory.
The base version requires only 512MB of memory. (If you add drivers,
packages, or apps, you'll need more memory.)
The 32-bit version of Windows PE can boot 32-bit UEFI and BIOS PCs, and 64-bit
BIOS PCs.
The 64-bit version of Windows PE can boot 64-bit UEFI and BIOS PCs.
Limitations
Windows PE is not a general-purpose operating system. It may not be used for any
purpose other than deployment and recovery. It should not be used as a thin client
or an embedded operating system. There are other Microsoft products, such as
Windows Embedded CE, which may be used for these purposes.
When Windows PE reboots, all changes are lost, including changes to drivers, drive
letters, and the Windows PE registry. To make lasting changes, see WinPE: Mount
and Customize.
You can use the 32-bit versions of Windows PE and Windows Setup to install
64-bit versions of Windows. For more information, see Windows Setup
Supported Platforms and Cross-Platform Deployments.
Although Windows PE supports dynamic disks, Windows Setup does not. If
you install Windows to a dynamic disk created in Windows PE, the dynamic
disks won't be available in Windows.
For UEFI-based PCs that support both UEFI and legacy BIOS modes, Windows
PE needs to be booted in the correct mode in order to correctly install
Windows. For more info, see WinPE: Boot in UEFI or legacy BIOS mode.
See also
Content type References
Deployment WinPE: Create USB Bootable drive | Demo: Installing Windows PE on a USB
Drive | WinPE: Create a Boot CD, DVD, ISO, or VHD | WinPE: Install on a
Hard Drive (Flat Boot or Non-RAM) | WinPE: Boot in UEFI or legacy BIOS
mode | Boot to UEFI Mode or Legacy BIOS mode
Operations WinPE: Mount and Customize | WinPE: Storage Area Network (SAN)
Policy | WinPE: Create Apps
Troubleshooting WinPE Network Drivers: Initializing and adding drivers | WinPE: Debug
Apps |
Technologies based Windows Setup | Windows Recovery Environment | Diagnostic and Recovery
on Windows PE Toolset
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
When you boot Windows PE on a UEFI PC, you may need to check whether the PC
is booted in UEFI mode or legacy BIOS-compatibility mode.
For many operations, such as applying Windows images using Diskpart and DISM,
the firmware mode might not make a difference.
Boot to UEFI mode
1. When booting the PC, you may need to manually select the UEFI boot files:
\EFI\BOOT\BOOTX64.EFI.
a. Boot your PC and press the key to get into the firmware menus
(examples: Esc, F2, F9, F12).
b. Look for a firmware option to choose the boot file (examples: Boot to
file, Boot to EFI file).
c. Select the file from the USB drive: \EFI\BOOT\BOOTX64.EFI.
Detect whether Windows PE is booted in BIOS or UEFI mode
Check
the HKLM\System\CurrentControlSet\Control\PEFirmwareType registry
value to see if the PC is booted to UEFI or BIOS mode. Note: you may need to
run wpeutil UpdateBootInfo to make sure this value is present.
Copy
This command returns 0x1 if the PC is booted into BIOS mode, or 0x2 if the
PC is booted in UEFI mode.
Sample script:
Copy
wpeutil UpdateBootInfo
for /f "tokens=2* delims= " %%A in ('reg query
HKLM\System\CurrentControlSet\Control /v PEFirmwareType') DO SET
Firmware=%%B
:: Note: delims is a TAB followed by a space.
if %Firmware%==0x1 echo The PC is booted in BIOS mode.
if %Firmware%==0x2 echo The PC is booted in UEFI mode.
If this is a frequent problem, you can remove the boot files for UEFI mode or
BIOS mode to prevent the PC from booting in the wrong mode. If the PC
firmware is set up to boot in the wrong mode, the media will immediately fail
to boot, allowing you to immediately retry booting the PC into the correct
mode.
o Boot in UEFI mode: To prevent Windows PE from booting in BIOS mode,
remove the bootmgr file on the root of the media.
o Boot in BIOS mode: To prevent Windows PE from booting in UEFI mode,
remove the efifolder on the root of the media.
When installing Windows on UEFI-based PCs using Windows Setup, your hard drive
partition style must be set up to support either UEFI mode or legacy BIOS-
compatibility mode.
For example, if you receive the error message: “Windows cannot be installed to this
disk. The selected disk is not of the GPT partition style”, it’s because your PC is
booted in UEFI mode, but your hard drive is not configured for UEFI mode. You’ve
got a few options:
1. Reboot the PC in legacy BIOS-compatibility mode. This option lets you keep
the existing partition style. For more info, see Boot to UEFI Mode or Legacy
BIOS mode.
2. Reformat the drive for UEFI by using the GPT partition style. This option lets
you use the PC’s UEFI firmware features.
You can do this yourself by reformatting the drive using the instructions
below, or if you need to preserve the data, use a third-party utility to convert
the drive to GPT format.
Why should I convert my drive?
Many PCs now include the ability to use the UEFI version of BIOS, which can speed
up boot and shutdown times and can provide additional security advantages. To
boot your PC in UEFI mode, you'll need to use a drive formatted using the GPT
drive format.
Many PCs are ready to use UEFI, but include a compatibility support module (CSM)
that is set up to use the legacy version of BIOS. This version of BIOS was developed
in the 1970s and provides compatibility to a variety of older equipment and
network configurations, and requires a drive that uses the MBR drive format.
However, the basic MBR drive format does not support drives over 4TB. It's also
difficult to set up more than four partitions. The GPT drive format lets you set up
drives that are larger than 4 terabytes (TB), and lets you easily set up as many
partitions as you need.
Reformatting the drive using a different partition style
To wipe and convert the drive by using Windows Setup
1. Turn off the PC, and put in the Windows installation DVD or USB key.
2. Boot the PC to the DVD or USB key in UEFI mode. For more info, see Boot to
UEFI Mode or Legacy BIOS mode.
3. When choosing an installation type, select Custom.
4. On the Where do you want to install Windows? screen, select each of the
partitions on the drive, and select Delete. The drive will show a single area of
unallocated space.
5. Select the unallocated space and click Next. Windows detects that the PC was
booted into UEFI mode, and reformats the drive using the GPT drive format,
and begins the installation.
To manually wipe a drive and convert it to GPT:
1. Turn off the PC, and put in the Windows installation DVD or USB key.
2. Boot the PC to the DVD or USB key in UEFI mode. For more info, see Boot to
UEFI Mode or Legacy BIOS mode.
3. From inside Windows Setup, press Shift+F10 to open a command prompt
window.
4. Open the diskpart tool:
Copy
diskpart
Copy
list disk
Copy
When choosing an installation type, select Custom. The drive will appear as a
single area of unallocated space.
Select the unallocated space and click Next. Windows begins the installation.
Make sure Windows Setup boots to the correct firmware mode
To automate this process, you'll need to run Windows Setup through Windows PE,
and use a script to detect which mode you’re in before installing Windows. For
more info, see WinPE: Boot in UEFI or legacy BIOS mode.
See Also
To prepare to deploy a Windows® image to a new PC, you can create partitions by
using a DiskPartscript. This topic provides examples of how to configure disk
partitions for a PC that is based on Unified Extensible Firmware Interface (UEFI)
firmware and whose disks use a GUID partition table (GPT). This topic covers the
following partition configurations:
After you create the partitions, you can apply the Windows images on the newly
created partitions.
In this topic:
Windows PE reassigns disk letters alphabetically, starting with the letter C, without
regard to the configuration in Windows Setup. This configuration can change
based on the presence of different drives, including USB flash drives.
In these DiskPart examples, the partitions are assigned the letters T, S, W, and R to
avoid drive-letter conflicts. After the PC reboots, Windows PE automatically assigns
the letter C to the Windows partition. The system partition, the Windows RE tools
partition, and the recovery image partition do not receive drive letters.
The following steps describe how to partition your hard drives and prepare to
apply images. You can use the code in the sections that follow to complete these
steps.
To partition hard drives and prepare to apply images
Save the following code as CreatePartitions.txt, and then use the DiskPart tool to
run the script that automates the configuration of the System, MSR, and Windows
partitions.
Copy
select disk 0
clean
convert gpt
create partition primary size=300
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
create partition efi size=100
rem == Note: for Advanced Format Generation One drives, change to
size=260.
Save the following code as CreatePartitions.txt, and then use the DiskPart tool to
run the script that automates the configuration of the Windows RE Tools partition,
the System, MSR, Windows, and recovery image partitions.
Copy
rem == CreatePartitions-UEFI.txt ==
rem == These commands are used with DiskPart to
rem create five partitions
rem for a UEFI/GPT-based PC.
rem Adjust the partition sizes to fill the drive
rem as necessary. ==
select disk 0
clean
convert gpt
rem == 1. Windows RE tools partition ===============
create partition primary size=300
format quick fs=ntfs label="Windows RE tools"
assign letter="T"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
rem == 2. System partition =========================
create partition efi size=100
rem ** NOTE: For Advanced Format 4Kn drives,
rem change this value to size = 260 **
format quick fs=fat32 label="System"
assign letter="S"
rem == 3. Microsoft Reserved (MSR) partition =======
create partition msr size=128
rem == 4. Windows partition ========================
rem == a. Create the Windows partition ==========
create partition primary
rem == b. Create space for the recovery image ===
shrink minimum=15000
rem ** NOTE: Update this size to match the size
rem of the recovery image **
rem == c. Prepare the Windows partition =========
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 5. Recovery image partition ================
create partition primary
format quick fs=ntfs label="Recovery image"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit
Providing Additional Protection for Windows RE Tools and Recovery Image
Partitions
If you use the recommended DiskPart script, end users do not see the Windows RE
Tools partition and the recovery image partition in File Explorer. However, they can
see and remove the recovery image partition by using disk management tools.
If you want to prevent end users from removing partitions by using disk
management tools, you can add the following DiskPart command to the script
when you create a partition.
Copy
gpt attributes=0x8000000000000001
After you create the partitions, you can use a deployment script to apply the
Windows images on the newly created partitions. For more information,
see Samples: Applying Windows, System, and Recovery Partitions by using a
Deployment Script.
This topic describes how to configure hard drive partitions including hard disk
drives (HDDs), solid-state drives (SSDs), and other drives, for a Unified Extensible
Firmware Interface (UEFI)–based PC.
In this topic:
When you deploy Windows® to a UEFI-based PC, you must format the hard drive
that includes the Windows partition by using a GUID partition table (GPT) file
system. Additional drives may use either the GPT or the master boot record (MBR)
file format.
This partition must allocate space for the Windows RE tools image (winre.wim,
typically between 250-300MB, depending on base language and
customizations added), plus enough free space so that the partition can be
captured by backup utilities:
o If the partition is less than 500 MB, it must have at least 50 MB of free
space.
o If the partition is 500 MB or larger, it must have at least 320 MB of free
space.
o If the partition is larger than 1 GB, we recommend that it should have at
least 1 GB free.
o This partition must use the Type ID: DE94BBA4-06D1-4D40-A16A-
BFD50179D6AC.
o The Windows RE tools should be in a separate partition than the Windows
partition to support automatic failover and to support booting Windows
BitLocker Drive Encryption-encrypted partitions.
System Partition
The minimum size of this partition is 100 MB, and must be formatted using
the FAT32 file format.
This partition is managed by the operating system, and should not contain
any other files, including Windows RE tools.
Note
For Advanced Format 4K Native drives (4-KB-per-sector) drives, the minimum size
is 260 MB, due to a limitation of the FAT32 file format. The minimum partition size
of FAT32 drives is calculated as sector size (4KB) x 65527 = 256 MB.
Advanced Format 512e drives are not affected by this limitation, because their
emulated sector size is 512 bytes. 512 bytes x 65527 = 32 MB, which is less than the
100 MB minimum size for this partition.
Add an MSR to each drive for drive management. The MSR is a reserved
partition that does not receive a partition ID. It cannot store user data.
Any other utility partitions must be located before the Windows, data, and
recovery image partitions. This allows end users to perform actions such as
resizing the Windows partition or reclaiming the recovery image partition
without affecting system utilities.
o Image_size: This is the estimated size of the image after it has been
applied from the WIM image file. Use the command:
Copy
If your WIM image file contains multiple images, use the size
information reported for the image configured to be used by push-
button reset.
o Buffer:
x64: 1.2 GB
x86: 1.1 GB
ARM: 1.0 GB
When used, this partition includes the Windows recovery image (install.wim).
The size of this partition must include space for the Windows recovery image
(at least 2 GB), plus enough free space so that the partition can be captured
by backup utilities:
For more information about GPT drive and hard drive partitions, see The Windows
and GPT FAQ.
Partition Configurations
This section describes the default partition configuration and the recommended
partition configuration.
Default Configuration: Windows RE Tools, System, MSR, and Windows
Partitions
By using this configuration, you can add system tools such as Windows BitLocker
Drive Encryption and Windows RE to your customized Windows installation.
Recommended Configuration: Windows RE Tools, System, MSR, Windows,
and Recovery Image Partitions
By default, system partitions do not appear in File Explorer. This helps protect end
users from accidentally modifying a partition.
You can help protect end users from accidentally modifying other partitions in the
same way by identifying them as utility partitions.
To set partitions as utility partitions
When you are deploying Windows by using the DiskPart tool, use the attributes
volume set GPT_ATTRIBUTE_PLATFORM_REQUIRED command after you create
the partition to identify the partition as a utility partition. For more information, see
the MSDN topic: PARTITION_INFORMATION_GPT structure.
1. Click Start, right-click Computer, and then click Manage. The Computer
Management window opens.
2. Click Disk Management. The list of available drives and partitions appears.
3. In the list of drives and partitions, confirm that the system and utility
partitions are present and are not assigned a drive letter.
Related Sample Files
The following files contain XML samples that demonstrate how to set up partitions
on a UEFI-based PC.
Sample: Configure UEFI/GPT-Based Hard Demonstrates how to add answer-file settings to
Drive Partitions by Using Windows Setup automatically configure hard drive partitions during
Windows installation.
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
These instructions show how to set up a basic Windows PE installation that runs
from the drive. This can sometimes give you better performance than booting from
memory, and can help you run Windows PE on PCs or virtual environments with
low memory. This procedure is also known as a non-RAMDISK boot, or a flat boot.
Note
When Windows PE is running from the drive, you must turn off the PC before
disconnecting the drive to avoid losing your work.
Install the Windows ADK
Get the Windows Assessment and Deployment Kit (Windows ADK) Technical
Reference, including the Windows PE feature.
The 64-bit version of Windows PE can boot 64-bit UEFI and 64-bit BIOS PCs:
Copy
Copy
Copy
Note
The following commands prepare a USB hard drive that can boot on either a BIOS-
based or UEFI-based PC.
On UEFI-based PCs, Windows PE requires a boot partition formatted using the
FAT32 file format, which only supports file sizes up to 4 GB. We recommend
creating a separate partition on the drive, formatted using NTFS, so that you can
store Windows images and other large files.
Copy
diskpart
list disk
select <disk number>
clean
rem === Create the Windows PE partition. ===
create partition primary size=2000
format quick fs=fat32 label="Windows PE"
assign letter=P
active
rem === Create a data partition. ===
create partition primary
format fs=ntfs quick label="Other files"
assign letter=O
list vol
exit
where *\<disk number\>* is the listed number of the external USB hard
drive.
Copy
Copy
Ignore any warning messages that say "Warning: Resume application not found."
Boot to Windows PE
1. Connect the device (internal or external USB hard drive) into the PC you want
to work on.
2. Turn on the PC, and use the boot menus to select the Windows PE drive.
Typically this requires pressing a hardware button or a key, such as the Esc
key.
Note
For UEFI-based PCs, you might need to find an option to manually select the UEFI
boot files, for example, USBDrive01\EFI\BOOT\BOOTX64.EFI.
Copy
If the PC does not boot, try the following steps in sequence, and try to boot
the PC after each step:
1. For external USB drives, try inserting the drive into a different USB port.
Avoid using USB hubs or cables, because they might not be detected
during the boot sequence. Avoid USB 3.0 ports if the firmware does not
contain native support for USB 3.0.
2. If your PC requires drivers to boot, such as storage drivers or video
drivers, or if your driver requires changes to the registry, add the driver
to the Windows PE image. For more info, see WinPE: Mount and
Customize.
3. Update the firmware of the PC to the latest version.
For tips on connecting to a network, see WinPE Network Drivers: Initializing
and adding drivers.
Running Windows Setup from Windows PE
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
Create a Windows PE (WinPE) bootable USB flash drive or an external USB hard
drive.
The default installation runs from memory (RAM disk), so you can remove the drive
while Windows PE is running.
Install the Windows ADK
Install the following features from the Windows Assessment and Deployment
Kit (Windows ADK):
o Deployment Tools: includes the Deployment and Imaging Tools
Environment.
o Windows Preinstallation Environment : includes the files used to install
Windows PE.
Install Windows PE
Copy
3. Install Windows PE to the USB flash drive, specifying the drive letter:
Copy
After the command window appears, the wpeinit command runs, which sets
up the system. This might take a few minutes.
Troubleshooting
If the copype command isn't recognized, make sure you're running the
command from the Deployment and Imaging Tools Environment, which is
part of the Windows ADK.
If Windows PE doesn't appear, try the following workarounds, rebooting the
PC each time:
o To boot a PC that supports UEFI mode, in the firmware boot menus, try
manually selecting the boot files: \EFI\BOOT\BOOTX64.EFI.
o Try a different USB port. Avoid hubs or cables.
o Avoid USB 3.0 ports if the firmware doesn't contain native support for USB
3.0.
o Clean the USB flash drive, and then reinstall Windows PE. This can help
remove extra boot partitions or other boot software.
Copy
diskpart
list disk
select disk <disk number>
clean
create partition primary
format quick fs=fat32 label="Windows PE"
assign letter="F"
exit
o Try booting Windows PE from a DVD instead. Create an ISO file that you
can burn onto a DVD:
Copy
o If your PC requires storage or video drivers to boot, try adding those same
drivers to the Windows PE image. For more info, see WinPE: Mount and
Customize.
o Update the firmware of the PC to the latest version.
If the PC doesn't connect to network locations, see WinPE Network Drivers:
Initializing and adding drivers.
Storing Windows Images on the Windows PE Drive
For external USB hard drives, you can create a separate NTFS partition that
can handle larger file sizes:
Copy
diskpart
list disk
select <disk number>
clean
rem === Create the Windows PE partition. ===
create partition primary size=2000
format quick fs=fat32 label="Windows PE"
assign letter=P
active
rem === Create a data partition. ===
create partition primary
format fs=ntfs quick label="Other files"
assign letter=O
list vol
exit
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
Common customizations:
Add device drivers (.inf files). You can customize device drivers, such as
drivers that support network cards or storage devices. For more info,
see WinPE: Add drivers.
Add optional components (packages or .cab files). You can add features to
Windows PE, such as languages, hotfixes, and support for features like
PowerShell and the HTML Application Language (HTA). In Windows PE,
feature packages are known as optional components. For more info,
see WinPE: Add packages (Optional Components Reference).
Add a language. To run Windows PE in multiple languages, add the packages
(optional components) for those languages. For more info, see WinPE: Add
packages (Optional Components Reference).
Add a startup script. Examples include setting up a network connection, or
adding a custom application, such as diagnostic software.
Add an app. Note, Windows PE only supports legacy apps.
Add temporary storage (scratch space). If your application requires
temporary file storage, you can reserve extra memory space in RAM.
Replace the background image
Add answer file settings
Get the Windows Assessment and Deployment Kit with Windows PE tools
Install the Windows Assessment and Deployment Kit (Windows ADK) Technical
Reference, including the Windows PE feature.
Copy
o The 32-bit version of Windows PE can boot 32-bit UEFI, 32-bit BIOS, and
64-bit BIOS PCs.
Copy
Copy
For Plug and Play or networking support, make sure that you include a call
to wpeinit in your customized Startnet.cmd script. For more info, see Wpeinit
and Startnet.cmd: Using WinPE Startup Scripts.
Add an app
Copy
md "C:\WinPE_amd64\mount\windows\<MyApp>"
Copy
3. Test the app later by booting Windows PE and running the application from
the X: directory.
Copy
X:\Windows\System32> X:\Windows\<MyApp>
Copy
Dism /Set-ScratchSpace:128 /Image:"C:\WinPE_amd64\mount"
Replace the background image
1. If you've got multiple versions of Windows PE, you can set the background
image so you can instantly tell which version of Windows PE is running.
Some Windows PE settings can be managed by using an answer file, such as firewall,
network, and display settings. Create an answer file, name it unattend.xml, and add it
to the root of the Windows PE media to process these settings. For more
information, see Wpeinit and Startnet.cmd: Using WinPE Startup Scripts.
Copy
Copy
Windows PE won’t boot? See the troubleshooting tips at the end of the
topic: WinPE: Create USB Bootable drive
For tips on connecting to a network, see WinPE Network Drivers: Initializing
and adding drivers.
If the Windows PE image becomes unserviceable, you may need to clean up
the images before you can mount the image again. For information,
see Repair a Windows Image.
To delete a working directory:
In some cases, you may not be able to recover the mounted image. DISM protects
you from accidentally deleting the working directory, so you may have to try the
following steps to get access to delete the mounted directory. Try each of the
following steps:
Copy
Copy
Copy
dism /Cleanup-Mountpoints
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
These instructions show how to set up a basic Windows PE installation that runs
from the drive. This can sometimes give you better performance than booting from
memory, and can help you run Windows PE on PCs or virtual environments with
low memory. This procedure is also known as a non-RAMDISK boot, or a flat boot.
Note
When Windows PE is running from the drive, you must turn off the PC before
disconnecting the drive to avoid losing your work.
Install the Windows ADK
Get the Windows Assessment and Deployment Kit (Windows ADK) Technical
Reference, including the Windows PE feature.
The 64-bit version of Windows PE can boot 64-bit UEFI and 64-bit BIOS PCs:
Copy
The 32-bit version of Windows PE can boot 32-bit UEFI, 32-bit BIOS, and 64-
bit BIOS PCs:
Copy
Copy
Note
The following commands prepare a USB hard drive that can boot on either a BIOS-
based or UEFI-based PC.
On UEFI-based PCs, Windows PE requires a boot partition formatted using the
FAT32 file format, which only supports file sizes up to 4 GB. We recommend
creating a separate partition on the drive, formatted using NTFS, so that you can
store Windows images and other large files.
Copy
diskpart
list disk
select <disk number>
clean
rem === Create the Windows PE partition. ===
create partition primary size=2000
format quick fs=fat32 label="Windows PE"
assign letter=P
active
rem === Create a data partition. ===
create partition primary
format fs=ntfs quick label="Other files"
assign letter=O
list vol
exit
where *\<disk number\>* is the listed number of the external USB hard
drive.
2. Apply the Windows PE image to the hard drive.
Copy
Copy
Ignore any warning messages that say "Warning: Resume application not found."
Boot to Windows PE
1. Connect the device (internal or external USB hard drive) into the PC you want
to work on.
2. Turn on the PC, and use the boot menus to select the Windows PE drive.
Typically this requires pressing a hardware button or a key, such as the Esc
key.
Note
For UEFI-based PCs, you might need to find an option to manually select the UEFI
boot files, for example, USBDrive01\EFI\BOOT\BOOTX64.EFI.
Copy
If the PC does not boot, try the following steps in sequence, and try to boot
the PC after each step:
1. For external USB drives, try inserting the drive into a different USB port.
Avoid using USB hubs or cables, because they might not be detected
during the boot sequence. Avoid USB 3.0 ports if the firmware does not
contain native support for USB 3.0.
2. If your PC requires drivers to boot, such as storage drivers or video
drivers, or if your driver requires changes to the registry, add the driver
to the Windows PE image. For more info, see WinPE: Mount and
Customize.
3. Update the firmware of the PC to the latest version.
For tips on connecting to a network, see WinPE Network Drivers: Initializing
and adding drivers.
Running Windows Setup from Windows PE
See Windows Setup Supported Platforms and Cross-Platform Deployments for tips
on installing Windows on UEFI PCs that support both UEFI and legacy BIOS firmware
modes, and for using the 32-bit (x86) version of Windows PE to install a 64-bit
version of Windows.
See Also
What is DISM?
04/14/2014
7 minutes to read
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
DISM replaces the ImageX tool which was deprecated in Windows 8. DISM also
replaces Package Manager (Pkgmgr.exe), PEimg, and Intlcfg that were included in
previous deployment toolkits. DISM also adds new functionality to improve the
experience for offline servicing.
Image Requirements
Benefits
Common Servicing and Management Scenarios
Limitations
Image Requirements
DISM can be used to mount and service a Windows image from a .wim file, .vhd
file, or a .vhdx file or, in some cases, to update a running operating system. It can
be used with older Windows image files (.wim files). However, it cannot be used
with Windows images that are more recent than the installed version of the
Windows Assessment and Deployment Kit (Windows ADK) in which DISM is
distributed. DISM is also installed with the Windows 8.1 and Windows 8 operating
system.
For a complete technical description of WIM, see the Windows Imaging File Format
(WIM) white paper.
Windows 8.1
Windows 8
Windows Server 2012 R2
Windows Server® 2012
Windows® 7
Windows Server 2008 R2
Windows Server 2008 SP2
Windows PE 5.0
Windows PE 4.0
Windows Preinstallation Environment (Windows PE) 3.0
Note
DISM cannot mount a Windows image from a VHD on Windows Vista® with
Service Pack 1 (SP1) or Windows Server 2008. You must attach the VHD using the
DiskPart tool before you can use DISM to service the image. When you service VHD
images that have been attached using the DiskPart tool, the changes are
automatically committed with each operation and cannot be discarded.
Note
To service inbox drivers in an offline image of Windows Vista with Service Pack 2
(SP2) or Windows Server 2008 with SP2, you must use the Windows 7 version of
DISM or PkgMgr. The Windows 7 version of DISM is available in Windows 7 and
Windows PE 3.0 operating systems, or can be installed with the Windows
Automated Installation Kit (Windows AIK) or the Windows OEM Preinstallation Kit
(Windows OPK) for Windows 7.
For a list of the supported platforms and architecture types, see DISM Supported
Platforms.
Benefits
You can use DISM with .wim, .vhd, or .vhdx files to:
Image servicing and management solutions fall into two main categories:
Here are some common scenarios for image servicing and management:
Tasks
Manage several images in a single .wim file by appending, removing, or enumerating the images.
List specific information about an image mounted from a .wim, .vhd, or .vhdx file, including where it is
mounted, the mount status, and the index of each image in a .wim file.
List all of the Windows editions that an image can be upgraded to.
Split a large .wim file into several smaller files to fit on selected media.
Limitations
Answer files. When you specify an answer file (Unattend.xml) for an image, only
the settings specified in the offlineServicing configuration pass are applied. All
other settings in the answer file are ignored. For more information, see DISM
Unattended Servicing Command-Line Options
Version compatibility. DISM can be used with target images of older Windows
operating systems, but not with target images of operating systems that are more
recent than the installed version of the Windows ADK in which DISM is distributed.
Service Packs. Service packs must be installed online with the Windows Update
Standalone installer. For more information about Windows Update Standalone
Installer, see Description of the Windows Update Standalone Installer in Windows.
Package installation order. Packages are installed in the order that they are listed
in the command line. In the following example, 1.inf, 2.inf, and 3.inf will be installed
in the order in which they are listed in the command line.
Copy
DISM.exe /image:"c:\images\Image1" /Add-Driver /ForceUnsigned
/DriverName:"C:\Drivers\1.inf" /DriverName:"C:\Drivers\2.inf"
/DriverName:"C:\Drivers\3.inf"
Supported servicing commands are dynamic. The commands and options that
are available for servicing an image depend on which Windows operating system
you are servicing, and whether the image is offline or a currently running operating
system.
Multiple unattend files are not supported. You can specify more than one driver
or package on a command line. However, multiple Unattend.xml answer files are
not supported. Only a single answer file may be specified on any command line.
Multiple servicing commands are not supported. You can specify multiple
drivers (1.inf, 2.inf) or packages, but you cannot specify multiple commands (such
as /Add-Driver/Remove-Driver or /Add-Driver/Add-Package) on the same
command line.
Logging to a network share. When you use a computer that is not joined to a
network domain, use net use with domain credentials to set access permissions
before you specify the path for the DISM log that is stored on a network share.
Do not install a language pack after an update. If you install an update (hotfix,
general distribution release [GDR], or service pack [SP]) that contains language-
dependent resources before you install a language pack, the language-specific
changes that are contained in the update are not applied. Always install language
packs before you install updates.
The ImageX tool is deprecated in Windows 8 and has been replaced with DISM for
image management.
You can also use DISM to install, uninstall, configure, and update Windows
features, packages, drivers, and international settings in a .wim file or VHD using
the DISM servicing commands.
DISM commands are used on offline images, but subsets of the DISM commands
are also available for servicing a running operating system.
DISM is installed with Windows 8.1, and it is also distributed in the Windows
Assessment and Deployment Kit (Windows ADK). It can be used to service
Windows 8.1, Windows 8, Windows Server 2012 R2, Windows Server® 2012,
Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2008,
Windows Preinstallation Environment (Windows PE) 4.0, or Windows PE 3.0 images.
DISM replaces several deployment tools, including PEimg, Intlcfg, ImageX, and
Package Manager.
In This Section
What is DISM? Describes the DISM system requirements, benefits,
common servicing and management scenarios, and
limitations.
DISM Reference (Deployment Image Provides reference information for DISM, including
Servicing and Management) command-line options, best practices, and supported
platforms.
Problema de arranque en
Windows 8- ¿Cómo utilizar el
comando BCDBOOT en WinPE?
Última actualización : 2015/06/15 19:56
SENT TO YOUR EMAIL ABRIR EN SU TELÉFONO INTELIGENTE
Nota:
1. Este metodo es valido solo para Windows 8/8.1 y algunos datos se pueden
perder.
2. Si no ha resuelto el problema de arranque,por favor contacte con el
Soporte Tecnico de ASUS.
Para este problema ,podria tratar de utilizar WinPE para recuperar el Boot
Configuration Data(BCD).
1. Iniciar desde un drive USB donde tiene instalado WinPE.
[Windows 8] Como iniciar el sistema desde una unidad USB o un CD-ROM
drive?
¿Como acceder a la configuracion de BIOS en un Portatil?
2. Digitar "diskpart" y pulse Enter.
Applies To: Windows 8, Windows 8.1, Windows Server 2012, Windows Server 2012
R2
Push-Button Reset Overview Overview of push-button reset features, which are available in
Windows 8 client editions.
Windows Recovery Environment Use REAgentC.exe command-line options and other Windows
(Windows RE) Reference RE tools to customize Windows RE features and settings during
installation.
Volume activation is the process that Microsoft volume licensing customers use to
automate and manage the activation of Windows operating systems, Microsoft
Office, and other Microsoft products across large organizations. Volume licensing is
available to customers who purchase software under various volume programs
(such as Open and Select) and to participants in programs such as the Microsoft
Partner Program and MSDN Subscriptions.
Volume activation is a configurable solution that helps automate and manage the
product activation process on computers running Windows operating systems that
have been licensed under a volume licensing program. Volume activation is also
used with other software from Microsoft (most notably the Office suites) that are
sold under volume licensing agreements and that support volume activation.
This guide provides information and step-by-step guidance to help you choose a
volume activation method that suits your environment, and then to configure that
solution successfully. This guide describes the new volume activation features that
are available in Windows 8.1 and Windows Server 2012 R2 and the tools that are
provided in these versions of Windows and Windows Server to manage volume
activation.
Because most organizations will not immediately switch all computers to Windows
8.1, practical volume activation strategies must also take in to account how to work
with the Windows 78, Windows 7, Windows Server 2012, and Windows Server 2008
R2 2 operating systems. This guide discusses how the new volume activation tools
can support earlier operating systems, but it does not discuss the tools that are
provided with earlier operating system versions.
Volume activation—and the need for activation itself—is not new, and this guide
does not review all of its concepts and history. You can find additional background
in the appendices of this guide. For more information, see Volume Activation
Overview in the TechNet Library.
Keep in mind that the method of activation does not change an organization’s
responsibility to the licensing requirements. You must ensure that all software used
in your organization is properly licensed and activated in accordance with the terms
of the licensing agreements in place.
In this guide:
on the client device. You can activate Windows 8.1 in the same ways as previous
versions—by using Multiple Activation Keys (MAKs), retail keys, or volume licensing
keys with a Key Management Server (KMS). This guide examines in more detail the
differences in how keys are used from the client and applied from the KMS.
A significant change was made with the release of Windows 8 and Windows Server
2012 with the addition of Active Directory-based activation. This new activation
method is a role service that allows you to use Active Directory Domain Services
(AD DS) to store activation objects, which can further simplify the task of
maintaining volume activation services for a network. With Active Directory-based
activation, no additional host server is needed.
Instead, a computer running Windows 8.1, Windows 8, Windows Server 2012 R2, or
Windows Server 2012 R2 attempts to retrieve volume activation information from
the domain at startup, falling back to KMS if the domain is not available or not
configured for Active Directory-based activation. The computer will periodically
attempt to reactivate by using the domain, and it will stay activated as long as it
remains a member of the domain and has periodic contact with a domain
controller or a KMS.
See also