Cannot clean install Win 10 UEFI mode (Toshiba Satellite C75A)

Hi zbook. problem is I don't end up with a working bootable system to run a log collector. I could try running it from a working system with the failed installation disk connected via USB - will that work?

What were the steps that were made to get the setupact.log?

Code:

2017-12-31 14:38:26, Info                  UI     Entering Page Image Selection.2017-12-31 14:38:26, Info                  UI      search directory is [C:\Sources].
2017-12-31 14:38:26, Info                  UI     pid_GetProductKeyFromSources:Product key found in pid.txt/ei.cfg is malformed
2017-12-31 14:38:26, Info                  UI     DetectDigitalMarker: Digital marker product key detected.
2017-12-31 14:38:26, Info       [0x060122] IBS    Callback_Productkey_Validate: Entry
2017-12-31 14:38:26, Info       [0x060124] IBS    Callback_Productkey_Validate: Validating user supplied product key
2017-12-31 14:38:26, Info                  IBS    Callback_Productkey_Validate: Could not find working directory on blackboard
2017-12-31 14:38:26, Info                  IBS    Callback_Productkey_Validate: Calling SkuGetImageProductKeyFiles to get product key files
2017-12-31 14:38:31, Info                  IBS    Callback_Productkey_Validate: Retrieving alternate product key...
2017-12-31 14:38:31, Info                  IBS    Callback_Productkey_Validate: Alternate product key retrieval result: [0xC004F210].
2017-12-31 14:38:31, Error      [0x060555] IBS    Callback_Productkey_Validate: Error with PidgenX config file while validating product key.
2017-12-31 14:38:31, Error      [0x060554] IBS    Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
2017-12-31 14:38:31, Info       [0x06012e] IBS    Callback_Productkey_Validate: ProductKey Value=NULLSTR Error=ERROR_INVALID_DATA Show=1
2017-12-31 14:38:31, Info                  IBS    Callback_Productkey_Validate: Storing return code 0x8a010001 on the blackboard.
2017-12-31 14:38:31, Info       [0x060130] IBS    Callback_Productkey_Validate: Exit
2017-12-31 14:38:31, Info                  UI     Digital marker key found is invalid
2017-12-31 14:38:31, Info       [0x0a0035] UI     Allowing Page 'Product key' to be shown
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 S
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 S N
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Home
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Home N
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Home Single Language
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Education
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Education N
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Pro
2017-12-31 14:38:31, Info       [0x0a0052] UI     No language pack available for image Windows 10 Pro N
2017-12-31 14:38:31, Info       [0x0a011c] UI     WizardDialogPost::SetActive
2017-12-31 14:38:35, Info                  UI      search directory is [C:\Sources].
2017-12-31 14:38:35, Info                  UI     pid_GetProductKeyFromSources:Product key found in pid.txt/ei.cfg is malformed
2017-12-31 14:38:35, Info                  UI     DetectDigitalMarker: Digital marker product key detected.
2017-12-31 14:38:35, Info       [0x060122] IBS    Callback_Productkey_Validate: Entry
2017-12-31 14:38:35, Info       [0x060124] IBS    Callback_Productkey_Validate: Validating user supplied product key
2017-12-31 14:38:35, Info                  IBS    Callback_Productkey_Validate: Could not find working directory on blackboard
2017-12-31 14:38:35, Info                  IBS    Callback_Productkey_Validate: Calling SkuGetImageProductKeyFiles to get product key files
2017-12-31 14:38:44, Info                  IBS    Callback_Productkey_Validate: Retrieving alternate product key...
2017-12-31 14:38:44, Info                  IBS    Callback_Productkey_Validate: Alternate product key retrieval result: [0xC004F210].
2017-12-31 14:38:44, Error      [0x060555] IBS    Callback_Productkey_Validate: Error with PidgenX config file while validating product key.
2017-12-31 14:38:44, Error      [0x060554] IBS    Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
2017-12-31 14:38:44, Info       [0x06012e] IBS    Callback_Productkey_Validate: ProductKey Value=NULLSTR Error=ERROR_INVALID_DATA Show=1
2017-12-31 14:38:44, Info                  IBS    Callback_Productkey_Validate: Storing return code 0x8a010001 on the blackboard.
2017-12-31 14:38:44, Info       [0x060130] IBS    Callback_Productkey_Validate: Exit
2017-12-31 14:38:44, Info                  UI     Digital marker key found is invalid

Code:

2017-12-31 14:38:15, Warning               UI     CLanguages::v_InitLanguage - Failed to load en-US resources with error 2. Will load fallback binaries

Code:

