Anyone testing Win10 vesion2004 / build19041 / 20H1?

Which would you prefer to do?


  • Total voters
    4

bseklecki

New Member
All:

Redmond released Win10 "may 2020" aka "20H1" aka version 2004 on Monday.

Has anyone run it though NTLite yet?

I successfully performed a build?

How about with a FOD addition: NetFX3 and NTLite was asking for the CABs in updates\10.0.1909.x64.FOD\ , so perhaps I thought a new build of the binaries would be required to RegExp match the version string in the Image WIM?

Figured a new build would be out soon since I assume the NTLite team guys are hooked into the behind-the-scene operation at Redmond :)

~BAS
 

nuhi

NTLite developer
Staff member
NTLite has been tested on Win10 2004 since last year previews, so it's safe.
Of course as usual if you see any issues, let us know before spending time on it.

NETFX3 you can add in the Updates page, Add - Template - .NET, if loaded from a full ISO content.
To avoid that FOD thing, don't enable it on the Features page, use the Updates page as described.

Previews of Windows are public, no special treatment needed :)
 

nuhi

NTLite developer
Staff member
Error 18 is a bit tricky, it means the underlying host Windows WIM engine is broken or blocked.
Here is a lot of info regarding that subject (replies by me, nuhi), let me know how it goes.
 

bigbadmoshe

New Member
Error 18 is a bit tricky, it means the underlying host Windows WIM engine is broken or blocked.
Here is a lot of info regarding that subject (replies by me, nuhi), let me know how it goes.
Don't mind me. It was something on my side. It's a ok now.

Thanks for responding
 

bseklecki

New Member
I tested NetFX3 integration in both places, and concurrently both, without incident during build.
I will run test install results with all three permutations to verify result.

NOTE: Hopefully Rockwell Automation will update their code soon to eliminate the need for this legacy framework.

Native OS: Win10 1809 Pro
Target OS: Win10 1809 EntIOT LTSC
 

Attachments

Top