Jump to content
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. ×


  • Posts

  • Joined

  • Last visited

  • Donations


About sanszajnrege

Profile Information

  • OS
    Vista Ultimate x86

Recent Profile Visitors

1,382 profile views

sanszajnrege's Achievements



  1. To mess with the WIM images of Longhorn alphas, you have to find early versions of XImage - 4007 and 4050.
  2. Disc burning or mounting software: DAEMON Tools Pro v7.0 ($$$, CS) - last Vista/XP supported version UltraISO ($$$, CS) - still supported Multimedia: PowerDVD 15 ($$$, CS) - last supported version DVD/BD rippers: AnyDVD HD ($$$, CS) - still supported DVDFab ($$$, CS) - still supported
  3. KB4019204 -> KB4022887 correct me if I'm wrong, but I'm checkin' the M$ Catalog page and found only one supersedence. Installing all of them will be so painful.
  4. You have to download and install manually the compatibility pack SP3 updates for Excel and Word: KB3191897 and KB3203438 (valid as of July).
  5. Actually, it's not true. You have to install only four updates (five, if you have got IE9), to speed up the process: KB3205638; KB4012583; KB4015195; KB4015380; KB4014661 (IE9) If you have the Office 2007 or 2010 you have to install another four updates: https://answers.microsoft.com/en-us/windows/forum/windows_vista-update/why-has-vista-stopped-automatic-updates/42c98c78-157b-44b7-858a-3ba92933cb90?msgId=9366cc04-59d6-4b37-bee9-dffcdc7c602a
  6. No, it's impossible in that way. The licensing system on NT6+ is token-based not the registry. You can only swap the tokens.dat with Server 2008 one, but you will end with entirely Server 2008 system (for example no MCE). Anyway, it would be too much hassle to swap it just for updating. Generally speaking, by switching the tokens.dat you can go from and to every system edition, at least theoretically (the branding will stay the same as the base edition). That's how the early "activators" worked (preactivated tokens.dat from Ultimate edition copied to any SKU).
  7. Thanks for your comprehensive reply. Nothing more to ask. Looks like I've got newest version from WU, since I was April-then up to date. So it should be 4.6. Regarding the superseding thingy, probably the kernel update superseded earlier one. I have to study it myself or with some guy from M$ forum. It's important if it comes to proper working of WU (you know, to reduce the checking for updates amount time). I'm curious if the Server 2008 kernel updates affects the WU also, when it comes to update after reinstalling system.
  8. Digital audio workstations: Avid Pro Tools 10 ($$$, CS, UNS) - despite dropping support of XP/Vista from 9 onwards, both 9 and 10 versions can be installed - 9 as far as I remember without problems, but PT10 requires editing MSI file in Orca. Just find the Avid Pro Tools.msi in the installation folder (it's hidden maybe, I don't remember) and fire it up in Orca. Search the LaunchCondition section and delete something like "VersionNT >601...". You can also delete the RAM limitation memory check, it starts something like "PhysicalMemory>=1024" or 2048. Pro Tools notifies itself about less than 2GB of RAM at launch, but that trick allow you to install it on lower amount of memory. Probably newer versions doesn't work, since they have an audio engine rewritten and 64-bit only. I've got Vista 32 so I'm not able to check. WARNING! Avid Virtual Instruments 10 doesn't work on Vista and lower. Probably it's due to the newer version of Windows Installer. Removing entries from LaunchCondition changes nothing. Audio editing software: Sony Sound Forge 11.0.272 ($$$, CS, UNS) - it's the last version of the Sound Forge working on Vista officially. However, I haven't tried newer builds, maybe there is a way to install it. Multimedia: Winamp (FREE, CS, UNS) - it hasn't been updated since few years, but there is a unofficially patched latest official version fixing some bugs. You can obtain it from the Winamp forums: http://forums.winamp.com/showthread.php?t=374929 Most likely the last one. ;( More software will be added later.
  9. Does the 4.5 rollup update contain the updates for 2.0? Or they have to be installed separately? And is much difference between .NET 4.6 vs 4.5? Does it make greater compatibility of software of what? It's good to have these updates working on Vista, as it should be expected. Now we have to maintain which updates are superseding earlier ones, next month.
  10. Oh man, I've tried only one update, someone from the newest 4xxxxx range. Why should I try everyone cause EVERYONE are so far not edition dependant? Especially for you: Security Update for Windows Vista (KB4012598) windows6.0-kb4012598-x86_13e9b3d77ba5599764c296075a796c16a85c745c.msu Security Update for Windows Server 2008 (KB4012598) windows6.0-kb4012598-x86_13e9b3d77ba5599764c296075a796c16a85c745c.msu Security Update for Windows Vista (KB958623) windows6.0-kb958623-x86_e1a442325f78b4b2f61367af47848f189ac64210.msu Security Update for Windows Server 2008 (KB958623) windows6.0-kb958623-x86_e1a442325f78b4b2f61367af47848f189ac64210.msu The first one is one of the newest, and the second one is one of the oldest. Notice that some kind of checksum at the end of filename? It's bit to bit IDENTICAL. Why should I try every update released since all of them are the same? Do you think that M$ would do any changes just to screw few people installing Server 2008 updates on Vista? I'm not (look Server 2012/8 case). Once again, I mean only security updates. You now, we're all guessing now. We should just wait. Powershell 3.0 is not so important thing, I even don't know what is it for. Everything goes about security updates.
  11. The Powershell 3.0 is screwed up at me. Firstly I installed it on Server 2008 SP2 it gave me not applicable error. Later I installed Powershell 2.0 and then tried to install 3.0, and it gave me the same error. How you can install it on Server 2008? Do I need a platform update?
  12. You're right. I made a test with replaced tokens.dat with Server 2008 Std one. After that I tried to install Powershell 3.0 and it showed me: "This update is not applicable to your system". So yes, if Microshit deletes the client files from update files we're out of luck. Probably the MSU has some integrity check or something like that and it would be impossible to trick it to install. Maybe it would be easier to edit some system files, but who would do it? I think that the Powershell 3.0 is the exception since it probably wasn't meant for Vista, that's why it has Server 2008 only settings. In my opinion security updates should have it all in right place - would it be affordable to them to change now the MSU structure just to screw 1% of Vista users? They even aren't doing anything to stop XP users from using POSReady updates and the XP userbase is still larger. Looks like the tokens.dat change would be only useful to handle Server 2008 updates by Windows Update. And it's only a temporary solution, since as I said before, it changes components to the Server ones (it also enables Shutdown Event Tracker for example). So you know - change tokens.dat -> update the system -> restore original tokens.dat. I'm under impression how the NT6+ systems are componentized and interchangeable each other.
  13. I tried only one, but if you look at the files at Microsoft Catalog, they are the same for Vista/Server 2008, so yeah it has got files for both client and server. You're right, if they delete the client files from cab inside the msu, our only hope is to switch tokens.dat to Server 2008, so it is nothing more than using Server 2008 (without MCE for example). If they didn't remove the client files from updates for 8/2012, they shouldn't do that in Vista/2008. You know, Server 2008 gets only security updates, so it is not edition specific. Apparently the applications are checking some licensing values. I'm not a hacker, so I can only guess, but there is a Kernel-ProductInfo entry in tokens.dat which specifies edition (e.g. 1=Ultimate, 7=ServerStandard). We have to just wait, it's only few days remaining.
  14. Server 2008 updates work on Vista. They should work in May also, why not. It would be great to maintain the updates list in Excel or something like this, to take care about superseded and new updates, etc. I had an idea to modify tokens.dat file to make WU updating manually. But modification of the tokens.dat screws the system hardly, I think. It messes with components related to the specific version licensing. Or maybe just update to W7, but I don't have any need to, since Vista is sufficient for me.
  15. As far as I know, the USP4 is only compatible with EN XP. Is there any option to install it on Polish XP? I would like to not download tons of updates after installation of XP SP3, or more of them in XP MCE 2005 SP2.

  • Create New...