Again windows guru help needed ...

[marc_256]

Hi ChrisR,

Thanks again for your help,
the windows 10 pro x64 comes with the SBC/PC.
So I don't have any original OEM windows DVD/memory stick or activation codes.
Can I still use Win10XPE ?

thanks,
marc,

PS: I just installed an old SSD 500GB (80mm M.2)
So now I have 32GB SSD for the OS, and 500 GB for my PB programs.
But still only 4GB RAM

[ChrisR]

Of course you can use Win10XPE, you just need to download an original Windows 10 ISO,
Not a warez version, just an original microsoft ISO version, you don't need a serial number, so it's perfectly legal.
For the Windows 10 version I recommend, Win10_2004_English_x64.iso version 10.0.19041.264 (quite stable windows version), you can google with:

Code: Select all

en_windows_10_consumer_editions_version_2004_updated_may_2020_x64_dvd_36d61c40.iso
SHA-1: 71a288febd984839b575efb3bd9bc9ab7471b604

en_windows_10_consumer_editions_version_2004_updated_may_2020_x86_dvd_2b9b4e01.iso
SHA-1: 7ea6827131b176442c4f9fb007df95d0b149f6b2

I didn't check SHA-1 but with a quick search I found them here

If you need help to build a Win10XPE, don't hesitate, I can help you if needed, I think it's worth a look for this kind of app.
And you can read Win10XPE - How To Quick Start Guide.pdf

[Kuron]

I think you mean 4GB of RAM ...

Nope, 4MB. Seems like yesterday that is what you needed for Windows. A 386 processor and 4MB of RAM and Windows 95 flew along.

[Oso]

Of course you can use Win10XPE, you just need to download an original Windows 10 ISO, Not a warez version, just an original microsoft ISO version, you don't need a serial number, so it's perfectly legal.

It looks very interesting ChrisR. You mention that you don't need a serial number. Is that because it's a recovery system and the recovery system doesn't need activating?

[ChrisR]

It's a bit off-topic and there's a lot to be said for what it is:
It is LiveCD based on Windows 10 or a "better" alternative to Microsoft Dart 10 Diagnostics and Recovery Toolset 10, with extensive documentation here.
After more than 12 years (Win7PESE, Win8PESE, Win10PESE, Win10XPE), I still update the project from time to time, but I don't really work on it anymore. But I'm lucky that other guys have taken over, ex: Win10XPE - Build Your Own Rescue Media.

The project allows you to build your own Win10XPE, from an original Windows 10 ISO. It is indeed not allowed to distribute Windows files and thus share a ready-made Win10XPE build.

It is based on Winre.wim, the Windows Recovery Environment present in all Windows installations and in windows ISOs under install.wim folder \Windows\System32\Recovery\Winre.wim
Then many Windows features were added, such as explorer, disk Management, network, sound, Wow64 basic, etc...
Using Windows files from the ISO, adding the appropriate registry keys... to offer a lightweight desktop environment close to Windows (but without all its features).
It allows you to run a wide range of well-known software applications for performing tasks or troubleshooting a Windows OS while it is offline or for installing a Windows OS. It can be booted via USB drive, CD-ROM, or hard disk. It's fast, being loaded directly into memory.
Over time, the project has become a well known reference, for PC troubleshooters or forensic analysis.

But here, I suppose, it could also be used to control PLCs or run computationally-intensive applications.

[Piero]

"I'm (try to) build a walking robot"
I dunno: I'm supposedly becoming barely able to walk myself, and I have no idea how I did it all this time; it must involve all kinds of miracles

[Oso]

It is LiveCD based on Windows 10 or a "better" alternative to Microsoft Dart 10 Diagnostics and Recovery Toolset 10, with extensive documentation here.

Thanks for the information ChrisR, clearly I need to use it to know it better. What I understand is that you first need a Windows 10 system in order to run it and prepare the new ISO, consisting of the options of your choice, using the built-in tool Winbuilder, is that correct? Then once you have your ISO, you can boot it and I presume install it.

Part of the reason for having an interest in this, is that I'm unhappy with the dictatorial way Microsoft is now behaving, in particular laying down the law in terms of compatibility with older hardware and causing what is even quite recent hardware to become prematurely obsolete. Reading their empty corporate rhetoric on this page about needing to be secure https://support.microsoft.com/en-us/win ... 74389a7ba3 it's easy to see they are moving towards a method of control, while at the same time Windows 10, which is more supportive of existing technology, will start to become unsupported in a couple of years' time.

[ChrisR]

