'Incorrect function' error since KB4579311 for 2004 & 2009 "20H2"

[WKjun]

Hello!

First of all I want to thank you for your excellent work! I'm a regular user of NTLite - and I have got a license too.

See #3 for a clear and compact description of the situation where integrating the latest update breaks changing of features and integration of the .net 4.8 cum. update, while processing a fresh Windows 10 Pro x64 2004 wim file.

In #4 I report that it is persistent in Windows 10 Pro x64 2009 (20H2), without integrating anything.

Best Regards,
Wilhelm

 

[George King]

Can you please upload used preset? So we can review whats going wrong.

 

[WKjun]

To make it simple, I've made a clean install and a new preset. It is all about the cumulative update KB4579311 - without it everything works as it should.

"without" preset:

• enable & disable some features
• Servicing Stack (2020-09)
• .net 4.8 cumulative update (2020-10)
• .net 3.5 (sxs)

"with" preset:

• same as above with cumulative update KB4579311 (2020-10)

Results can be seen in corresponding logfile.

 

[WKjun]

It is the same problem with version 20H2 (2009)! Ever since 2020-10 cumulative update, which is already integrated in the latest ISO, NTLite cannot enable/disable certain features anymore.

 

[nuhi]

Hi,

thanks for reporting, but I cannot replicate, better than that I have a theory.

Your .NET 3.5 CAB may be wrong, see the log:

19.10.2020 17:44:16 Integrating: .NET Framework 3.5 (includes .NET 2.0 and 3.0)
19.10.2020 17:44:35 Integrating: KB4578968 - .NET Framework Update
19.10.2020 17:44:44 Error 0x80070001 '[1] Incorrect function.' KB4578968 - .NET Framework Update

It means all after .NET 3.5 is already questionable since the first update after it already has the issue, and since you pull the .NET CAB from a custom SXS folder, might be from old Windows.
Please repeat all using a fresh image, load your preset, remove .NET 3.5 CAB, use Add - Template - .NET 3.5 so the tool pulls the correct one from the image.

Then try that, should work.

 

[WKjun]

Greetings!

Thanks for examining my situation. I always take the .net 2.0/3.0/3.5 SXS from the appropriate ISO. If I integrate cum. update 2020-09 it works. With 2020-10 it does not. I've even extracted the files once more, just in case.

The more important thing for me is the feature setup. I've attached a new log and xml. Here I just enable or disable certain features as before, without integrating updates or changing anything else. It is the ISO of Win10 2009 (20H2) where the 2020-10 update is already included. And it leads to the very same error, as if MS has changed the names of its functions which are now no longer recognized by NTLite.

 

[WKjun]

I have news (case can be closed):

I'm weirded out! On an ancient Windows 7 x64 machine I was able to change features for the Windows 10 x64 (2009) image...
Never would I have expected my PC to be the fault, because previous versions/presets still work. No wonder no one else reports this. If I had experienced anything problematic that would suggest a local problem with my Windows installation (or whatever it is), the first thing I ever do is to test it on another machine.

I still wonder what could cause this. The only thing that's different from the years before, where I did never upgrade, but reinstall the OS, is the upgrade from 1903 to 1909.

Well, whatever. Thanks for your time and excuse my poor troubleshooting capabilities for once.

 

[Kasual]

I still wonder what could cause this. The only thing that's different from the years before, where I did never upgrade, but reinstall the OS, is the upgrade from 1903 to 1909.

Well, whatever. Thanks for your time and excuse my poor troubleshooting capabilities for once.

Seems like KB4579311 (Ms) doesn't support old hardware anymore.

 

[nuhi]

Well, MS is allowed to have bugs as well, give it time, they'll fix it.
Ping us if it's solved with the next cumulative.

 

[WKjun]

Greetings!

Finally I have found out what caused (and still causes) all this:

ImDisk RAM drive is in use only on this machine for temporary files and to play around. Using it for Temp & Scratch causes integration to fail for .net Framework 4.8 updates as well as disabling features. Switching to a regular HDD or SSD path everything works!

Knowing that in conjunction with the fact that it worked for months (or years) that way, something has changed.
What I cannot recall is if it was an update of ImDisk, NTLite or even Windows.

The configuration of the RAM drive itself has not changed. It uses NTFS or else NTLite would find fault with it not being NTFS.
Although it is not a huge backdraw for me, it was the main reason to put in 32GB of RAM into my machine. :/

If I find the time I may try another vendor, like Radeon RAM Disk, which I have used some years ago.

 

[nuhi]

Thanks for the info.
Do you by a chance have a not-activated Windows?
Asking as I had a similar issue when I used a RAM disk and ran out of space, because Windows silently locks to 16GB if not activated, making the RAM drive fill up earlier than expected.

 

[WKjun]

Thanks for your info too!
In fact you are right, mine is not activated. To my knowledge Win10 is just limited in personalization and task bar customization, not technically in any other way. On the other hand I have no issues whatsoever filling up the 24GB RAM disk with other data and NTLite just needs about 10GB of it anyway, which would make even a 16GB limit sufficient.
Do you still know which RAM disk you have used back then?

 

[nuhi]

ImDisk as well.
Weird I cannot find any documentation about trial vs activated Windows memory limit.
I clearly remember having the utilized memory stop at 16GB and then started activating my license (thought that it will quickly get flagged due to my reinstalls, but it doesn't).

The way I tested the limit back in the day was to create/copy ISO files to the RAM drive.
Now I can fill up as much as it is sized, while when it was not activated, it would run out of space before it would make sense by looking at the Explorer reported sizes.
Then I did find info on it, and activated, but now for some reason Google-foo is failing me.
Only found that Win7 Home is limited to 8/16GB always, here, which is also good to know, they don't mention activation on that page.