What Happens To Those Of Us Who Can't Update Beyond 1709? Solved

Page 1 of 8 123 ... LastLast
  1. Ex_Brit's Avatar
    Posts : 389
    Win7 Ult + Win10 Pro - x64
       #1

    What Happens To Those Of Us Who Can't Update Beyond 1709?


    From Googling people like me there seem to be an awful lot who have tried every which way to install 1803 and then 1809 and no doubt 1903 will be the same.
    What did Microsoft do to the updates that made them so finicky?
      My ComputerSystem Spec

  2. NavyLCDR's Avatar
    Posts : 11,809
    Windows 10 LTSC
       #2

    Your best option is to do a clean install and start with a fresh, problem free slate. Out of about 10 computers on my home network, I've only hav one that refused to update since Windows 10 first came out. But they all started with good, solid base installs.

    The one computer that failed to update was my father÷in÷laws, but he was the worst click happy computer user ever and only God knows what he clicked on to break things.
      My ComputerSystem Spec

  3. Try3's Avatar
    Posts : 2,432
    Windows 10 Home x64 and Pro x86
       #3

    Perhaps the hardware is no longer supported. What information there is can be seen in
    How to Check Windows 10 Computer System Specs n Requirements - MS
    Minimum hardware requirements - Microsoft Docs [see section 3 mainly]

    There is some guidance on using a utility called setupdiag for update failure diagnosis in
    Need Suggestions for a failed 1809 update - TenForums
    & posting its results could get you a solution or a definitive explanation.

    If you are really stuck on Ver 1709 [as I am with one old computer] then you can continue to update Windows defender but will still be at an ever increasing risk of malware vulnerability as the resilience of the OS diminishes in the face of malware developments.

    I'm soon going to get my router to block the old computer from the internet and will therefore have to accept limitations on which jobs it can do. I already tend to use it for local jobs such as reorganising the files on my large backup xHDDs [jobs which my newer computers regard as beneath their dignity].

    Denis
      My ComputerSystem Spec

  4. Ex_Brit's Avatar
    Posts : 389
    Win7 Ult + Win10 Pro - x64
    Thread Starter
       #4

    Looks like Microsoft have caught the planned obsolescence bug from Apple forcing people to keep their machines new or no older than 2 years.
    I'd buy an Origin PC in a flash, if I could afford it.
    As it stands I'll probably have to settle for another Alienware one as Dell Canada has financing arrangements.
    I tried setupdiag and all that it inidicated was some driver which I can't find even displaying Windows hidden OS drivers etc.
    It didn't give it a name, just a hint as to what it might be for.
    I still would love to know what the heck they're playing at as this makes me really angry.
    I've tried 24 times with just about everything disconnected and/or disabled
      My ComputerSystem Spec

  5. Try3's Avatar
    Posts : 2,432
    Windows 10 Home x64 and Pro x86
       #5

    Peter,

    What was the
    … some driver … It didn't give it a name, just a hint as to what it might be for

    I don't know the age of your hardware but I suppose that the problem has arisen because the hardware maker has stopped supporting it - Windows can only continue to function if the hardware makers provide the necessary drivers.

    I gave up and have not tried setupdiag but perhaps you could search by whatever it gave as identification for the hardware concerned - you could search here in TenForums and, if it is your existing Dell that the problem concerns, in the Dell user forum.

    Since you posted in another thread that you had also tried a clean install on the problem computer that means you are only going to succeed if you can identify the problem hardware then remove it or block it in the Bios if possible.

    My problem computer is a Dell Inspiron 9300 from 2005.
    I am still able to update on a Dell Inspiron 1545 from 2010.


    Best of luck,
    Denis
      My ComputerSystem Spec

  6. Ex_Brit's Avatar
    Posts : 389
    Win7 Ult + Win10 Pro - x64
    Thread Starter
       #6

    Yes. It's a real headache. In the past Microsoft Windows-anything would continue installing and ignore anything it didn't support and simply ask you to research the problem after the installation succeeded. Now it just fails with a vague error. I wouldn't mind so much if it actually pointed to whatever the problem was, but it doesn't.
    I also miss the days when I could call Microsoft and get free live support for any update issue.
    Thanks anyway for the help.
      My ComputerSystem Spec


  7. ignatzatsonic's Avatar
    Posts : 794
    Windows 10 Home, 64-bit
       #7

    That's a 10 year old CPU. A powerhouse when it was introduced, but I wonder how old a CPU can be and still accept Windows 10?
      My ComputerSystem Spec

  8. Try3's Avatar
    Posts : 2,432
    Windows 10 Home x64 and Pro x86
       #8

    Peter,

    What was the
    … some driver … It didn't give it a name, just a hint as to what it might be for

    When I backup drivers I also save a host of data files about drivers. I use built-in facilities plus NirSoft's
    DriverView
    InstalledDriversList
    DevManView

    Whilst whatever setupdiag gave you might seem meaningless, it might match something in one of those driver data files thereby enabling you to identify the hardware concerned.

    You'll need to set up your own folder paths for BackupFolder and the references to C:\Tools\External\NirSoft\DriverView etc

    BackupDrivers.bat
    Code:
    ::::::::::::::: Driver backup section  :::::::::::::::
    Set BackupFolder=E:\InstalledDrivers
    :: DriversLists
    powershell.exe Get-WindowsDriver -Online ^| Export-CSV '%BackupFolder%\DismDriversList-3rdParty.csv'
    powershell.exe Get-WindowsDriver -Online -all ^| Export-CSV '%BackupFolder%\DismDriversList-All.csv'
    :: Get HardwareIDs list
    powershell.exe Get-WmiObject Win32_PNPEntity ^| Select Name, Manufacturer, DeviceID, Status ^| Export-CSV "%BackupFolder%\HardwareIDs.csv"
    :: Get DriverView output
    C:\Tools\External\NirSoft\DriverView\DriverView.exe /scomma "%BackupFolder%\DriverView.csv"
    :: Get InstalledDriversList output
    C:\Tools\External\NirSoft\InstalledDriversList\InstalledDriversList.exe /scomma "%BackupFolder%\InstalledDriversList.csv"
    :: Get DevManView output
    C:\Tools\External\NirSoft\DevManView\DevManView.exe /scomma "%BackupFolder%\DevManView.csv"
      My ComputerSystem Spec

  9. Cliff S's Avatar
    Posts : 22,556
    Win10 Pro, Win10 Pro N, Win10 Home, Win10 Pro Insider Fast Ring, Windows 8.1 Pro, Ubuntu
       #9

    It's not just Microsoft, it's also the hardware OEMs no longer supporting old hardware with new signed drivers.(like the old intel CPUs)

    If you have a spare disk(or a good system image) you could try turning off Windows 10 UEFI and secure boot, and switching to CSM(Compatibility Support Module, also used if you want to install and native boot another OS other than Windows 8 or 10) mode, and reinstall Windows.
    It won't be secure against boot rootkits, but still work and might update also, and you will want to turn off Driver Signature Enforcement.
    Click image for larger version. 

