In that case, perhaps the discussion should be continued in the other thread that you started.Markus wrote:it seems to be happening with only ryans too..
Mods: split and merge?
hijamesdean wrote:Did Microsoft update Windows Script 5.7?
Date Published: 8/24/2007
Nope. Check the timestamp of the digital signature on the "new" package. August 1, same as before. The hash is the same as before, too, so unfortunately, it's still the same broken thing.jamesdean wrote:Did Microsoft update Windows Script 5.7?
Date Published: 8/24/2007
Ah, that explains a lot. I think I have an idea of what may be causing nLite to mess this up, but I'll need to test and see.waleed_wwn wrote:But , with Integrator it disappeared
Well, that's the one! I think you're better off asking Xable & co. where the heck they find them.ricktendo64 wrote:I mean what forum/website do you guys hang around at to find them all? (other than TheHotfixShare)
Just delete resetwmi.exe from svcpack after integration (you can ignore the entry in svcpack.inf).armond wrote:If, for any reason, I want to remove the "utility that will clean up any repository corruptions" from your update pack, what things should be remove from it?
First, WMI corruptions happen at random, and most of the time, it does not occur. So just because you haven't seen it yet doesn't mean that it won't affect you some time in the future. Second, there is no harm whatsoever in running resetwmi.exe; if there was a problem, it will fix it, and if there wasn't a problem, it won't mess anything up. It's only 1 KB, so space isn't an issue either. So there really isn't any point in getting rid of resetwmi.exe...I'm asking because I did not have any problem with your previous versions.
regardscode65536 wrote:....... it will modify all the text files like the hives even if no edit was needed (it's mostly cosmetic, I know, but wreaks havoc when I do a diff of two sources to make sure that the cumulative changes made were what I wanted). Yes, I'm a control freak.
Okay, this is only tangentially related, but doesn't it bother anyone else that nLite and RVMI will leave the timestamp of newly compressed files as they are? Windows Setup is dumb enough that it will set the file time of uncompressed files to whatever the timestamp of the compressed version is, which means that, for example, tcpip.sys will be dated to whenever you did the integration instead of 2006/09/26, which, needless to say, wreaks havoc in sorting through system files and comparing that to times that MSKB lists.