TeraByte Product Release Thread

I tried with Q-Dir and failed too. I think is the lack of support from a minimal OS like a WinPE or WinRE. These can't associate file types with a particular program.
I know you might already know but here I go anyway: you must open notepad, click open and then browse the file system. You can still launch executables from Explorer++ though.

 

Thanks. I installed x64 in the TBWinRE. It lets you open .txt files directly without browsing.

http://vault32.com/a43/download/FileManagers.zip

Select the .txt file, click the Text Editor icon at the top.

 

Still no luck isolating this problem. I've tried exiting out of Directory Opus, but the same thing happens.
What I do know today is if I click "Retry" twice, the error goes and the process completes. As I've said, I've never had this problem before.



Do you guys have Windows 11 24H2 running?

 

Not me.

Did you try this already?
https://www.terabyteunlimited.com/ucf/viewtopic.php?t=2401

 

You gave me a clue, Mr.X.
Have a look at this.

 

Uninstalling the previous Windows PE Add-on for Windows ADK and the previous Windows ADK, then installing the newest versions have fixed my problem.
It appears that it's needed for Windows 11 24H2.

Thanks to all who contributed.

 

Hadron,

Were you making TBWinPE rather than TBWinRE?

 

Yes Brian.

 

I tried installing adksetup.exe in 2 computers. Failed. I don't have 24H2.

 

I've now updated all my Windows 11 computers to ADK v10.1.26100.1 (May 2024) and the Windows PE Add-on. You have to uninstall the previous versions first.

 

No versions were installed on either computer. The installer said it couldn't download "something". My quotes.

 

Did you run the installer as Administrator?

 

I usually install the ADK to my test computer and copy the following 2 folders to D:\ .... \11 folder in other computers.

Assessment and Deployment Kit
Catalogs

I then restore an image to the test computer to remove over 3 GB of ADK. There is no point having the C:\ drive larger than it needs to be.

So my path is...

D:\My_files\Storage\Keep\H to N\M\Microsoft\_ADKs extracted\11

 

The installer in Microsoft's links is a downloader and installer. I only use the default settings, as my main aim is the Windows PE Add-on.

 

Yes. 2 computers. 2 Win11 on one computer. Same result. One was a fresh Win11 install.

So 3 Win11.

 

Common message...

 

That doesn't look like anything I saw.
Did you go here?
https://learn.microsoft.com/en-us/windows-hardware/get-started/adk-install

 

Yes and I re downloaded the file.

 

I see now. You have a window over the top of the first one.
I seems like it's looking for a cab file.
Have you tried downloading the package, then installing it?

 

No luck there either. Same error.

I'll try tomorrow.

 

Get the full ADK 10.1.26100.1 (May 2024) iso:

ADK (Uncheck all cases except "Deployment Tools")
https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/26100.1.240331-1435.ge_release_amd64fre_ADK.iso


ADK WinPE addons
https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/26100.1.240331-1435.ge_release_amd64fre_adkwinpeaddons.iso

 

Superb. Thanks. Great workaround. I've made a TBWinPE UFD. Yesterday's download still doesn't work.

Installing the ADK added 4.1 GB to the used space in my C: drive. I copied the "10" folder to my D: drive (added 2 GB) and renamed it 11_24H2.
Then the Win11 partition was restored to yesterday's image.
I can use the 11_24H2 folder in my other computers as there is no need to have the ADK installed to make TBWinPEs.

 

Did you Uncheck all cases except "Deployment Tools"?
Unmarking not needed cases/features reduces useless space significantly.

 

Yes I did. Always.

As my CPU isn't ARM64, I deleted the arm64 folder from 11_24H2. That saves a further 1 GB. 11_24H2 is now 1.06 GB

 

It appears that you have Windows ADK v10.1.26100.1 (May 2024) and Windows PE Add-on all sorted with the workaround, Brian.
If it was me though, I'd be scratching my head trying to identify the initial problem you had.

The cab file error (d562ae79e25b943d03fc6aa7a65f9b81.cab) that setup couldn't locate is most likely the clue.
Have you done a file and registry search for that particular cab file? It appears that it may have once been on your 'E' drive.

There is probably a reference to it in the registry.