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

Page 8 of 8 FirstFirst ... 678
  1.    #71

    Denis,
    All good, happy to accept we've had a bonus with Win 10 lasting this long. With the X300 drivers there were some minor irritations with the tag-based dell-supplied X300 drivers around the time of coaxing the unit into Win10 and I settled on the current one as least problematic - and I can't recall an issue with it tbh. However the ATI software is not so good, sometimes PC started very slow and it's the ATI sub-system hogging the CPU for some random reason. I think it was that sort of issue stopped the device coming out of sleep properly, and may have just settled (randomly on the drv I last tried in the mix) with the combo of ATI components that caused fewest glitches on wake up. This, or another trial-and-error way to get it done. Vaguely recalling details as my memories are slowly trickling back! Current version is 8.360.0.0 signed

    If the graphics card turns out to be the issue, then perhaps (slim chance) MS will eventually fix it as they did with the broadcomm wireless hardware that had troubles pre 1709. In that case they responded to queries from a few in that minority, even though only a few fails were reported via telemetry. I'd not expect to get anywhere with this issue though, and antique devices are not a big target for their efforts. It is a pity to be caught out as the memory, CPU and disk space are explicitly checked, and [I suspect] graphics card and other key items are silently checked pre-install for known issues. In our case they seem to pass, but then fail on deployment. It maybe just because something equally obscure has been missed in testing by MS as they've moved from 1709 to 1803. It may not be the graphics card, and unless someone can vouch differently I will assume that's the conclusion
    One longer timed wake up test also failed for me just now so I am giving up on the Dell for the evening and turning to the Tamnnavulin (whisky) instead! Cheers!!
      My ComputerSystem Spec

  2. ThrashZone's Avatar
    Posts : 5,095
    3-Win-7Prox64 2-Win10Prox64
       #72

    Hi,
    Looked at ebay 15.us for a gt640 1 or 2gb card can't remember
      My ComputersSystem Spec

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

    I have checked through my notes & my backup drives and the MOBILITY RADEON X300 display card driver that worked is the one at
    Microsoft Update Catalog ATI MOBILITY RADEON X300

    It is the newest one in the list and is labelled as v8.561.0.0 dated 12/1/2008 but actually results in version 7.14.10.8333 dated 8/25/2006 - numbering systems at Dell & its OEM suppliers are often completely different.

    I have a note about having first tried the one labelled 8.501.0.0 but it "did not work" - I have not kept any details about what was wrong with it.

    You will also see an entry in the MS update catalog page for MOBILITY RADEON X300 (Microsoft Corporation - WDDM) which is what mine reports itself as. My notes from that time have been 'tidied up' but I believe that I tried both the one I have explained above and this one and they both turned out to be the same thing.

    Dell's XP driver is still available and is labeleld v8.162 dated 14 Sep 2005. Also known as R106547.EXE it was accompained in 2005 by a display card bios update [R101351.EXE] which I assume I installed at the time but about which I have no records.

    If you can find a download link for your 2007 [Vista?] driver then I could experiment with it if that helps.

    Denis
      My ComputerSystem Spec

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

    Richard,

    Once again I have missed a post of your [#71] because I was very slow in compiling my own post.

    Your "sometimes PC started very slow" problems might be as a result of display driver differences as I do not experience the same. Do you make system images? Otherwise you'd probably not be comfortable with experimenting with different drivers.

    About "Current version is 8.360.0.0 signed" - is that the one you referred to as 14 mar 2007? Is this version number also reported by Device mgr [which is the only common basis upon which we can comapre them given their fondness for different version numbering systems]?

    I remember that ethernet network adapter business.. I just disabled mine in Bios and have left it disabled ever since.

    About "graphics card and other key items are silently checked pre-install for known issues. In our case they seem to pass, but then fail on deployment" We both tried the Update assistant at some stage in our ver 1803 updating failures. It leaves compatibility reports in C:\$GetCurrent\Logs but I cannot find anything in them to shed any light on the updating block.

    About "It may not be the graphics card, and unless someone can vouch differently I will assume that's the conclusion" During early Windows 10 days some other users concluded that strange failures such as the Task scheduler wakeup failure were caused by chipset incompatibility.
    - Funnily enough, whilst rummaging through my archives for info on display driver versions I came across a chipset update R114079.exe along with an unexplained note "not done".
    - I found a publication date of 2006 but a further reference to it being from 2005 and I then found it online at Dell drivers & downloads with a 2013 date.
    - I hesitate to do anything with it at all given my earlier decision not to install it. I think I'll leave it alone as Windows 10 will have installed whatever it considered best.
    - I do not know where in Device manager to look for chipset drivers so I can check what has already been installed.

    So that's probably it.

    All the best,
    Denis
      My ComputerSystem Spec

  5.    #75

    Good morning Denis
    I decided to try the chipset update. Why not, curiosity got he better of me.
    I rebooted after the chipset update. A few extra flashes of 'stuff' I didn't spot at restart, but nothing untoward, it seemed. So next obvious thing to do was try an update!
    I had suspended all the windows update options from the settings control panel, so being lazy I started the upgrade assistant. And for the first time, this failed in the first check phase with the CPU check saying CPU <1GHz and 1GHz is required. Now we know we have the 2GHz so that's most odd. Checked in system and it shows the 2G but that it's at 798Mhz. So I'll do a bit more tweaking now...
    Can't help thinking that Peter (Ex-Brit) in Toronto has succeeded with his 9300 - in the midst of our exchange yesterday he reposted the PNPclean advice. Strangely enough I forgot to do that step before the reboot/update attempt, so will do so now, as well as look at enabling SpeedStep in the BIOS. Hope to be back soon...
    Richard
      My ComputerSystem Spec

  6. jimbo45's Avatar
    Posts : 7,662
    Windows / Linux : Centos, Ubuntu, OpenSuse
       #76

    Hi there
    depending on what you need to do on W10 -- why not run the latest (1903) version as a Virtual Machine until you can get hardware issues sorted out on your PC --It will run fine -- I've even run W10 1903 as a VM on an XP Host !!!!!!! - yes it can be done!!!.

    While not a long term solution for you it would at least give you the chance to see if some of your programs will keep working on the newer versions of Windows..
    Installing a Virtual machine these days is a doddle if you use Virtual Box or VMWare player.

    This I know could be overkill for what you want but at least it "keeps you in the game" with current W10.

    Cheers
    jimbo
      My ComputerSystem Spec


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

    Can't help thinking that Peter (Ex-Brit) in Toronto has succeeded with his 9300
    No, he has an Alienware computer not an Inspiron.

    PNPclean advice
    It will have no effect. Clean installs fail and they do not depend on the installed drivers.

    Denis
      My ComputerSystem Spec

  8.    #78

    One more thing... I've just had the std BSOD from the attempt to update, results of failure not showing up on settings page/update history, curiously. Reviewing the setupdiag output reveals nothing, as usual, but this is new ground as previous update attempts were falling into either 1803 or 09 and this one was the first that attempted to apply TargetOSBuildString =10.0.18362.1 (19h1_release.190318-1202). Looking at the setup logs I see for the driver migrations it runs a cmd for pnpclean so whilst potentially of some use at an earlier stage in proceedings, it being included in the MS script suggests that is a pointless manual task now, or always was pointless for clean builds. I may try to get a boot log diagnostic to see which driver is causing the bsod - not sure why that is so difficult, but these challenges are here to keep us entertained! Cheers.
      My ComputerSystem Spec

  9. Ztruker's Avatar
    Posts : 8,507
    Windows 10 Pro X64 1903 189362.439
       #79

    See the 2nd post by Andre Da Costa Microsoft MVP, in this thread:

    Tried Everything. Can't Update Windows 10 Beyond v1709

    Press Windows key + X
    Click Command Prompt (Admin)
    Type the following command:
    rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
    Hit Enter on your keyboard
    Exit command prompt
    Restart

    If you have virtualization in the BIOS enabled, disable it then attempt the upgrade again.
      My ComputersSystem Spec

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

    Ztruker said: View Post
    See the 2nd post by Andre Da Costa Microsoft MVP, in this thread:

    Tried Everything. Can't Update Windows 10 Beyond v1709

    Press Windows key + X
    Click Command Prompt (Admin)
    Type the following command:
    rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN
    Hit Enter on your keyboard
    Exit command prompt
    Restart
    That's already been discussed above.

    Denis
      My ComputerSystem Spec


 
Page 8 of 8 FirstFirst ... 678

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 17:35.
Find Us