Yes, that's basically it.
I'm trying with a rough summary

In a Windows 10 ISO, you have 3 images:

• Boot.wim for booting before installing Windows
• Install.wim, which contains several Windows installation images (Home, Education, Professional)
• And Winre.wim, the Windows recovery environment included in Install.wim, which can be accessed via a hotkey (F8 or other) when starting up the PC.
  This image is similar to Boot.wim with additional apps and features for recovery, including a minimal network support.

Basically the work with Winbuilder, an interpreted scripting language with an integrated GUI is:

• Apply (mount) the Winre.wim image that serves as a base in a subfolder (Target).
• Load the registry hives to apply the correct access rights.
• Extract the required files from the Windows Install.wim image, depending on the features to be added.
• Copy and adapt parts of the registry from install.wim to winre.wim.
• Integrate host PC drivers, mainly network drivers. Making them available is the user's job.
• Install various applications as selected in the tree by the user.
• The BCD (Boot Configuration Data) is prepared to start boot.wim, below
• Then package everything by creating a new boot.wim image and Win10XPE_x64.ISO

The list of files according to functionality and the registry is the big part of the job, so as to have only the required dependencies and not much more.
Taking into account all changes following Windows updates ISO version, every 6 months.

In application scripts, additional required dependencies are added, driver if there is, required associated registry, services and shortcuts.
For PureBasic, there are no additional dependencies to add, it works very well out of the box on a very light, minimal configuration, proof of its strength and efficiency.

From this ISO created, there is no installation:

• It can be copied (extracted) to a USB stick using USB7Ice or Rufus.
• Copied (extracted) to a hard disk or SSD partition (4 Gb is more than enough)
  In this case, a script "XPE Host Boot Option" prepare for you a batch to configure Win10XPE's entry in your PC's BCD (boot configuration data).
  It's up to you to run it and add Win10XPE at your PC startup list

If booting from a USB key, at 1st use, you must enter in the boot configuration (via hotkeys, ex: F2 for Acer) to add the USB stick to the startup list.

At Win10XPE startup, the bcd loads Bootmgr then applies the boot.wim image in a Ramdisk (WinPE Cache).
Then the system is started from memory, hence the speed in addition to being light and with only the required processes and services started.

But it can't be used like a normal windows, boot.wim image is fixed, modifications or applications install are not preserved, like a snapshot, it's an image.
But with the advantage of remaining intact and keeping the same performance and functionalities.
On the other hand, files created or copied outside X: drive (boot.wim) on the usb key or hard disk are them preserved.

I hope I was clear enough, I am really off topic and unrelated to PB, even if some tools included are written with PB.
Well, the best way to understand is to try. Win10XPE is designed to be simple for users but there is still a small learning curve.

I think it's good to have it at hand, in your toolbox, on a USB key or on a hard drive partition, prepared in advance in case.
You will probably be happy to have it available to repair a future problem on your computer, such as boot problem, unreadable partition, deleted files to recover, malware, etc.

Sorry Marc_256 to have polluted your topic with my ads for my open source project.
I would like to thank again Kyhi, for all the application scripts added and contributions. And not to be completely naive, the Microsoft guys who contributed on some difficult points, without saying where they come from!

[Oso]

Sorry Marc_256 to have polluted your topic with my ads for my open source project.

Indeed, sincere apologies likewise to Marc_256 — I had been intending to go back after finishing dinner, to add a note to my earlier post, as I was conscious of having diverged from your topic. The reason I didn't PM on this, is that I think it's broadly of benefit to other PureBasic forum participants. Perhaps a new thread is in order, at some point?

For PureBasic, there are no additional dependencies to add, it works very well out of the box on a very light, minimal configuration, proof of its strength and efficiency.

That means then, that if boot.wim is volatile on reboot, it is necessary to install any applications needed, during the creation of the ISO? I can still see that the tool has some very important benefits — network appliance services being a prime example, where we don't want the O/S to be changed or updated, nor for any automatic reboots to take place.

[ChrisR]

That means then, that if boot.wim is volatile on reboot, it is necessary to install any applications needed, during the creation of the ISO?

Yes, that's right.
However if you keep the building folder, you can individually run new application scripts to add them on the previously constructed base. Then simply recreate boot.wim and ISO, using a button provided in Create ISO script.
And you can also add portable applications copied directly to the USB key or HDD, a lot of them can work without the need for additional dependencies.

For the record, the 1st build is a little slow with registry preparation, drivers, application download,... but all this is cached for the next build, which will be much faster.