Windows 10: About copype.cmd

I cannot use copype.cmd with amd64 architecture.There is an error "The following processor architecture was not found: amd64."My computer use Windows 10 education, version 21H2, x64-based processor Intel core i3-7100U CPU

:)

 

'copype' is not recognized as an internal or external command, operable program or batch file.

I am trying to create WinPE on bootable device. I installed Windows Preinstallation Environment with add-ons, typed 'copype' on 'Deployment and Imaging Tools Environment', but faced faced with an issue like not recognized command.

Below actions are already taken. So please take into account when providing a solution:

1. 'adksetup.exe' is installed
2. 'adkwinpesetup.exe' is installed
3. The folder containing 'Windows Kits' added into Windows Firewall Exclusion list
4. DISM launched as Administrator
5. 'Deployment and Imaging Tools Environment' launched as Administrator

Despite above listed prerequisites 'copype' command still not available and or recognized by the tool.

I already searched this topic in Microsoft forums and followed all the instructions.

I would be very thankful if you would provide a solution to this issue.

Thanks in advance.

 

Windows and CMD- renaming a file in CMD

Steps I've done

Here what happens

• 
  turn on PC
  
• 
  start windows
  
• 
  get blue screen ( message NTFS file)
  
• 
  it reboots returns to diagnosing PC
  
• 
  Diagnose and repair fails
  
• 
  I move to advance options
  
• 
  will not reset windows , I click on CMD
  

things I've tried
commands:

reagentc /disable

reagentc /enable

*************************FAILED
not recognized
**********************************

Please advise

• 
  

 

laptop doesnt boot automatically

This is what happened.

1. Did a repair install and later disabled hibertnate in CMD.
2. Enabled legacy option ROM in BIOS.
3. After a few times startup ( i used the system in such mode for 5 days), changed boot option back to default.
4. Vola!! It boots automatically to win10 without any keypress. Tested it with many starts to confirm the same.
5. Re-enabled hibernate option using CMD and later selected Fast Startup.
6. System booted normally, without the need for any keypress.

I do not know exactly whether such steps resolved the problem or what else happened, hence cannot suggest above steps.

Many thanks to all members who helped to troubleshoot problems.