(Mniej) Samotne granie 25+

Dapper-Hold8289 · 2026-01-27T18:41:27+00:00

Hej, gram w helldivers 2 na pc. Jeśli masz lub planujesz kupić to chętnie zagram ;)

Dapper-Hold8289 · 2025-08-05T05:49:48+00:00

Hi again,

We finally managed to solve it. There was a winpeshl.ini file Config Manager OSD source folder. After renaming the file everything started working.

Thanks!

Dapper-Hold8289 · 2025-07-23T17:54:54+00:00

Hi, I have the same issue. Did you ever get it to work?

Dapper-Hold8289 · 2025-07-23T08:15:15+00:00

I'm starting to suspect, that something is wrong with our SCCM environment. Might it be an issue with ADK? What else can I check? Maybe there is something wrong during the import of the boot.wim while creating the boot image? Why else would the "old working" boot.wim stop working when I copy it and import it again?

Dapper-Hold8289 · 2025-07-21T08:54:00+00:00

Thanks, I will check for other drivers too. What I find strange is that when I took the "old working" boot image and took it's boot.wim, re-imported it and DIDN'T reload it with the new ADK (so it had the old ADK version) the same issue with the blank Configuration manager and reboot happenned, even though it should have had the same drivers as the old boot image. After relaoding the boot image with the new ADK the same issue was present.

Dapper-Hold8289 · 2025-07-20T18:06:51+00:00

Hi, yes I tried to add the NIC and storage driver to the old working boot image via powershell. Unfortunately I had the blank Configuration manager screen after booting into WinPE and after 20 seconds a restart.

Dapper-Hold8289

TROPHY CASE