Jump to content



Recommended Posts

Using the latest version of nlite ( with my usual build, I noticed several ''issues'' regarding hotfix integration:

1. The latest version of nlite still doesn't support direct integration of several hotfixes.

These updates are: Windows Feature Pack for Storage 1.0 (Imapi and Smartcard), KB974266, KB979099, KB916157 v6, KB922120 v6, KB932716 v2, KB950305 v2, KB967048 v2, KB970326, KB970401, KB971276 v3, KB982316 and the Redistributable Framework Components (KB971286 + kmdf 1.9 - hard to come by, it's included in the archive with all the updates linked above).

2. (request) If some updates from the ones above cannot be integrated directly, please add an option to nlite that enables integrating them (via the ''regular integration method'') without permission from the user / when checked, redundant screens like this won't appear at the final stage of the integration process.

This request is kind of optional - if all the updates from the archive linked above are integrated directly, such an option will be useless.

3. (request) Please add an option to enable the default behaviour of the integration process to directly overwrite files only when a higher version number is present, without user permission.

So, screens like this won't pop up at the final stage of the installation process, and so I won't be forced to press the ''yes'' button at least 20 times everytime I use nlite with my usual build.

If these two requests are implemented, the user won't be bugged at all with pop up screens at the final stage (in ''normal'' circumstances).

4. (question) Do you plan on supporting direct integration for the MSRT tool, or only swichless installers of it at T-13 are ok with nlite? Right now, I get the usual screen when trying to add it to the queue.

5. I use four unofficial updates from the first post from here (no 1 - KB291343, no 2 - KB921606, no 5 - KB2575928 and no 6 - KB2616879). With nlite, the integration process goes smoothly, however with, for KB291343 I get this screen, that is wrong I think - the unofficial updates clearly has a newer version stored inside. Again, this didn't happen with nlite

6. (Optional) From the list Onepiece mentioned here (4th post), with all the updates for windows xp available from Microsoft, I don't use ~ 20 of them, for various reasons. However, maybe some people use them all, so I also tried them once to see how they cope with your app.

KB938720 (legit check .cab) is clearly icompatible with your app, as you can see here, the same as KB282784 (qfecheck - see here) or KB940157 (windows search 4.0 - see here and here).

Again, this one is optional from my point of view, as I don't integrate these, but please investigate either way. Thanks. :)

Edited by Yzöwl
Microsoft Software 3rd party download link removed
Link to comment
Share on other sites

Recently I removed MSN Explorer from Windows XP Sp3 setup. When installing everything went fine. but at the first logon it showed a SFC error.

It asked me to insert the Windows setup disc . (nlite

(before removing MSN Explorer, Installation was fine)

Link to comment
Share on other sites

g-force, yeah I saw that nLite doesn't always save a preset, there are some triggers. That could be done better, let me know if you find a repeatable issue.

RicaNeaga, great report once again, thanks.

#1 I will check.

#2 and #3, all that you requested is the default behaviour if Reports are disabled in Hotfix page advanced options. What are you missing in that scenario, or the option is not clearly explained?

#4 it's in my todo to check MSRT and its GUID extraction if possible, is there another way to integrate it without extracting the GUID (which I haven't yet tried, maybe it's simple)?

#5 oh wow, that is an important find, will look into it.

#6 I will check.

Asrin475, so to replicate the issue I just remove MSN explorer, nothing else checked or selected in nLite?

Link to comment
Share on other sites

So great to see Nuhi's return !! Thanks for the hard work !

Would like to finally see a trully portable version yeah, and as I don't run any .net shit here, would love to be able to get rid of the annoying runtime installation somehow.

Well, at least, the old minimal runtime package still works (nLruntimeR3.exe)...

Link to comment
Share on other sites

Thank you very much for your hard work.

I'm having an issue with the new version. I have an XP SP3 disk with some addons integrated with RyanVM. I've been using the same modified source for quite some time without issue.

Now, when integrating the latest windows updates with the new version of nlite, the process continually fails at sfc_os.dll with an error about being unable to open the file.

Link to comment
Share on other sites

Thanks for the clarifications. :)

#2 and #3 - yes, I don't know how I missed that option (''Display Reports''), but I'm ashamed to say that I did. But yeah, maybe it can be explained better (I think - ''very optional'' suggestion). Again, sorry for missing it. :D

#4 - Please consider checking xable's update pack for two reasons. One - he has managed to slipstream MSRT inside his updatepack, maybe it helps somehow. Two - if you choose to make your app to directly integrate MSRT, please check it will be compatible with xable's pack. Of course I'll firstly add his pack in the integration queue and then ''overwrite'' the MSRT with the newer one (during the nlite integration process), but it's likely that two MSRTs would generate issues. Again, please check it, as I'm sure there are many xable's updatepack users out there, that use it with nlite.

Thanks again. :)

Link to comment
Share on other sites

Could you please upload to your site a portable version of nlite? Just a ziped one without installer.

I can't remember did Nuhi actually create those old portable nLite's or were those fan creation only available from the interwebs ?

Link to comment
Share on other sites

I can't remember did Nuhi actually create those old portable nLite's or were those fan creation only available from the interwebs ?

A portable self-extracting archive was provided on nliteos.com until nLite was released. The latest snapshot by the Wayback Machine that shows the archive is from 2013/08/06.

Edited by 5eraph
Link to comment
Share on other sites

I don't know if this classifies as a bug but when I remove every keyboard except the one for my language the following keys and files for extra US-based keyboards are not removed:

"HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00010409""HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00020409""HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00030409""HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Keyboard Layouts\00040409""C:\Windows\System32\KBDDV.DLL""C:\Windows\System32\KBDUSX.DLL""C:\Windows\System32\KBDUSL.DLL""C:\Windows\System32\KBDUSR.DLL"
Edited by Francesco
Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...