Woody Leonhard's no-bull news, tips and help for Windows, Office and more… Please disable your ad blocker – our (polite!) ads help keep AskWoody going!
Home icon Home icon Home icon Email icon RSS icon
  • If you got hit by the 1809 upgrade file deleting feature…

    Posted on October 6th, 2018 at 12:55 woody Comment on the AskWoody Lounge

    and you’ve tried using Recuva to get the files back…

    Contact Microsoft directly:

    “They have the tools to get you back to a good state.”

    Like, maybe Hawaii?

    If Microsoft does have a secret tool or two in their hip pockets, I’d sure like to hear about it/them.

  • Patch Lady – 1803 issues with peer to peer

    Posted on June 23rd, 2018 at 09:40 Susan Bradley Comment on the AskWoody Lounge

    A new “known issue” note was posted in the answers forum:

    https://answers.microsoft.com/en-us/windows/forum/windows_10-networking/file-explorer-may-not-detect-other-devices-or/a7509468-27ce-4e92-a19b-a6b78d311b14

    File Explorer may not detect other devices or perform file sharing on the local network when running Windows 10 version 1803

    Justin posts:

    Microsoft is aware of reports that devices running Windows 10 version 1803 cannot connect to other devices on their home network and is investigating the issue.

    You can resolve this problem by setting some services to Automatic (Delayed Start) and restarting Windows:

    1. Press the Windows Key and R at the same time to bring up the Run dialog.
    2. Type services.msc in the Run dialog and press Enter.
    3. For each of the following services, locate the service in list, right-click the service and select Properties.  Then set the Startup type to Automatic (Delayed Start) and select Apply.
      • Computer Browser (Browser)
      • Function Discovery Provider Host (FDPHost)
      • Function Discovery Resource Publication (FDResPub)
      • Network Connections (NetMan)
      • UPnP Device Host (UPnPHost)
      • Peer Name Resolution Protocol (PNRPSvc)
      • Peer Networking Grouping (P2PSvc)
      • Peer Networking Identity Manager (P2PIMSvc)
    4. Restart Windows.

     

  • Patch Lady – Quickbooks and emails

    Posted on June 16th, 2018 at 00:46 Susan Bradley Comment on the AskWoody Lounge

    I was posting up the master patch listing tonight and I spotted this KB and I know this impacted people recently:

    https://support.office.com/en-us/article/external-applications-crash-sending-email-through-outlook-fe719ad7-f44e-4f25-9822-478186c5ff4b

    ISSUE

    After updating Outlook to Monthly Channel Version 1805 (Build 9330.2087), external applications may crash when interacting with or sending email.

    For example, you may get an “Outlook is not responding” error with Intuit QuickBooks. Possible solutions for that specific error can be tried via this Intuit QuickBooks Help article: Crash: Com Error in QuickBooks Desktop

    STATUS: FIXED

    This issue is fixed in Monthly Channel Version 1805 (Build 9330.2118) and higher. To get the latest update immediately, open Outlook and choose File > Office Account > Update Options > Update Now.

    Microsoft made a service change for Outlook on June 11 2018 (3:45 PST) to mitigate instances of a crash that happens if you’re using a POP or IMAP account. Because of the way the service changes are implemented and also because the issue involves 3rd party interaction with Outlook, you may have to restart Outlook up to three times to ensure that the service change is applied. These restarts ensure that the service change is recognized, then downloaded, then applied successfully to your install of Outlook.

    If anyone is seeing this on NON Click to run, let me know.  But again this points out you need to move to the semi-annual non monthly version of Office 2016 as there are less issues.

  • Patch Lady – KB 4103718 no longer lists “investigation” note

    Posted on May 25th, 2018 at 01:30 Susan Bradley Comment on the AskWoody Lounge

    Remember that KB that was updated to showcase that Microsoft was investigating the networking issues?

    https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718

    This has been removed from this KB and appears to have been updated today to remove this note:

     

    Microsoft is aware that some customers have reported that network drivers are intentionally uninstalled, then fail to reinstall after applying the May 8, 2018 update. This can result in the loss of network connectivity.

    Microsoft is presently investigating and will provide a status update when the investigation is complete.

    I haven’t seen as many reports in the last few days of networking issues, but I’m not sure if that’s due to folks holding off on updating.  I can tell you on my several Windows 7 machines I have not seen an issue with networking.

    As always, when you go to install, be prepared to roll back.

    Updated note:  My apologies if I didn’t make this clear:  The patch had no change.  All that happened was a documentation change where they removed the investigation note.  However we have no final word on what happened.  All I know is that in my personal testing/patching on my Windows 7 under my control none had issues with networking.

  • Patch Lady – KB4103718 /KB4103712 known issues

    Posted on May 14th, 2018 at 13:41 Susan Bradley Comment on the AskWoody Lounge

    As noted in https://support.microsoft.com/en-us/help/4103718/windows-7-update-kb4103718 and in https://support.microsoft.com/en-us/help/4103712

     

     

    Microsoft is aware that some customers have reported that network drivers are intentionally uninstalled, then fail to reinstall after applying the May 8, 2018 update. This can result in the loss of network connectivity. Microsoft is presently investigating and will provide a status update when the investigation is complete.
  • Surface Pro 4 gets a firmware/driver patch

    Posted on April 12th, 2018 at 15:05 woody Comment on the AskWoody Lounge

    Just saw an addition to the Surface pro 4 update history page.

    Windows Update History Name Device Manager Name
    Surface – Human Interface Device – 2.0.313.0 Surface Digitizer Integration – Human Interface Device

    • 2.0.313.0 enables on-screen support for Surface Dial.
    Surface – Firmware – 105.0.106.8 Surface Touch – Firmware

    • 105.0.106.8 enables on-screen support for Surface Dial and improves touch accuracy.
    Surface – System – 2.0.2.0 Surface Dial Detection – System

    • 2.0.2.0 enables on-screen support for Surface Dial.
    Surface – System – 1.0.821.0 Surface Touch Servicing ML – System

    • 1.0.821.0 enables on-screen support for Surface Dial and improves touch accuracy.

    Care to bet that they didn’t solve the screen shake problem?

  • Patch Lady – Networking issues and KB 4088875

    Posted on March 15th, 2018 at 00:11 Susan Bradley Comment on the AskWoody Lounge

    As Woody pointed out earlier today there are some reports of networking issues after the install of this month’s Server 2008 r2 and Windows 7 patch.  The issues are not widespread and they appear to be limited to two scenerios:

    Scenerio 1 – VMware.  As noted on a reddit post a new virtual Ethernet network card is installed/enabled after the update.  The side effect has occurred before with other convenience rollups and a workaround was previously posted to this KB and a script is provided to fix the issue.  It is not impacting all servers, it appears to be impacting virtual machines on VMware.

    You can see more threads here.

    Scenerio 2 – workstations.  This one is a bit more fuzzy and not clear cut.  I’ve seen reports where workstations with static IPs may be impacted with this update.  There are definitely enough credible reports of chipsets being reset and losing their networking IP addresses.

    Note that I’m seeing this more in businesses than in consumer/peer to peer settings.

    On my Windows 7 (my old machine that we keep around for older programs), I’m seeing this update unchecked:

    Which normally means that Microsoft is throttling the patch while they monitor issues.

    What is honestly a bit more concerning is this documented side effect:

    After installing this update, SMB servers may leak memory. Microsoft is working on a resolution and will provide an update in an upcoming release.

    If you run a file server, you may want to run tests and determine if you do see THIS side effect as that one may impact.

    More on this as I see issues.

  • Revisited: How to update an old copy of Win7

    Posted on February 20th, 2018 at 06:32 woody Comment on the AskWoody Lounge

    Credit: David Stanley, Nanaimo, Canada

    Kevin Beaumont just tweeted:

    Barry Dorrans replied with a reference to this advice from @SwiftOnSecurity in April 2016:

    [REVISED] If updating fresh Win7, first download these, install, and reboot to make update install faster:

    KB3102810
    KB3138612
    KB3145739

    What struck me is how @SwiftOnSecurity’s advice (from April 2016) differs from our AskWoody advice (Feb. 2017, as amended) from @CanadianTech at AKB 3172605, basically:

    3… download and install either one or two updates manually. In most cases only the first (KB3172605) of these is needed. If that produces a result that says the “update is not appropriate for your computer”, you need to first install the 2nd of these (KB3020369), then install the first (KB3172605).

    Can anybody out there reconcile the differences? Which method is best?

    I have a sneaky suspicion we’re going to see lots of Win7 (re-)installs this year.