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

WKjun

New Member
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
 

Attachments

  • error_CumUpdateNet48integration.png
    error_CumUpdateNet48integration.png
    4.8 KB
  • error_ChangingFeatures.png
    error_ChangingFeatures.png
    10.9 KB
Last edited:

WKjun

New Member
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.
 

Attachments

  • 2020-10_with_KB4579311.xml
    4.8 KB
  • 2020-10_without_KB4579311.xml
    4.7 KB
  • NTLite_with_KB4579311.log
    10.3 KB

WKjun

New Member
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.
 
Last edited:

nuhi

NTLite developer
Staff member
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

New Member
Greetings! :cool:

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. o_O
 

Attachments

  • 20H2_NTLite.log
    7.1 KB
  • 20H2_features.xml
    4.4 KB

WKjun

New Member
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... :eek:
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

Well-Known Member
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

NTLite developer
Staff member
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.
 
Top