Windows 10: Deployment Tools Prompt iscdimg.exe is valid,but is for a machine type other than the...

anyone can help me solve this prompt?

:)

 

Installation media boots to command prompt

I've just booted from known working install media to see exactly what it does when booting. The sequence of events is...

1. Windows logo on a black screen
2. circling dots appear beneath the logo
3. light blue 'Please wait' screen with circling dots
4. a command prompt window (very briefly)
5. the initial Setup page appears

Do you see steps 1-3? If so, it appears you have stopped at step 4, suggesting that something on the disc cannot be read.

Does the disc boot properly in another machine? If so, try cleaning the laptop's drive lens then try booting from the disc again.

If not, make new install media with Microsoft's Media Creation Tool, either as a bootable USB, on an ISO that you can burn to another disc. At Step 8 in Option One of this tutorial you can choose between making a USB or an ISO.

Download Windows 10 ISO File

 

Customised Windows 10 deployment on multiple desktops and laptops.

OK, after giving this a thought and thinking how I would do it, here's my suggestion. Please notice that, as I said, this is how I would do it. Other geeks might disagree with parts or all of it.

I tested this scenario using one Hyper-V VM as technician machine (the one to build image) and three virtual machines to test simultaneous deployment in two scenarios:

• Capturing install.wim from technician machine and using DISM to apply / deploy image from a network share
• Capturing install.wim from technician machine, making ISO from it, deploying by clean installing from ISO burned to Flash drive

Based on the fact that ISO method is clearly faster and simpler, it is what I suggest to you. I estimate you would need an hour and half to two hours to customize install image, capture it and make an ISO, then assuming you would make 5 Flash drives for install / deployment you would need about half an hour per five machines, in other words you would deploy to those 25 new machines in less than three hours, almost a full working day to deploy those 50 existing ones.

Two working days, day 1 to make the image and deploy to new machines, day 2 to deploy to old ones.

Chronological workflow based on my suggestion:

Phase 1, Image customization tutorial, parts One through Six:

• Install Windows 10 on a technician machine (I recommend Hyper-V VM but any capable PC is OK)
• Boot to Audit Mode
• Update Windows, install software, customize & personalize Windows
• Sysprep

Phase 2:

• Capture the install.wim from technician machine as told in this tutorial, Part Four steps 4.1 through 4.5 (physical PC as technician machine) or Part Four steps 4.6 through 4.13 (Hyper-V VM as technician machine)
• Create ISO as told in same tutorial, Part Five
• Burn / write ISO to as many Flash drives as you want to / need to for simultaneous installs
• Boot production machines from Flash drive, install Windows 10

The above is how I would do this. If you choose the DISM method instead, applying install.wim from a network share, see this Microsoft support article: https://technet.microsoft.com/en-us/.../hh824910.aspx

For more advanced deployment using MDT see this article: https://technet.microsoft.com/en-us/.../dn475741.aspx

 

Unable to type in to box on 'Control Panel'.

In this case, we suggest that you check for corrupted Windows system files. System File Checker (SFC) is a utility in Windows that scans for corrupted Windows system files. If it finds a problem, it will try to replace the problematic system files from a
cached version that’s on your PC. If SFC can’t replace the files, the Deployment Image Service and Management Tool (DISM) can check the corrupted files then download and replace the files through Windows Update.

To run System File Checker (SFC), follow these steps:

• In the search box on the taskbar, type command prompt, press and hold (or right-click)
  Command Prompt, then select Run as administrator >
  Yes.
• At the command prompt, type sfc /scannow (note the space between sfc and the /). Scanning will take a few minutes.
• Do one of the following, depending on the results of the scan:
  • If SFC finds corrupted files and replaces them, restart your PC and check if the issue persists.
  • If SFC doesn’t find corrupted files or finds corrupted files but can’t replace them, try using the Deployment Image Service and Management Tool (DISM).

For more info about System File Checker, see
Use the System File Checker tool to repair missing or corrupted system files.

To use the Deployment Image Service and Management Tool (DISM), follow these steps:

• In the search box on the taskbar, type command prompt, press and hold (or right-click)
  Command Prompt, and then select Run as administrator >
  Yes.
• At the command prompt, type dism.exe /Online /Cleanup-image /Restorehealth (note the space between dism.exe and / and each switch (/)).
• If DISM finds corrupted files and replaces them, restart your PC and check if the issue persists.

Note: You need to be connected to the Internet to use DISM, and it might take several minutes to finish.

For more info about DISM, see
Fix Windows Update errors by using the DISM or System Update Readiness tool.

Let us know how it goes.