Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. 


  • Content Count

  • Donations

  • Joined

  • Last visited

  • Days Won


mike_shupp last won the day on October 30 2018

mike_shupp had the most liked content!

Community Reputation

31 Excellent

About mike_shupp

Profile Information

  • OS
    Vista Ultimate x64
  • Country

Recent Profile Visitors

521 profile views
  1. So what's new and exciting these days at Microsoft? Windows 10 version upgrade woes? Oh those are old and rancid! What concerns US? What's waiting in the Windows Update Catalog? Well, here are some updates for Windows Server 2008 R2, which is maybe officially for some neighbors of ours, but which we might quietly appropriate and enjoy as well ... KB4488661 NET Framework 2.0 update KB4488666 NET Framework 4.6 update KB4488869 NET Framework 4.52 update KB4489873 Cumulative Security Update for Internet Explorer 9 KB4489876 Security Only update for March 2019 KB4489880 Security and Monthly Quality Rollup for March 2019 KB4489489 Security and Quality Rollup for NET Framework 2.0, 3.0, 4.5.3, and 4.6 -- contains KB4488661, KB4488666, KB4488869, plus the old regulars mspatchregfix, KB3078602, and KB4020478. Not so much to shout about actually, since MS's shoving what used to be a half dozen or more patches into one "rollup" . Oh well. One more minor thing, I'm expecting to move very shortly, and my internet interfacing may be a bit ... irregular... for a time (my beloved PC will be in a box in a storage cubicle for a couple of months unless I'm damn lucky, I'm trying to say). Granted, I haven't been doing anything really essential to GreenHillManiac's operations, so I expect things to continue smoothly. But if anyone is curious about my sudden silence , that'll be the reason.
  2. We have two more Win Server 2008 updates this week at the Microsoft Update Catalog: KB4486459 qualifies as an EXTRA -- it brings the latest Chilean time zone changes to your system KB4490514 provides capabilities that I would have thought had been in last week's updates -- there's a fix to re-enable databases using Access 95, plus a fix for virtual machines which fail to restart properly after a save operation (I don't know if this for VMs in general or just for those employing Virtual PC 2004 and VPC 2007; I suspect it's the latter case). Also, the curious can find previews of next month's NET (KB4486546 and KB4487259) and Monthly Quality (KB4487022) Rollups. And now back to sleep for a couple of weeks. Zzzzzzzz .....
  3. Very nice! You got it all. Now I can sleep in without feeling guilty!
  4. Well .... the need for this patch is a bit unclear, let's say. As originally presented, this was a fix for a problem created by KB4480970, the January SMQ Rollup for Windows 7, namely that users accessing other PCs by way of the SMBv2 protocol might see difficulties. (Vista and Win 7 users, in other words. Windows 8 and 10 users would use SMBv3 by default, and not have problems). The suggestion of the knowledgeable folks at www.AskWoody.Com was to bring up the CMD line interface, enter "reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\system /v LocalAccountTokenFilterPolicy /t REG_DWORD /d 1 /f", then exit and reboot the system. A one line registry fix. But some of us have qualms about fiddling with the registry, even with things that look simple and straightforward. (That includes me actually, so I'm not being particularly snide. I've never seen a reasonable account of how the Windows registry is set up. It's obscure and mysterious, and I've come to think Microsoft wants this to be the case.) Anyhow, KB4487345 is a MS hotfix that implements that registry change. It takes a 30 megabyte program file to add one line, with under a hundred characters, to the registry, and that's all it does. Okay. This tells us something about modern programming skills I guess, or maybe something about the efficiency of modern compilers. Or something --- a programmer in the 1960's-1970's era would be on the floor moaning at that 30 MB monstrosity, which could have been coded in about 150 characters in machine language. (I'm an old-fashioned guy, if you haven't figured this out yet.) Anyhow. This seems to be a rather low priority fix, since MS isn't shoving it off onto everyone as a routine update, but just keeping it as an optional thing at the Microsoft Update Catalog. The implication is that most of us will get by happily without the fix. thus my suggestion that it be treated as an "Extra." But I don't make the rules here -- I'm a scout., a PFC at best. GreenHillManiac set up the database, so he's the officer in charge.
  5. Okay, one more update as of mid-month. KB4487354, a hotfix for those who have already updated with KB4480968 or KB4480957. Quoting Microsoft: "This update resolves the issue where local users who are part of the local “Administrators“ group may not be able to remotely access shares on Windows Server 2008 SP2 machines after installing the January 8th, 2019 security updates. This does not affect domain accounts in the local "Administrators" group." There is a similarly numbered patch at the MS update Catalog for people running Windows 7. I.e., if you're running Vista and discover you can't download files from another PC running Vista, or can't upload files, this patch may fix things. Or it may not not. Or maybe just as well, you might uninstall KB4480968 or KB4480957. Or maybe wait to see if the fix is added to next months Security And Quality Rollup. Of course this problem isn't really likely to happen, but ... We're not dealing with certainties here, but if you've just got to have EVERYTHING on your Vista machine as soon as possible, you'll want this patch. Otherwise ... I'd classify it as an "extra." Not my call actually. This is where I take a step back and give my best salute to GreenHillManiac. I'll trust his judgement.
  6. Wa-hoo! I'm impressed, that looks a lot more professional than what I've been throwing up. So I'll sit on my hands once more, thank you! And to backup your cautionary note, it seems Microsoft has already pulled 4 updates for MS Office 2010 this month. and found an error in the Win 7/ Server 2008 R2 monthly security rollup package less than a day after posting. Sad to admit, but 2019 looks unlikely to be The Year Things Went Perfectly For Microsoft. So sorry, people in Redmond.
  7. Tamris: Dude ... Lady? ... Do not express your qualms about being understood in a language that's not your native tongue. YOU'RE DOING FINE. First of all, we're dealing with a shared interest --- keeping Vista going on our PCs -- so we can all grasp the intent of someone's post here even if the words and syntax being used are not the best of formal English. Secondly, if you actually lived in an English speaking environment, surrounded by people who speak that language and none other, you'd quickly notice that most "native speakers" are not orators or authors. They wave their hands about, they say some words loudly and let others fade into silence, they throw meaningless phrases like "you know" and "I guess" and "you all" and "What about her emails" into conversations to fill up gaps, they mispronounce words that most high school graduates should be familiar with, their spoken vocabulary is small. Most English speakers are just ordinary folks, not expecting to do much with their use of the language, and -- surprise! -- not doing much with it either. Third. you're doing fine and you're surrounded by people doing fine. Nobody in this discussion thread or, as far as I've noticed, in any of the MSFN discussions I've followed, has used English here in any way whatsoever that would be noticed by ordinary Americans, Canadians, Britons, etc. YOU ARE ALL DOING FINE. Really, the only person here who needs feel some embarrassment about his impoverished language skills is me. I might get along talking to a five year old German kid or a two year old French infant, but we'd be limited to talk about liking sauerkraut and potatoes and taking naps rather than running personal computers. Let me say it again. YOU ARE ALL DOING FINE.
  8. Nah, it's new. Just released today or yesterday, so there's no way you could have spotted it last week -- unless you're a MS test engineer. So, you got it, and you can pat yourself on the back for posting here about it. I'd do it myself if I were capable, but reaching from San Francisco to Poland takes a bigger arm than I've got! But thanks!
  9. Nicely done, and thank you! My only quibble is with KB4471984, which I suggest ought to be described as KB4471990 was, to show it contains the three security only npdXX files. Also one addition: for those who demand everything, the December Malicious Software Removal Tool, KB890830 is out there at the MS Update Catalog as well. (It's easily overlooked, as the same file apparently works on Win 7 and Win Server 2008 R2 as well.) As for this being "my job" ... well, no. The thing is, I'm multi-booting on this system with Win 10 v1809. Win 10 v1803, Win 7, and Vista. And for most of this year, since the unveiling of the Spectre and Meltdown vulnerabilities, it's seemed sensible to keep control of system updates in my own hands rather than trust MS system updates to make everything right automatically. To do that, I have to go out to the MS Update Catalog site at least once a month and see what's there. Since I'm looking at updates for three operating systems, adding a fourth is no big deal. And then I might as well share what I've learned with other Vista users, who are by definition compatriots .... and if I screw up, as alas happens now and then, we've all got GreenHillManiac to chomp down on that big cigar and set things right! What else? There are updates aimed specifically at .NET 3.5 this month, which is kind of ... unusual. Unusual enough that noting them specifically is probably worth doing. Generalizing wildly, some .NET patches conflict with others, and some don't. Specfically, there are a batch of .NET 2 patches, generally with names like WINDOWS6.0-KBXXXXXXX- .... MSU, that everybody ought to have on their system (or at least try to have; some of these get obsoleted and won 't install). There are some .NET 3.5 patches, named NDP3.5xxxxx or such, and they ought to be installed. Then there are .NET 4 patches, an unholy mess. These last have numbers like 4.0.X, 4.5.X, 4.6.X, and 4.7.X. The 4.0 series is aimed at Win XP, I suspect. People with 4.5 and 4.6 versions of .NET can't use the 4.0 patches. People with 4.5.0 can install 4.5.1 patches and 4.5.2 and so on, but not 4.6.X or 4.7.X patches. However, people with 4.6 can install 4.7 patches -- in fact folks at MS sometime seem confused, and you'll get something described as a .NET 4.6 patch at the MSUC site which refers to itself as a .NET 4.7 patch during installation. Hmmmm. I seem to have made a post here even if Tamris did do the heavy lifting this time. Christmas season, I recall, and this was a present. Thank your for the lovely gift, Tamris!
  10. I've got two Vista Ultimate installations, both updated with Server 2008 SP2 patches, and both show the 11.0.6002.24483 version number you have. Looking at some other files in the WMP folder, things with 11.0.6000.xxxxx numbers date back to 2006, when Vista first appeared. Things numbered 11.0.6001.xxxx go back to 2008. The setup_wm.exe file I'm looking at is numbered 11.0.6002.18111 and dates to 2009. For comparison, Win 7's WMP has some file version numbers starting with 6.1 (and some with 12.0.) So my suspicion is that the 600N thing was Microsoft's pointer to "Windows Vista Service Pack N" So your later WMP file number (and mine) came from one of those Server 2008 updates. Well. that was the whole point of patching in the Server 2008 stuff -- to get the updates. So now you've shown it works.
  11. Click on START. Enter REGEDIT in the box. In the Registry, seek out "Software\Microsoft\Internet Explorer" and delete any entries to "OSVersion" . Then save and exit and start up the browser. Go to Internet Options, then hit Advanced Tab, slide down to Security. Make "Use SSL 1.0" thru "Use TLS1.0" boxes blank, check "Use TLS 1.1" and TLS 1.2. Save and restart the browser. These are security settings used by websites over time. SSL got beaten by malware and thus has fallen out of use. TLS 1.0 was the default for Vista and others for a long while (it goes with those "http//" URLs), but has been obsoleted by TLS 1.1 and now TLS 1.2 (all those "https//" URLs that Vista couldn't open). You may find that options for 32-bit and 64-bit IE9 are different, that TLS 1.1 and 1.2 appear for one browser version but not the other. Alter the one that you can, and try to remember to use that browser. Another happy note: TLS 1.3 is due to appear shortly; I've no ideas as to whether Microsoft will fit that into IE9 (or IE11). There are a few other browsers than IR9 that work with Vista fortunately.
  12. Nearer at hand, for those curious about what the future holds, Microsoft has released some Previews of next months Security and Quality Rollup Updates. The Windows Server 2008 SP2 update is KB4467687. The .NET Framework 2.0-4.6.2 update is KB4467227; this contains KB4459945 (ndp45), KB4467088 (ndp46), and KB4459933 (for .NET 2.0). Basically these tinker with local issues: Daylight savings time zone changes in Russia and Morocco, revised names for currency in Venezuela, calendar revisions in Japan. These don't seem to be immediately pressing concerns for most of us here (any of us?), they don't deal with serious flaws in the Windows Vista/Server 2008 software, and in another couple weeks we'll have the official monthly update releases, maybe with a bit more content. So we can all be patient. This is a pretty-nothing post, in other words. GreenHillManiac has a policy of excluding routine previews from his database. It struck me some people might be curious about what they might be missing because of that, so now you know -- Not Much.
  13. That time of the month again, and Microsoft has some Win Server 2008 SP2 updates at the MS Update Catalog site. So far, they've come up with KB4466536 Nov 2018 Security Update for IE 9 KB4467700 Nov 2018 Security Only Quality Update for WS 2008 KB4467706 Nov 2018 Security & Monthly Quality Rollup for WS 2008 KB4467243 Nov 2018 Security & Quality Rollup for .NET Framework (with KB4459933 for NDP 2.0, KB4459945 for NDP 4.5, KB4459942 for NDP 4.6) As usual, I'd suggest waiting a bit before installing things -- Microsoft's been known to change things within a few days (or even hours, on recent occasion). Wait for GreenHillManiac to give them his blessing, that's the safest policy. ----------- And almost as promised, a couple of these did get revised. KB4457700 and KB4467706, the Quality Rollups for Win Server 2008 SP2, were originally dated 9 November. The KB numbers, hashcodes, and sizes don't seem to have changed, but the dates went to 13 November., suggesting some change in the packaging info. Same old spam but a different label on the can, that's my take, but I'm not infallible.
  14. get it updated manually one-by-one it's very difficult. ... Vistaboy: After you've installed Vista SP2, the regular Vista Windows Update (available on your Start Menu) will download a wad of updates, typically several hundred, that will bring your system up to April 2017. Note that you should run the System Update Readiness Tool and the four or five "speed up" updates before trying to get Win Update to do its thing, otherwise you'll be twiddling your thumbs for a couple of days waiting for stuff to happen. AFTER THAT, you can begin to look for Win Server 2008 updates -- maybe at the Microsoft Update Catalog, if that's to your taste or happen to be looking for some non-Vista files, or from GreenHillManiac's collection if you want to keep things simple. Anotther word of advice: Windows Vista does not like to run MSU update files while the the Windows Update window is open, so before you tackle the the WE2008 updates go to WU Settings and turn everything applicable to OFF. Then dig in. More advice: I'd suggest that after every three or four updates you reboot the system rather than try to get everything all at once, Not a manditory requirement, but my experience is that the first patch installs quickly, and the next ones take a bit longer. So my rule of thumb is to devote an hour or two to Vista patches and other installations, then reboot, and repeat the process. You should be all done in a day or so. Then you can go back to the WU Settings and restore them to the original values. If you're running Windows Defender or Microsoft Office, you'll get an occasional update through this channel afterwards-- maybe a couple every month, maybe less. And you'll be even with the rest of us. And we'll have to call you Vista Man!
  • Create New...