MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.

If you have DEP selected for "all programs and services" (not the default), then you might have to exclude StartIsBackCfg.exe from it. I believe this was mentioned early in the development, but as users have to manually change from the default DEP setting to this, it would probably be considered "normal" behavior to have to exclude it from DEP if DEP isn't set to the default "for essential Windows programs and services only". It just strikes me as odd for any program developed in this day-and-age to crash when subject to DEP. I mean, as you say, I can exclude it, but it's a really bad coding habit to slide into. Check DEP. Check ASLR. This stuff should be enabled on everything you do as of at least five years ago.

Having integrated an Intel graphics driver into my nLite Windows XP DVD I am prompted during my "fully automated" setup whether I wish to connect to Windows Update to look for drivers for my monitor. Is there any way to setup an answer in advance so this prompt does not occur?

In the case of the former because I couldn't find the affected versions list. In the case of the later because while I suspected I didn't need it, I couldn't see any harm in doing so to be on the safe side. If it's not needed then it will never be installed. After all, going by versions I wouldn't include the v6 WMP patches, but I do believe they're relevant even post-WMP11.

I'm sure I'm not the only user who uses WUD in onjunction with nLite. Combining WUD, DriversPack and nLite allows me to create fully patched Windows DVDs with automated setups and most of the drivers I will need for any build. However, nLite can only integrate standard hotfix packages as those support a fixed set of options which allow them to be slipstreamed into the build, where as WUD doesn't differentiate between a hotfix and anything else, or even hotfix dependencies. This can lead to situations where you will slipstream hotfixes for a tool which didn't ship as a hotfix and thus couldn't be slipstreamed. What would be desirable was if WUD understood the difference between a hotfix and "everything else", and even knew when a hotfix was dependent upon a non-hotfix, then gave you the option to filter those out of your download. Sounds painful to implement to me, but it would certainly make the whole WUD/nLite relationship much more useful and far easier to use.

One of my favourite things about nLite is its ability to slipstream hotfixes. Of course, collecting these is a pain so I'm sure I'm not the only one who grabs WUD (also hosted on these forums) to download them. The problem is the two don't really work all that smoothly together. WUD doesn't differentiate between a hotfix and any other kind of download, like a tool pack or a standard executable install, while nLite doesn't handle an error in passing switches all that gracefully. What I would ideally like to see is a situation where, when nLite asks me what hotfixes I wish to slipstream, I can simply point it at a directory (not files) and let it recursively work its way through the directory, silently ignoring anything which isn't a hotfix package. This would certainly make this feature a lot more useful, or at the very least, friendly.

My organisation currently using Squid 2.6 STABLE 16. Squid 2.6 has two modules which ship with it, mswin_check_lm_group and mswin_ntlm_auth. The former is used to confirm the received user is in a specified group, be it domain or local, while the later allows for authentication using NTLM/NTLMv2. When a user attempts to connect to a page the credentials of the logged on account are requested by Squid and then authenticated using NTLM via the modules listed above, checking both password and group membership. From what I can see, WUD doesn't have any support for NTLM, so Squid rejects the connection as the authentication attempt fails.