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
  • Malicious Software Removal Tool update, KB 890830, throwing weird WinXP (!) EULA prompts

    Posted on November 15th, 2018 at 05:11 woody Comment on the AskWoody Lounge

    If I’d seen it once, I’d just disregard it as another bizarre Microsoft bug. But we have three reports now, like this one from @Morat:

    I’m running Windows 7 Pro 32-bit. MSRT Nov 2018 KB890830 popup notice says, “Prerelease Version of Service Pack 2 for Microsoft Windows XP Professional, Home, Media Center, or Tablet PC Edition END-USER LICENSE AGREEMENT FOR PRERELEASE CODE”. What the heck… prerelease code for Windows XP?

    There’s confirmation from @bsfinkel and from an anonymous poster.

    Looks like there’s a bug in KB 890830 for 32-bit Win7 — Prerelease code for XP? Pshaw.

    Thx, @Microfix

  • Best way to transfer an old Win7 PC to a new Win10 VM?

    Posted on November 7th, 2018 at 07:07 woody Comment on the AskWoody Lounge

    Interesting question from an old friend:

    I’ve got a six year old Windows 7 Home Premium Service Pack 1 PC that’s getting kind of long in the tooth (though still working fine). I would like to upgrade it to a spankin’ new Win 10 desktop without the weeks-long pain of having to figure out how to migrate my applications and upgrade them, not to mention figuring out all the little Win 10 quirks.

    So I thought what might be slick would be to make the old machine a virtual machine and then transfer it whole hog to the new machine.

    I’ve already nudged him toward switching to a Chromebook 🙂 but regardless of how he goes, the proposal raises several interesting questions.

    • What’s the best way to get a “valid” version of Win7 running on a Win10 VM? Where’s the best place to buy a Win7 license?
    • If he can get a Win7 VM going, what’s the best way to transfer the contents of the old PC to the new VM? (Fully realizing that there will be lots of problems.)

    Anyone have experience with a brain transplant?

  • Where do we stand on the April “Group B” Win7 patches?

    Posted on April 25th, 2018 at 08:00 woody Comment on the AskWoody Lounge

    I’m trying to sort through all of this month’s dregs and summarize things for Computerworld readers.

    I see where “Group A” is pretty well set for this month. The re-re-release of KB 4093118 on Monday night makes the Total Meltdown fix relatively innocuous. Yes?

    I’m more concerned about “Group B” and the side-effects of installing KB 4093108. Anybody have a concise summary of where we stand with all of the problems associated with KB 4093108?

    I’m still seeing complaints about “The User Profile Service failed the logon” bugs, but MS has addressed that problem here.

  • Weird hibernation state on reboot attributed to Win7 patches

    Posted on February 24th, 2018 at 07:49 woody Comment on the AskWoody Lounge

    We have two reports here on AskWoody of Win7 hibernation (?) problems after installing recent Win7 Monthly Rollups.

    An anonymous poster:

    I installed KB 4074598 on my Windows 7 Desktop PC (I use AMD stuff etc) and it kept putting my PC into a weird hibernation state when trying to restart.. every single time. It wouldn’t show input from the monitors, mouse/keyboard, but the tower would still be running. To get out of this state I had to turn off the PC directly from the button on the tower itself, then turn it back on. It didn’t even do that “windows shut down unexpectedly” thing when you force turn off the PC.

    And a summary of reports on other forums, compliments of @amraybit.

    Looks like the problems started with the January Monthly Rollup, KB 4056894, and continue with this month’s Monthly Rollup KB 4074598. It seems to impact both Intel and AMD chips.

    Ben1907 on the Microsoft Answers forum has had some success, without uninstalling the patch:

    I checked my C-State settings on my ASUS P8P67-M motherboard and they were set to the default settings in the ASUS manual.

    • C1E [enabled]
    • C3 Report [disabled]
    • C6 Report [enabled]

    Playing around by setting different combinations, I found the C1E enabled/disabled did not matter, so left it enabled. However, by setting C6 Report to DISABLED, I have now been able to perform a normal restart/reboot from Windows 7. Tried at least half dozen times and all good so far.

    Thanks for investigating this and putting me on the right path to correct this issue. Microsoft has caused me so many lost hours of troubleshooting problems they inject with updates you wonder if they have any quality control.

    Indeed.

  • KB 4025341, KB 4025337 cause crashes on some older hardware running Win7

    Posted on July 14th, 2017 at 15:48 PKCano Comment on the AskWoody Lounge

    There have been reports of BSODs after installing the July 11 patches on some older Win7 machines. Both KB 4025337, the security-only Update, and KB 4025341, the Monthly Rollup have been involved. Uninstalling the update fixes the problem.

    Many posters have reported successful installation of the updates. So it doesn’t appear that the updates themselves are broken, but, when combined with specific drivers, BSODs result. It is likely due to some of the changes Microsoft has made to Win7 via the patches. @NetDef reports that updating the Intel C600 chipset driver fixed the problem. Another report possibly points to AMD graphics drivers.

    If you have experienced a BSOD after installing the July 11 patches, your information would be helpful. The errors on the blue screen can pinpoint a conflict with a device. The Device Manager in the Control Panel is also an excellent source of information on installed drivers. What was the source of your drivers – from the manufacturer or were they Microsoft drivers?

    This is an example of the type of information that is useful:

    OS: Win7 Ultimate SP1 64bit
    PATCH: KB 4025337
    BSOD Info: STOP SYSTEM_SERVICE_EXCEPTION 0x0000003b
    CPU: Intel Core 2 Quad Q8200
    GRAPHICS: ATI AMD Radeon HD6450 v15.300.1025.0
    CHIPSET: Intel P35/G35/G31 r.10 (or version)
    FIX: Uninstalled update, or Rolled back HD6450 driver to n.15.200.1052.0, or Updated Intel chipset drive to…

    Any luck in identifying the the exact driver(s) involved would be most helpful to a lot of people.