• AusJohn

    AusJohn

    @ausjohn

    Viewing 15 replies - 1 through 15 (of 95 total)
    Author
    Replies
    • in reply to: Windows 10 1903 Build 18362.239 Upgrade Error [Laptop] #2482092

      True.  It’s just that I’m overseas, and short of both time and resources at the moment.

      It looks like my best option is to wait until I get home, then do a clean install when I have time and can concentrate on it properly.

       

    • in reply to: Windows 10 1903 Build 18362.239 Upgrade Error [Laptop] #2481855

      Did you try clean install (providing you have a full image backup of OS and data) ?

      No.  I don’t have a full image, and I really don’t want to have to install everything again if it’s at all possible.

      Do you have enough free space on C drive ?

      More than enough, from what I’ve read; about 74 GB free.

       

    • in reply to: Windows 10 1903 Build 18362.239 Upgrade Error [Laptop] #2481838

      Thank you for the suggestion.

      Sadly, it didn’t work for me.  Final result – same as all my previous attempts, with one minor exception.

      I followed the instructions and the install proceeded as usual; after that the restart process commenced.

      There were a couple of reboots, then the restart process reached 49%, and that was far as it got.

      The computer shutdown.

      In case it’s of any use/interest to anyone, a screen shot of the message is attached.

      We-couldnt-install-Windows-10-25-Sep-2022

    • All good questions; I’d certainly be interested to see the answers.

    • Thank you so much.

      I did as you suggested and, of course, the install worked like a charm.

      It even shows in the list of “Installed Updates”.

      Your assistance is sincerely appreciated.

    • No. Should I?

      And if ‘yes’, which option should I select, from 1, 2, and 3?

    • Thanks for your suggestion.

      I’ve followed your instructions, and the resulting log file is in the attached ZIP archive.

      Doesn’t make much sense to me, but I would appreciate it – if you have time – if you could take a look.

      2 users thanked author for this post.
    • Thanks for the suggestion.

      I’ve just done as you suggested, but the result – surprise, surprise – was the same.

      That is:

      “All applicable updates are detected as installed”

      So once again, thank you. You’ve done all you can, and I appreciate that, so now you can give up.

    • Have you looked in installed updates to verify it’s not already installed?

      Yes

      Have you checked the file name to be sure it is x86 (not x64) and has the right KB number 4586827?

      Yes

      Did you put it in a folder with the contents of W7ESUI.v0.2.zip?

      Yes

      Right click on the .cmd file and Run as Administrator?

      Yes

      Have you tried with a fresh downloaded copy of W7ESUI.v0.2.zip?

      Yes

      Any other thoughts or suggestions?

    • I’ve tried to install Win 7 Monthly Rollup 4586827 on my Win 7 SP1 32-bit Professional machine, using W7ESUI v0.2 run as Administrator, but it stops after a short while with the message:

      All applicable updates are detected as installed

      ============================================================
      Removing temporary extracted files…
      ============================================================

      ============================================================
      Finished
      ============================================================

      SSU KB4580970 (October 2020) is already installed.

      The update (using the .msu file) definitely hasn’t been installed because I just downloaded it from the Windows Update Catalog.  And, as expected, it’s not showing in the list of installed updates.

      This is the first time that I haven’t been able to install updates using the W7ESUI script.

      Any ideas as to what the problem may be, and how I can get it to install?

      1 user thanked author for this post.
    • in reply to: A changing of the guard at AskWoody.com #2310484
      Hi Woody,
      What a surprise!  About to retire, or at least take on something new/different.
      All I can say is “thanks”, and I hope you enjoy whatever the future holds.
      It’s a long time since I started ‘following’ you, with WOW in 1996, then WOWMM in 2000, and various “things” since then.
      Hopefully you’ve had as much enjoyment writing as I’ve had reading.
      Cheers,
      AusJohn
      (Also from Australia)
      2 users thanked author for this post.
    • in reply to: What happened to internet explorer in Win10 v1909? #2274585

      True, but it doesn’t necessarily mean that Internet Explorer isn’t still installed on the computer.

      Stranger things have happened.

      IMO it would be worthwhile to do a quick and simple search for iexplore.exe just out of interest.

    • in reply to: What happened to internet explorer in Win10 v1909? #2274516

      The name of the Internet Explorer executable file is iexplore.exe – are you looking for the correct file.

      I ask because you’ve mentioned ieexplorer.exe several times, and I’m wondering if that’s just a typo or you’re searching for the wrong file.

      Just a thought.

      1 user thanked author for this post.
    • Running Windows 7 SP1, updated with the March 2020 cumulative update (following abodi86’s excellent recipe), and MSE, I got the MSE problem after updating definitions from 1.313.1556 to 1.313.1638. The problem persisted when I updated the definitions to 1.313.1666.

      However, this morning I updated the definitions to 1.313.1687 and, so far at least, the problem appears to have been rectified. No more red MSE interface telling me that the security service isn’t running, and should be started.

      The situation was the same on both Windows 7 computers here.

      1 user thanked author for this post.
    • in reply to: Windows 7 and Office 365 Click-to-Run #2210017

      Thanks, I hadn’t seen those two references.

      Explains why I saw what I did, although I still find it rather odd that MS offer Office security support for three years after the end of Windows 7 support.

      Not to worry – I’ll accept it and be thankful for small mercies.

      1 user thanked author for this post.
      b
    Viewing 15 replies - 1 through 15 (of 95 total)