• rick41

    rick41

    @rick41

    Viewing 15 replies - 16 through 30 (of 167 total)
    Author
    Replies
    • Can’t say for sure whether they’re update related, but since applying the updates on June 28 (SMQRs in my case) I’ve had two BSODs, on July 11 and July 18, and my Win7 machine has rarely, if ever, had Blue Screens before this.  Disk check, System File Checker, and a short memory test don’t reveal any problems.

      1 user thanked author for this post.
    • I don’t think I’ve had a restart request from the Standalone Installer for quite awhile.  Just the “press any key to exit,” or something along those lines.  At first its absence concerned me a bit, but it always says installed successfully, and the updates indeed show up in Installed Updates.

    • For some reason, “RunOnce_W10_Telemetry_Tasks.cmd” appears on only one of the two Win 7 SP1 that I run the standalone installer on.  I just delete it, since I’m not overly concerned about the telemetry on these computers (not that I like it…).

       

      1 user thanked author for this post.
    • Did you install KB5027140 and KB5027275 in a single run of W7ESUI, or two separate runs? Similarly for DOTNETFX4 and KB5027129 and KB5028586, was it a single run or two runs of the script?

      Can’t speak for George1, but in my case it was KB5027140 and KB5027275 in a single run of W7ESUI (v4); and KB5027129 and KB5028586 in a single run of dotNetFx4 (_u).  Two Win7 SP1 computers,  no problems.  The install time was on the longer side, especially for the W7ESUI run.

      3 users thanked author for this post.
    • in reply to: Working with the Intel Driver & Support Assistant #2567852

      Would appreciate your response re my concern about installing Intel DSA updates that are never released in a parallel Lenovo version.  In my case I’m talking about a 1-year-old model, and the concern is particularly re graphics.

    • in reply to: Working with the Intel Driver & Support Assistant #2567594

      Even though I installed Intel DSA, I have been avoiding use of it with my Lenovo Thinkpad P1 Gen5.

      One reason has been that warning about overwriting OEM graphics driver customizations.  I spent quite awhile tweaking the graphics (in my case meaning simply color parameters, contrast etc) to get them exactly how I want them.  Yes, I’ve saved the settings as a preset, and you described how that warning applies only to older machines.  But despite all that, I have to wonder why —  if there were any significant enhancements present or worthwhile in the new graphics drivers —  Lenovo wouldn’t routinely offer parallel driver updates for Intel graphics (or any other hardware) in its own update programs like Vantage or System Update.  Instead, such offerings are less frequent than Intel DSA’s.

      Further, with WiFi working just fine, is there really any reason to update networking drivers if no security issue is involved?  Again, wouldn’t any significant enhancements be offered in Lenovo’s own update utilities, especially while the machine is still a reasonably recent model?

      EDIT:  Corrections

      • This reply was modified 8 months, 1 week ago by rick41. Reason: Corrections
    • in reply to: Windows Explorer Stops Working #2549986

      EDIT: Meant to mention that FileHippo has a download for Office Compatibility Pack which is v12.0.6612.1000, the same you were updated to.

      For the record, today a Norton popup said this FileHippo download is infected with PUA.Superfluss.

      This is strange on multiple counts:  (1)  I thought FileHippo was trustworthy; (2) why is Norton detecting this just now, when I had downloaded it almost 3 weeks ago?;  (3) ironically, I just did a Norton full system scan yesterday — which I do very infrequently  — and it reported that no threats were found; and (4) Norton reports that the file has been used by tens of thousands of people in the Norton Community, and that it is “mature — released 3 months ago.”  Out of curiosity I uploaded the file to VirusTotal, and, based on someone else’s submission just 2 hours earlier, 15 of 70 vendors flag the file as malicious.

      Regardless, I don’t need that download anyway, as I instead installed the version I had saved in April, 2014 (that is apparently the same as the version CNET has), which Win10 Windows Update then updated.

      .

    • in reply to: Windows Explorer Stops Working #2546063

      It inserts a blockquote.

      I could see that by hovering, but — from the sound of it –was thinking maybe that was what I wanted.  IIRC, the reason it was easier to teach myself the basic html in some forums I used to frequent is that I was able to see the html behind others’ posts. There’s no way to do that in AskWoody, is there? Another thing that would help on that count would be a Preview option, so that you could make sure everything looks right before submitting.

      Also, I find that Text (which I used to post this) can be more descriptive, e.g. it actually showed “blockquote” in the html rather than just indenting. (As you can see, I didn’t post a blockquote, I was just experimenting.)

    • in reply to: Windows Explorer Stops Working #2545636

      Good stuff!  Glad I just happened to check back here, because I oddly never received the notification email (and I just now checked to ensure I didn’t inadvertently miss or delete it or that it ended up in the spam folder).

      Anyway, thanks much for that easy and practical Winhlp solution!!  Even though I’ve used startup batch files in the past, it’s been so long that I actually forgot about that capability.  That approach removes the annoyance of having to remember to rerun the script when a Windows “feature” (that appellation still seems so odd to me…) or System File Checker deep-sixes the Winhlp fix.

      Thanks too for the posting info.  Not hitting reply was just an inadvertent mistake.  As for quoting sections of a post, I knew highlighting was probably part of the process, but I didn’t realize you then had to go back up to the post and click Quote.  I was trying to use the quotation marks symbol in the toolbar instead.

    • in reply to: Windows Explorer Stops Working #2544866

      I used Microsoft’s free offer to upgrade from Win7 to Win10 back on Dec 2019 so yeah, that particular security update was installed using Win10. However, it’s still available from the Microsoft Catalog…

        • Security Update for Microsoft Office Compatibility Pack Service Pack 3 (KB4461607)

      And doesn’t indicate it’s intended for any particular version of Windows so I’m a bit surprised it hasn’t been offered to your Win7 system.

      (This is in reply to the top part of your post, about KB4461607.  Some day I’ll figure out how to quote just the part I want to include.  I assume it involves highlighting.  Further, I see that I needed to use Reply somewhere to keep this reply from being removed from the hierarchy.  Oh, well…)

      Interesting.  I’ve now got the Compatability Pack on my new Win10 machine, using the exe I saved in 2014.  WU installed numerous updates, but still not KB4461607.  I don’t know whether this means it is no longer important, or just an MS glitch (not that that ever happens LOL), but I guess after reading the KB document I’ll just take a pass on seeing if it will install manually.

      BTW, I got Office 97 loaded onto the Win10 machine OK.  I was dismayed to find what others apparently learned several years back, namely that the Help function doesn’t work since MS stopped supporting Winhlp based help in Win10.  And from what I can see, script-based workarounds get wiped out every time there is a feature update (or System File Checker is used).  OR, you have to resort to an inconvenient method which requires opening individual .hlp files.  I don’t use Help in Word or Excel all that often, but it was indeed convenient when needed.  Oh well, at least Outlook 2003’s help function still works.

      [note from alejr:]  I edited your reply to match your “intended” response.

    • in reply to: Windows Explorer Stops Working #2544645

      Curious discrepancies…although I would guess they’re of minimal practical significance.

      BTW, you are looking at updates on Win10, right?  I guess that would explain why you have KB4461607 from November 2021 (post Win7 end-of-support) while I don’t.  I am still looking at Win7 for what we’re discussing here since I haven’t added Office 97 to my Win10 machine yet.   Although, I did have a Win7 ESU license for 2020 and 2021.

      I show a total of 10 items in Installed Updates under the heading “Compatibility Pack for the 2007 Office system” but the oldest one, from 6/7/2014, is the original Compatibility Pack itself, not a KB (it says “Microsoft Office Compatibility Pack Service”) and the version column for it is blank.

      Some of the updates refer specifically to the Compatibility Pack, while others only mention “Office 2007 suites.”  But it’s odd that in my list KB4011717’s name refers to the Compatibility Pack while your refers to to the 2007 suites.

      Next it will be interesting to see if Powerpoint Viewer, based on Office 2010, will install and get updates in Win10.  Though it’s not something that I use much.

    • in reply to: Windows Explorer Stops Working #2544616

      Thanks!

      I don’t recall seeing or installing those Service Releases for my Windows 7 Office 97 installation.  My installation CD is probably already updated to include those enhancements, as it’s labeled “SR-2”

      I had seen and (in anticipation to my switch to Win10) downloaded the CNET version of the Office [2007] Compatibility Pack.  But it turned out to be identical to the version I installed (and saved) in April, 2014 when I moved from XP to 7.  They are the same size, and both say v12.0.6500.5000.

      Since Windows (10) Update offered almost the entire slate of updates for my Outlook 2003 (as I described in another post), I assume it will also update the Office 2007 Compatibility Pack.

      Fyi, the Compatibility Pack version currently on my Win7 machine is apparently 12.0.6787.5000.  At least that’s what I see by hovering over  excelcnv.exe and Wordcnv.dll in C:\Program Files (x86)\Microsoft Office\Office12.  The install date is in March, 2018.  My last entries in Installed Updates are both dated 6-11-2018, and both called “Security Update for Microsoft Compatibility Pack Service Pack 3.”  KB4011717 and KB4018354.   Even before posting, I had downloaded these “just in case.”  (I did the downloads from the respective Microsoft KB pages.  They’re also in the Microsoft Update Catalog, but for these updates it gives you cab files instead of exe’s.)

      EDIT:  Meant to mention that FileHippo has a download for Office Compatibility Pack which is v12.0.6612.1000, the same you were updated to.

    • in reply to: Windows Explorer Stops Working #2544486

      @alejr, I’m going to soon be installing Office 97 (Word and Excel) on Win1o Pro, too.  Do you recall if you were able to apply any security updates (or even hot fixes) onto the Win10 installation?

       

    • in reply to: Windows Explorer Stops Working #2544478

      The time finally came to “move” Outlook 2003 from my Win7 Pro machine to my new Win10 Pro.  (My old installation CD is Outlook only; for Word and Excel I still use ’97, and apparently I’m not alone :).)

      Anyway, your instructions proved extremely helpful.  I ran the MSI (MS Installer) I found on the install CD (which is Outlook 2003 before any SP’s), choosing custom installation.  I actually only encountered one error message, about the registry lacking an expected entry for the Microsoft Visual FoxPro ODBC Driver.  After I clicked ignore it appeared to halt the installation, as I never saw even a “millimeter” of movement in the progress bar.  But instead, what I was presented with was an installation of Outlook 2003 that seemed to be working fine, except that (1) I had no MSO Cache folder (not really a concern, especially as long as I have the CD), and (2) my attempt to then “repair” the installation from Programs and Settings (still using the CD as source) produced the same error and aborted.  Also, I wondered why P & S listed Outlook’s size as only about 100mb, when my Win 7 machine listed about 500mb.

      But testing and re-testing showed that Outlook 2003 seemed to be working fine in every respect I could think to test, so I went ahead and did Check for Updates (importantly having set per your advice to check for updates to MS products).  And yes, it installed a load of them, in my case including an upgrade to SP3.  In fact, I compared (after several update-checks, until I got to “you’re up to date”), and these are the same set of patches shown as installed for Office 2003 and/or Outlook 2003 on my Win 7 machine, except for one from 2017 that was missing.  I Googled that one, and found a Microsoft page that still offered it.  It installed fine manually.  After the updates, the reported Outlook size in P&S had grown from about 100mb to about 350.  (BTW, the update check also installed 2 Filter-Pack patches that I have on my Win 7 — one from Oct 2014 and one from July 2019.)

      But I decided to try searching once more to see if if I could find anyplace reputable-looking to get that Visual Fox Pro ODBC Driver installed, so that I wouldn’t encounter error messages in the highly unlikely event I ever needed/decided to try to repair or change the Outlook 2003 installations (e.g., activate un-chosen features).  Just as I was about to give up after a slew of dead-ends (including from all MS pages about the long-defunct VFP), I found a small 2021 GitHub msi to install the VFP ODBC Driver.  (They actually recommended a different version of VFP, but Outlook 2003 was citing this one.)  After running the driver install, I rebooted and then tried “repairing” the apparently-working-fine Outlook installation — and this time it quickly completed without a hitch (progress bar and all).  Not that I really needed to take this step, but an error-free install provides a degree of comfort.

      I considered whether to completely uninstall and reinstall Outlook 2003 at that point, since it’s presumably the VFP ODBC error that kept me from ending up with an MSO folder, but decided against it.  If the system hadn’t already installed about 17 Outlook updates including SP3, I probably would have taken the leap.  BTW, the fact that you did end up with an MSO Cache folder makes me believe you may have had a different error, or used a different install method (e.g., other than the MSI) or options.

      Sorry, I doubt you or anyone else wanted this much detail, but frankly I’m also doing it to document for myself.

      Anyway, thanks again for your great advice a few months ago!

    • If you haven’t already read it, abbodi86’s post at the top of this page is key reading.  While it is about Win7, the process for running Win8.1 updates is the same, with the difference being that you have to instead use the Win8.1 version of the “ESUI” script that PKCano links to (e.g., in post #2543438 ).

      While there are no .NET updates this month, when there are, things are simplified a little for 8.1 vs. 7, as you’ll be able to use that same ESUI script to run any updates you need.  (Win7 requires a separate script for patching .NET versions that are not built-in Windows components like .NET 3.5.1 is.)

      2 users thanked author for this post.
    Viewing 15 replies - 16 through 30 (of 167 total)