News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • lmacri

    Forum Replies Created

    Viewing 15 posts - 1 through 15 (of 44 total)
    • Author
      Posts
    • lmacri
      AskWoody Plus

      A new Version 2004 Build 12730.20352 was released 21-May-2020 for retail versions of Office 2016 C2R and Office 2019 C2R. The update history at https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019 only states “Various bug and performance fixes” but the release notes at https://docs.microsoft.com/en-us/officeupdates/monthly-channel-2020#version-2004-may-21 include the comment “Fixed a Click-to-Run issue which was resulting in occasional update failures to the latest builds.”  Unfortunately, I don’t see any fix mentioned in those release notes for the MS Outlook search bug described in Woody’s Reports that this month’s Outlook update knocks out Search via Exchange Server.

      I checked today and my Office 2019 Home and Business C2R was still on Version 2004 Build 12730.20270 (rel. 12-May-2020) so I performed another manual update (File | Office Account | Office Update | Update Options | Update Now) to receive Build 12730.352. Fingers crossed C2R starts downloading my updates automatically again.

      Attachments:
      lmacri
      AskWoody Plus

      When I first read Woody’s article about this Outlook search problem on 08-May-2020 I immediately tested on my own Win 10 Pro v1909 machine and was pleasantly surprised to see the Search function was still working correctly with my MS Office 2019 Home & Business Version 2004 Build 12730.20250 (rel. 04-May-2020).  I understand that reports about this problem date back to 06-May-2020 but I use the Search function in Outlook 2019 almost every day so I have no idea why this issue didn’t appear on my machine until 16-May-2020.

      Sergiu Gatlan’s 13-May-2020 article Microsoft: Fix For Outlook Search Failures Coming Later Today on BleepingComputer was updated this past Friday and now states “Update May 15, 13:00 EDT: Microsoft is rolling out a fix for the Outlook search issues to all affected environments…“. Does anyone know the Outlook build number for the Version 2004 hotfix that is supposed to correct this problem? I don’t see anything listed beyond Build 12730.20270 (rel. 12-May-2020) in the update history at https://docs.microsoft.com/en-us/officeupdates/update-history-office-2019#retail-versions-of-office-2016-c2r-and-office-2019.

      lmacri
      AskWoody Plus

      I use MS Office Home and Business 2019 Version 2004 (Click-to-Run) on a 64-bit Win 10 Pro v1909 Build 18363.778 OS (May 12, 2020 KB4556799 / Build 18363.836 not installed yet) and just encountered this issue with the Search function in MS Outlook 2019. I was on Build 12730.20250 yesterday (16-May-2020) when I first noticed this problem with the Search feature and a manual update today to the latest Build 12730.20270 hasn’t fixed the problem. If I click the “Let’s look on your computer instead” link shown in the attached image the Search function works correctly and finds matches for messages downloaded to my local machine.

      MS-Outlook-2019-v2004-Build-12730_20270-Serach-Bug-17-May-2020

      I don’t know if the two problems are related but I should have received an automatic update to Build 12730.20270 (rel. 12-May-2020) a few days ago since MS Office 2019 is C2R. Fortunately, I was able to apply this patch manually per my post # 2263256 in Woody’s Reports that this month’s Outlook update knocks out Search via Exchange Server.

      Attachments:
      lmacri
      AskWoody Plus

      I use MS Office Home and Business 2019 Version 2004 (Click-to-Run) on a 64-bit Win 10 Pro v1909 Build 18363.778 (May 12, 2020 KB4556799 / Build 18363.836 not installed yet) and was able to update manually today from Build 12730.20250 to 12730.20270, but this is the first time I’ve noticed this C2R version didn’t update automatically shortly after an update was released.

      1 user thanked author for this post.
      in reply to: Anti-Telemetry Softwares. Surveillance Capitalisms. #2212312
      lmacri
      AskWoody Plus

      Just an FYI that Martin Brinkmann’s ghacks.net article Comparison of Windows 10 Privacy Tools at https://www.ghacks.net/2015/08/14/comparison-of-windows-10-privacy-tools/ghacks.net (last updated 03-Feb-2020) has an overview of many of the utilities mentioned in this thread like Debotnet, O&O ShutUp10, Spybot Anti-Beacon for Windows 10, etc.

      4 users thanked author for this post.
      lmacri
      AskWoody Plus

      Maybe this from Mozilla? Some Windows users who had previously installed and uninstalled Comodo antivirus software may not be able to start Firefox. Information on how to resolve this issue is described on support.mozilla.org or in the support knowledgebase.

      Please note that mledman’s quote is taken directly from the (revised???) FF 71 release notes at https://www.mozilla.org/en-US/firefox/71.0/releasenotes/. According to the Techdows article Fix Firefox 71 Does Not Start After Update and Firefox Forum Moderator philipp’s post at https://support.mozilla.org/en-US/questions/1274248#answer-1270830 the FF 71 startup failure can be caused by a Comodo file named IseGuard64.dll, IseGuard32.dll (or something similar) that is typically located in C:\Windows\system32\. This problem .DLL file may be present with currently running or previously uninstalled Comodo products.
      ———–
      64-bit Win 10 Pro v1903 build 18362.476 * Firefox ESR v68.3.0

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      Don’t know why but I can’t get either my production or test machines to update past 18362.418? Windows Update says I’m current..

      Hi RetiredGeek:

      Just an FYI that my Win 10 Pro v1903 OS was updated from Build 18362.418 to 18362.476 today and my missing Windows Update settings at Settings | Update & Security | Windows Update | Advanced Options | Choose When Updates Are Installed have reappeared. As expected, and per my previous comment in post # 2002647, Build 18362.476 (KB4524570) was installed ~ 30 days after its initial release. I’m not sure why, but the optional KB4522355 released on 24-Oct-2019 that included the initial bug fix for this problem was never detected by any of my manual Windows Update checks:

      • 2019-10 KB4517389 (OS Build 18362.418, released 08-Oct-2019) installed 07-Nov-2019
      • 2019-10 KB4522355 (OS Build 18362.449, released 24-Oct-2019) skipped by WU (optional update with initial bug fix)
      • 2019-11 KB4524570 (OS Build 18362.476, released 12-Nov-2019) installed 12-Dec-2019

      A few weeks ago I ran regedit to check the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings and confirmed that the value for “DeferQualityUpdatesPeriodInDays” had been previously set to “30” (see attached image), so rather than set this value back to “0” I just waited the 30 days until KB4524570 was delivered by Windows Update.
      ———————
      Dell Inspiron 5584, 64-bit Win 10 Pro 1903 Build 18362.476

      Attachments:
      lmacri
      AskWoody Plus

      Just updated Firefox to Version 71.0 this morning; an individual user in America & not on a corporate network. No distribution\policies.json in my Mozilla Firefox folder.

      I don’t think home consumers would normally expect to find this \distribution directory or policies.json file included with their FF installation. From the Firefox for Enterprise support article Customizing Firefox Using policies.json :

      To implement this policy support, a policies.json file needs to be created. This file goes into a directory called distribution within the Firefox installation directory. This directory is not usually included by default, so you may need to manually create this directory.”

      ———–
      64-bit Win 10 Pro v1903 build 18362.418 * Firefox ESR v68.3.0

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      The Firefox for Enterprise support article Customizing Firefox Using policies.json states “Unlike controlling Firefox with using Group Policy, the policies.json is cross-platform compatible, making it preferred method for enterprise environments that have workstations running various operating systems.

      I updated to FF ESR v68.3.0 yesterday and haven’t noticed any issues.  I’m not sure, but I suspect the policies.json problem described in Gunter Born’s article Firefox 71/68.3esr: Profile issues and bugs during upgrade affects Firefox users in larger organizations where they must use a company-approved Firefox profile located in the \distribution folder within the Firefox installation directory.
      ———–
      64-bit Win 10 Pro v1903 build 18362.418 * Firefox ESR v68.3.0

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      Re my above query about Defender automatically updating; it seems it does if I wait long enough (7 days). The update gets through the above advanced pausing setting, and presents itself as ready to download, and doesn’t download automatically. That sounds OK, but I’d prefer it updated its definitions every day. I don’t suppose there is a way to make it do that on a Home machine?

      Hi frankus333:

      According to Ed Bott’s 11-Mar-2019 Windows 10 tip: When You Should (And Shouldn’t) Pause Updates, pausing updates for 7 days “immediately stops all updates, with the exception of Windows Defender definitions (which are typically small and don’t require a restart)“. I assume that comment applies to both Home and Pro versions of Win 10 that allows users to temporarily pause Windows Updates.

      I’m fairly new to Win 10 and still exploring my configuration settings, but I don’t normally receive any Windows Defender definition updates since my McAfee AV automatically disables Windows Defender and Windows Defender’s Limited Periodic Scanning is currently disabled. However, I ran a brief test last month and confirmed that my Windows Defender definitions were automatically updated at least once a day as expected if I enabled Limited Periodic Scanning, even when I had my Win 10 Pro v1903 advanced setting set to defer “Quality updates that include security updates”.

      If required, Microsoft posts full offline installers for the latest Windows Defender definition set at https://www.microsoft.com/en-us/wdsi/defenderupdates that you can save to your desktop and install manually while you’re troubleshooting.
      ———-
      Win 10 Pro v1903 build 18362.418 * Firefox ESR v68.2.0 * McAfee LiveSafe v16.0 (R21)

      2 users thanked author for this post.
      lmacri
      AskWoody Plus

      Hi RetiredGeek:

      I’m still on Build 18362.418 (rel. 08-Oct-2019) as well, and you might be experiencing the same glitch as me. Shortly after my August 2019 Patch Tuesday delivered KB4512508 (OS Build 18362.295, rel. 13-Aug-2019) I changed the advanced Windows Update option (Settings | Update & Security | Windows Update | Advanced Options | Choose When Updates Are Installed) to defer “Quality updates that include security updates” to 30 days. I didn’t realize there was a known bug that would cause those advanced Windows Updates settings to disappear as soon as I entered non-zero numbers, and since August 2019 Windows Update has continued to honour that deferral setting (even if I click “Check for Updates” to run a manual update) and I’m currently stuck waiting 30 days for new cumulative quality updates to be delivered. For example, my Windows Update history shows my last 3 cumulative updates were delivered approx. 30 days after their official release date:

      • 2019-09 KB4515384 (OS Build 18362.356, rel. 10-Sep-2019) installed 10-Oct-2019
      • 2019-09 KB4524147 (OS Build 18362.388, rel. 03-Oct-2019) installed 03-Nov-2019
      • 2019-10 KB4517389 (OS Build 18362.418, rel. 08-Oct-2019) installed 07-Nov-2019

      I could probably fix this with the Group Policy Editor [Computer Configuration | Administrative Templates | Windows Components | Windows Update | Windows Update for Business | Select When Quality Updates are Received (my setting currently states “Not Configured“) followed by a Check for Updates] as described in the TenForums thread The Strange Case of the Missing Pause Feature Update Setting but I’ve decided to wait another two weeks until the bug fix in KB4522355 (OS Build 18362.449, released 24-Oct-2019) comes through on it’s own.
      ———————
      Dell Inspiron 5584, 64-bit Win 10 Pro 1903 Build 18362.418

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      Hi. Does anybody know, how the block was “removed” technically? Did it came with SEP definition updates?

      I’m wondering because my servers live in quite isolated environment, only WSUS has internet access to MS servers. So if my SEP version does not change, and WSUS rollup files do not change, then how the heck this blocking behaviour could be modified?

      See my post # 1924193. Norton users with a Win 7 SP1 OS were updated to Norton v22.18.0.222 (rel. 20-Aug-2019) to fix this problem, while Win 8.x and Win 10 users remained on v22.18.0.213 (rel. 29-Jul-2019).  Both those products have now been replaced by the latest v22.19.8.65 (rel. 13-Sep-2019).

      The SEP product updates for Win7 SP1 and Win Server 2008 R2 SP1 were released 27-Aug-2019, and version numbers are listed under “Solutions” at the bottom of the support article at Windows 7/Windows 2008 R2 updates that are only SHA-2 signed are not available with Symantec Endpoint Protection installed The FAQ refers to these updates as “SEP hotfixes.
      ———-
      32-bit Vista Home Premium SP2 * FF ESR v52.9.0 * Norton Security v22.15.2.22

      • This reply was modified 8 months, 1 week ago by lmacri. Reason: Clarified applicable OSs for SEP updates
      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      Hi Gene:

      It also affected Win 7 SP1 users with Norton home consumer products, and a Norton v22.18.0.222 update that targeted Win 7 SP1 (but not Win 8.x or Win 10) started rolling out on 20-Aug-2019 that allowed Win 7 SP1 users to apply their available Windows Update patches. See the 20-Aug-2019 revision to the original product update announcement Norton Security 22.18.0.213 for Windows is now available! as well as Norton employee Sunil_GA’s 20-Aug-2019 post in the thread Is it safe to install August 2019 Windows 7 update?? in the Norton Community forum.
      ————
      32-bit Vista Home Premium SP2 * FF ESR v52.9.0 * Norton Security v22.15.2.22

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      …that last one you listed (the Microsoft Graphics Component) caught my eye as a possible cause of the black screens on my Vista tower… the Vista laptop, which has nothing fancier than the integrated Intel graphics, has no problem with it.

      Hi Cybertooth:

      You mentioned <here> that the problem desktop that suffers a black screen after certain Win Server 2008 patches are installed has a discrete NVIDIA graphics card. I don’t know if it’s relevant, but see the August 2018 post by a Piriform employee in the CCleaner forum thread Changes in v5.45 and Your Feedback, which states in part:

      We’ve actually been in contact with the Windows team about this. They explained that when a Windows update occurs (e.g. Spring Update), various files are held in the Windows.old folder and an automatic migration process is started. This includes items like graphics drivers, which are remain there until Windows can programmatically re-map the paths and migrate them to the correct place outside of the Windows.old folder. In this particular case, cleaning the folder of the graphics drivers would completely break rendering for some users (their screens would turn black). The average CCleaner user does not know how to reinstall a graphics driver when their screen is black, and even a more technical user would find it a pain.

      It’s possible that older Vista-compatible drivers for some NVIDIA graphics cards don’t work correctly once the Vista SP2 OS build number is changed to 6.0.6003.x (i.e., in much the same way that legacy Avast/AVG v18.x software needs an emergency “micro-update” to prevents BSODs with build 6.0.6003.x) but I also wonder if there could be some cleanup routine or migration / re-mapping of graphics drivers during certain certain Win Server 2008 updates that keeps misplacing your NVIDIA drivers.

      I have an NVIDIA graphics card in my Vista SP2 machine, so you’ve given me one more reason to hesitate installing the KB4499180 patch now that I know this Win Server 2008 security update will muck up my Vista SP2 OS build number. Avast Free was supported on Win XP and Vista until January 2019 (see the Avast announcement <here>) and is still the AV of choice for many Vista SP2 users, so it’s not surprising everyone is hearing about the BSODs caused by Avast/AVG v18.x with build 6.0.6003.x.  I suspect reports of problems with other third-party software like VMware will continue to trickle in over time unless Microsoft releases a targeted patch for CVE-2019-0708 that doesn’t change the Vista SP2 build number.
      ——————-
      32-bit Vista Home Premium SP2 * Norton v22.15.2.22 * NVIDIA GeForce 8400M GS

      1 user thanked author for this post.
      lmacri
      AskWoody Plus

      …I would also recommend Imacri’s link for Server 2008 Updates on Windows Vista (which however contains no reports of “general system instability” as far as I can tell).

      Here’s one example in that thread from Jaguarek62’s 19-Apr-2019 post at https://msfn.org/board/topic/176686-server-2008-updates-on-windows-vista/?do=findComment&comment=1162598: “i would like to warn you about installing april updates for server 2008 on vista. My os is unstable after the april rollup. They are some changes being made to win32k which makes my vista x64 really unstable. Even build number is different now. i will keep you updated, but if you dont have to you should not install it. (kb4493458).

      When asked if they used an Avast product that same user posted <here> “In my case it was strangely due to vmware services. i disabled them and vista was stable again…”
      ————
      32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Norton Security v22.15.2.22

      • This reply was modified 11 months, 2 weeks ago by lmacri.
    Viewing 15 posts - 1 through 15 (of 44 total)