tomasz86

This is a workaround but can't you just prepare the shortcuts in advance (using system variables)?

Well, I had problems with the ntdll.dll starting from v9, on real hardware too (check #533).

I've also done some investigation and the fact is that M$ never uses quotes when referring to %systemroot% in their updates so it can be said for sure that %systemroot% can't have spaces

I've just done more tests and actually the same problem happens with both v10 and v11. The test machine is a VM (uses uniproc non-PAE kernel) with all official updates installed. I just added KB2479628 and KB2393802.

I've just tested it and this is normal system behaviour. It has nothing to do with unofficial updates

I'm not sure what you mean here. I don't think there's anything in UURollup which would cause such behaviour. Could you provide some screen shots to show what the problem is exactly about?

New test version of UURollup-v11 is ready. I've added dnsapi.dll 5.0.2195.7283 iphlpapi.dll 5.0.2195.7101 from the new version (v7) of WildBill's KB2508429.

...and the MSXML files themselves are actually language neutral

Thanks WildBill Is the ntdll.dll version same as in v10? Edit: Something seems to be wrong in the new ntdll.dll Explorer.exe restarts itself each time when trying to open a folder.

The difference between Firefox and Opera is that in case of Firefox they at least provided a reason for dropping Win2k support (using VS2010 to compile Fx) while in case of the current snapshot of Opera 12.50 it's still compiled in VS2008 and can be easily made to work in Win2k without even using any unofficial kernels. They didn't say anything about why they had decided to drop Win2k support.

The idea is good but is it 100% safe? I've had my data corrupted several times when I disconnected a USB HDD without using the safe removal option.

I'm using it right now and all fonts are shown correctly. The file is atmfd.dll 5.1.2.232.

I meant the Windows directory. %ProgramFiles% can have spaces ("Program Files") but I don't think that the Windows directory can.

The HAL shouldn't matter. You can change it manually in the Device Manager. Just remember not to switch between an ACPI and a non-ACPI one because this will break the system.

It's good to know that the solution worked By the way, has anything changed about the blank icons problem you described last time? I think the glitch is caused by mixing WildBill's 32-bit icon support with BlackWingCat's shell32.dll. If it is so then there are two ways of "fixing" it: 1) Bring back WB's shell32.dll. I wouldn't like to do it as the BWC version adds many useful APIs not present in the WB one. 2) Remove the 32-bit icon support, i.e. use comctl32.dll from XP and win32k.sys from BWC. I'm also not sure about this way of solving the problem but at least we don't lose any functionalities due to it (we can rather gain some more APIs thanks to the XP's comctl32.dll).

The problem happens both in the older and the newer version. Can't just the XP file be used as it is? OTF fonts open properly with the XP atmfd.dll from KB2507618 installed.

@Mim0 Thanks for keeping this updated By the way, I can host this and provide direct links which won't change even if the cab is updated. Please let me know if you're interested.

Can %systemroot% contain spaces?

I've just uploaded a new test version of UURollup-v11. There are too many issues in the current BWC kernel. In the yesterday's version of UURollup there is a bug which breaks Silverlight. I've tried all my best to fix it but couldn't get through it. Until this problem and other issues (see the main topic about BWC kernel) are fixed UURollup will use WB kernel. In the today's version of UURollup-v11 WB kernel is used and I've added one more update to it - KB2603381. It's no longer required to slipstream it separately. Edit: By the way, messing too much with system files can sometimes bring unexpected results

@WildBill There seems to be a bug in atmfd.dll from KB2507618:

Confirmed. The WildBill's atmfd.dll 5.0.2.231 is buggy. The problem will be fixed in the next version of UURollup. If you want an instant fix then download KB980218, unpack it and manually replace your atmfd.dll from %systemroot%\system32 and %systemroot%\system32\dllcache with atmfd.dll from the update. You can use Replacer to easily replace system files. Edit: Actually the XP file seems to work correctly too. I'll probably include it in the next stable version of UURollup.

You should ask them, not me Actually, in the new test version of UURollup-v11 almost all of the kernel related files come from BWC. Only ntdll.dll is still WB.

@jvidal Because the update can't be slpstreamed from HF It belongs to HFSVCPACK_SW1. Using the reg file is faster and saves space. The registry entry is not "%systemroot%\system32\packager.exe". It reflects your real system path so on my system it is: C:\WINNT\system32\packager.exe for other people it may be C:\WINDOWS\system32\packager.exe that's why it's necessary to use "cmd /c reg.exe" to get the real value for %systemroot%

Anyway, how about getting Win7 SP1 explorer.exe from this hotfix? http://support.microsoft.com/kb/2444677 x86: http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix347291/7600/free/425222_intl_i386_zip.exe (1.2 MB) x64: http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix347291/7600/free/425225_intl_x64_zip.exe (1.7 MB)

@acus Thanks for testing. Actually, in case of UURollup what's more important than the installation process itself (which is not very complicated) is how programs work with it, whether any unexpected problems occur, etc. I do know that it's very difficult and time-consuming to test all these things though. You did your test with IE5 installed, right? @PROBLEMCHYLD A piece of advice is always good, no matter whether I agree with it or not I know that switching between the kernels is not an ideal situation but what can I do at the moment? Leaving the original kernel would block all applications compiled in VS2010 so I can't even think of doing that. It would be the best if there was only one unofficial kernel but the reality is different so I cannot do anything but adapt to the current state of affairs. WildBill's kernel was used from the beginning but at the moment BWC kernel is more developed so I think it's a proper moment to make a switch. In the end the number of packages is going to be reduced but now I just must update UURollup to keep up with all the changes. If I left it like this then everything would be very difficult later when a lot of changes are to be implemented at once. It's much easier to add them one by one when BWC/WB update their files and new XP/2K3 (2K compatible) updates are released. I'm going to start with adding the official updates to USP5.2 and then the unofficial ones but in the end it's going to be only one package. I don't want to make it fragmented so I do not plan to prepare a separate version with official updates only. If someone wants to use only official updates then using Windows Update or installing Update Rollups 1+2 will probably satisfy them while USP5.2 is for people interested in having everything including all official/unofficial updates and all other optional components.