Name:	image.png 
Views:	3 
Size:	255.3 KB 
ID:	232938

    The next time you restart your computer, driver signature enforcement will be disabled—unless you go through this menu again. You can then install and use drivers(like older chipset ones, or LAN/Wifi) that haven’t been officially signed by Microsoft.
      My ComputersSystem Spec

  10. Try3's Avatar
    Posts : 2,432
    Windows 10 Home x64 and Pro x86
       #10

    ignatzatsonic said: View Post
    That's a 10 year old CPU. A powerhouse when it was introduced, but I wonder how old a CPU can be and still accept Windows 10?
    My own 2005 CPU [Dell Inspiron 9300] is happy with Windows 10 up to & including Version 1709. The only limitations were
    - Task scheduler could not wake it from sleep [despite all appropriate settings being correct]
    - It could not run PowerCfg -BatteryReport [so I had to use -Energy instead and plough through the results to get the two lines I actually wanted].

    My own non-powerhouse 2010 CPU [Dell Inspiron 1545] is happy with Windows 10 including Version 1809 & hopefully beyond. There are no limitations.

    [Edited 26 June 2019 - Task scheduler reference added because my post was otherwise seriously misleading]

    Denis
    Last edited by Try3; 26 Jun 2019 at 11:21.
      My ComputerSystem Spec


 
Page 1 of 8 123 ... LastLast

Related Threads
Solved Freeze at 33% during update to 1709 in Windows Updates and Activation
Running 1703 on Intel Hardware w/ SoundBlaster audio and Nvidia GPU. Samsung SSD. Peripherals include wireless 360 receiver and Logitech wireless keyboard/mouse dongle. Machine badgering me about updating to FCU, and "chooses" to update even...
Hi all, I am having a frustrating issue at the moment, where my pc is taking 20 minutes to boot - this is primarily because it keeps trying to install several windows updates, gets to 30% after multiple restarts, then fails, and says "recovering...
Hello How to turn off driver update via regedit ? os windows 10 fall creatros update 1709 Thank you
Hi! When Windows update has just installed all the pending updates, the start menu don't show the option "update and restart", only "restart", "shutdown" and "sleep". It's normal?? I have Windows 10 PRO Fall Creators Update 64 bits. Thanks!
Hi, Since the update, Microsoft is pushing strange Update Packages to me. Before the Update, everything was fine, now the Text says i.e.: for AMD64 based systems KB4051963 but what the heck, I do have a x64 based system (Intel). I don't...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:06.
Find Us