2017-12-31 14:38:15, Info                  UI      search directory is [C:\Sources].2017-12-31 14:38:15, Info                  UI     pid_GetProductKeyFromSources:Product key found in pid.txt/ei.cfg is malformed
2017-12-31 14:38:15, Info                  UI     DetectDigitalMarker: Digital marker product key detected.
2017-12-31 14:38:15, Info       [0x060122] IBS    Callback_Productkey_Validate: Entry
2017-12-31 14:38:15, Info       [0x060124] IBS    Callback_Productkey_Validate: Validating user supplied product key
2017-12-31 14:38:15, Info                  IBS    Callback_Productkey_Validate: Could not find working directory on blackboard
2017-12-31 14:38:15, Info                  IBS    Callback_Productkey_Validate: Calling SkuGetImageProductKeyFiles to get product key files
2017-12-31 14:38:22, Info                  IBS    Callback_Productkey_Validate: Retrieving alternate product key...
2017-12-31 14:38:22, Info                  IBS    Callback_Productkey_Validate: Alternate product key retrieval result: [0xC004F210].
2017-12-31 14:38:22, Error      [0x060555] IBS    Callback_Productkey_Validate: Error with PidgenX config file while validating product key.
2017-12-31 14:38:22, Error      [0x060554] IBS    Callback_Productkey_Validate: An error occurred writing the product key data to the blackboard.
2017-12-31 14:38:22, Info       [0x06012e] IBS    Callback_Productkey_Validate: ProductKey Value=NULLSTR Error=ERROR_INVALID_DATA Show=1
2017-12-31 14:38:22, Info                  IBS    Callback_Productkey_Validate: Storing return code 0x8a010001 on the blackboard.

Just a straightforward Win 10 install;
BIOS in UEFI mode
Install from DVD, USB, HDD partition. all tried. all failed

When setupact.log gets to
IBSLIB OSRollbackService::CSystemVolumeSelectionCheckpoint::Finalize: Created Store \??\G:\EFI\Microsoft\Boot\BCD

it just stops dead - no further activity no matter how long I wait

I think this is some peculiarity of the Satellite / BIOS because believe me I've tried and tried

When you attempted the clean install the bios was in uefi.
Had you tried to clean install in legacy?
Can you create a brand new windows 10 iso to perform the clean install?

When you power on the computer what do you see?
When the clean install failed how did you retrieve the panther log?

see first post - can install in CSM / legacy bios
Have created sevearl Win 10 isos
logs retrieved by booting from Win PE USB

Some o the problems in the log were related to product ID and language. But if you can perform a clean install in legacy I 'm puzzled why there were problems in UEFI with these reported events.
What would happen if you use Macrium to clone another computer and restore on this drive?
Backup and Restore with Macrium Reflect Backup Restore Tutorials

Ive got an HP but if I clone that to a Toshiba I'll get an assortment of problems - incompatible motherboard, display, hardware, drivers etc etc etc + licensing issues. I suppose I could try just to see if it boots

See if you can install Legacy without any problems. Then see if you can convert to UEFI:
Convert Windows 10 from Legacy BIOS to UEFI without Data Loss Installation Upgrade Tutorials
How to Change Legacy to UEFI in Windows 10/8/7

I can install Win 10 in legacy / CSM mode no problem at all.
I then tried running MBR2GPT.EXE:
/Validate option tells me it will work ok
When I run it it trashes something and the disk wont boot (CSM or UEFI)
I've run it from Win PE and Win 10 neither option works

As its an oldish laptop (nearly 5 yrs) i'll just install in CSM mode and use it as a backup. What is strange is that it originally came with Win 8 in UEFI mode and a few updates later was running Win 10 UEFI

Thanks for trying to help

You could try installing it manually.

Boot from PE (for example this Windows 10 Recovery Tools - Bootable Rescue Disk - Windows 10 Forums). You'll need another USB with the Windows installer on it.

1. Partition the disk (EFI, MSR, C, recovery) like you had in post #1 (except that was for Windows 8 not 10 and recommended order has changed - not that it matters really)

Code:

rem == CreatePartitions-UEFI.txt ==
rem == These commands are used with DiskPart to
rem    create four 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. 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 == 2. Microsoft Reserved (MSR) partition =======
create partition msr size=16
rem == 3. Windows partition ========================
rem ==    a. Create the Windows partition ==========
create partition primary 
rem ==    b. Create space for the recovery tools ===
shrink minimum=500
rem       ** NOTE: Update this size to match the
rem                size of the recovery tools 
rem                (winre.wim) plus free space                   **
rem ==    c. Prepare the Windows partition ========= 
format quick fs=ntfs label="Windows"
assign letter="W"
rem === 4. Recovery tools partition ================
create partition primary
format quick fs=ntfs label="Recovery tools"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
list volume
exit

UEFI/GPT-based hard drive partitions | Microsoft Docs

2. Copy EFI stuff to ESP

Code:

W:\Windows\System32\bcdboot W:\Windows /s S:

(check drive letters obviously)

3. Install Windows

Code:

dism /Apply-Image /ImageFile:D:\install.wim /Index:1 /ApplyDir:W:\

You can think about recovery partition later (but it is all in same link here as steps 2 and 3 above)
Capture and Apply Windows, System, and Recovery Partitions | Microsoft Docs)

If the issue is installing in UEFI mode rather than booting it then this will work. Considering it booted in 8 it should boot in 10 also as nothing changed afaik.

I did the same except I ran the steps above and installed Windows while the disk was in a external USB enclosure on a second PC and then physically removed the disk and put it in my laptop. It worked fine and started up from the OOBE stage (where it asks you your user name and so on).

It wouldn't take long to try (half an hour I guess) but if it doesn't work running CSM isn't that bad really. It won't run slower or anything.