Stopping the Win10 download nagging

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Slytod
    PCHF Member
    • Jan 2017
    • 269

    #16
    Thanks. Was just having breakfast coffee so downloaded and opened the MS β€œfix” cab file while I had the time. Didn’t see that tick page. But all seems ok for now; if there is no attempt to reinstall in the next few weeks that’ll be evidence it’s working. Cheers.

    (Just had a thought, maybe because, as the wanted driver was already in place, I didn’t uninstall anything, just stopped it installing (hid it) again.)

    Comment

    • phillpower2
      PCHF Administrator
      • Sep 2016
      • 15205

      #17
      Alternatively you can go into Devices and Printers in the Control Panel, right click on the icon for your computer, click on Device installation settings, select the No option then Save the changes as shown in the screenshot, it does mean that you would need to manually search for driver updates, no biggy imo as drivers should never be updated unless it is to address a known issue.

      Comment

      • veeg
        PCHF Director
        • Jul 2016
        • 8977

        #18
        So shall we mark this thread?

        Comment

        • Antman
          PCHF Member
          • Oct 2016
          • 316

          #19
          Originally posted by Slytod
          …Didn’t see that tick page. …

          (Just had a thought, maybe because, as the wanted driver was already in place, I didn’t uninstall anything, just stopped it installing (hid it) again.)
          An error of omission on my part >

          [ATTACH]1885[/ATTACH]

          Comment

          • Antman
            PCHF Member
            • Oct 2016
            • 316

            #20
            Yes. The Antman is blind.

            Comment

            • Slytod
              PCHF Member
              • Jan 2017
              • 269

              #21
              Update

              It seemed that things were finally working, but I then experience two BSODs, which was a new phenomenon. So I decided to run DDU anyway in case there was anything NVIDIA installs in more recent versions that was causing a problem; even though an earlier version shouldn’t use it. Even went into Safe Mode to do so. That managed to get all the icons on the desktop all over the β€œblessed” place. Anyway, went through that and reinstalled the older driver once more, for the last time.

              Then, to be sure I used the control panel method to turn off auto updates. Expected all to be well again.

              Just had MS have the damned gall to tell me there is an update I need to install, and when I checked it is the *&%^$Β£ NVIDIA driver again ! It is driving me utterly insane.

              I’ve run the .diagcab file again and am hoping it will remove any more nagging as I refuse to go through that uninstall reinstall nonsense any more. It’s more than flesh & blood can stand.

              Comment

              • Slytod
                PCHF Member
                • Jan 2017
                • 269

                #22
                Oh and I know it is an unrelated question but …
                What the heck is something called Windows Ink Workspace doing on my taskbar, and how do I get rid of this unrequested recent secret installation ? Or at least turn it off ?
                Cheers.

                It appears to be more control freakery from MS. I’ve tried this http://www.thewindowsclub.com/disabl...-ink-workspace and hope it works. I still see it on the taskbar but haven’t the heart to restart right now.

                Comment

                • phillpower2
                  PCHF Administrator
                  • Sep 2016
                  • 15205

                  #23
                  Originally posted by Slytod
                  What the heck is something called Windows Ink Workspace doing on my taskbar,
                  No idea and unless you have a touchscreen it is a total waste of time having it, hopefully the fix you have will resolve the issue.

                  To the BSOD you mention;
                  1. Copy any dmp files from C:\Windows\Minidump onto the desktop.
                  2. Select all of them, right-click on one, and click on Send To> New Compressed (zipped) Folder.
                  3. Upload the zip folder using the Upload a File tab.

                  Comment

                  • Slytod
                    PCHF Member
                    • Jan 2017
                    • 269

                    #24
                    Can’t say I even noticed it until my use of Safe Mode.
                    To be honest I’ve not had a BSOD since the DDU & reinstall. Just had a crash out of the game but that is as common as expected for the older driver, now.
                    But I’ll attach them in case someone would like to see if they can spot anything.
                    Thanks.

                    Comment

                    • phillpower2
                      PCHF Administrator
                      • Sep 2016
                      • 15205

                      #25
                      Please bear with me here as there is a fair bit of explaining for me to do and links with additional info for you to read, this so that you will understand that it may take a bit of work to resolve this and it may not be a quick fix.

                      Dump files are often pretty straight forward to decipher and the suggested fix also pretty straight forward, your dump files are a bit more complex

                      The particular driver identified in your two crashes is MODULE_NAME: dxgmms2 which is a Windows as opposed to an Nvidea driver, possible causes of this may include a conflict with another driver and a problem with Windows itself as two examples, with such a scenario the first thing that I normally check is if any other drivers have failed to load etc, below is a list of drivers that are shown to have failed to load in your crash dump, links provided so that you can see the types of issues/problems with these drivers can cause or to explain what the driver does etc;

                      Unloaded modules:
                      fffff80c[ICODE]20e00000 fffff80c[/ICODE]20e3c000 WUDFRd.sys
                      fffff80c[ICODE]20e00000 fffff80c[/ICODE]20e3c000 WUDFRd.sys
                      fffff80c[ICODE]1e930000 fffff80c[/ICODE]1e93f000 dump_ataport
                      fffff80c[ICODE]1e950000 fffff80c[/ICODE]1e95c000 dump_atapi.s
                      fffff80c[ICODE]1e980000 fffff80c[/ICODE]1e99d000 dump_dumpfve
                      fffff80c[ICODE]209f0000 fffff80c[/ICODE]20a0c000 EhStorClass.
                      fffff80c[ICODE]1d700000 fffff80c[/ICODE]1d71c000 EhStorClass.
                      fffff80c[ICODE]1e510000 fffff80c[/ICODE]1e524000 dam.sys
                      fffff80c[ICODE]1d1f0000 fffff80c[/ICODE]1d1fb000 klelam.sys
                      fffff80c[ICODE]1e810000 fffff80c[/ICODE]1e81f000 hwpolicy.sys

                      Blue Screen dxgmms2.sys thread post on the GEFORCE forum here

                      Please take the time to read through the above and then get back to us, one of us will be around.

                      Comment

                      • Slytod
                        PCHF Member
                        • Jan 2017
                        • 269

                        #26
                        Wow !

                        As mentioned, since the DDU thing in Safe Mode (and the sudden appearance of the Windows Ink Workspace) and subsequent reinstall of the older NVIDIA drivers, I’ve not had any more BSODs. So I’m not knowledgeable enough to know how much value there is in analysing the dump files. But if you think it might shed light on the remaining issue of the graphics crashing out occasionally, then I guess it is likely worth it. Just to say when the graphics does crash it it usually recovers sufficiently for the game window only to be no more use (after β€œrecovery” it just goes white) and the rest of the windows/system is ok, so I can stop the game task and start again. But on rare occasions there is no recovery and one can only recycle the power.

                        I’ll try to find time to look at the links etc. later today.

                        BTW I’m still being nagged about the NVIDIA upgrade but it may be my own fault, not rebooted since I turned off (I hope) the driver reminder. Must do that today too.

                        Read through the driver list, have to say it meant little to me other than β€œit does something I’m not normally aware or concerned about and it’s a problem”.
                        Just started on that forum thread now. I’m using 347.88 too Ah 22 pages, I think this is all going to sound horribly familiar, where nothing suggested as a solution works and one gives up the will to live unless one puts up with the occasional crashes from 347.88.

                        Comment

                        • Slytod
                          PCHF Member
                          • Jan 2017
                          • 269

                          #27
                          Apologies but skipped to the last page of that GeForce forum thread. It seems like they are still blaming Microsoft even though it appears that it is only their GeForce cards that are affected. Looks like an easy excuse not to progress the issue to me. Even if it is a Microsoft issue as they claim, other card manufacturers either don’t fall foul of it, or have put in a work-around. It used to crash on Win 7 too, in fact the deciding reason I installed Win 10 was the hope that it would fix the issue; but it didn’t. Now I live with a couple of crash outs a day on average. None if I don’t go back and waste my time on the game.

                          Comment

                          • phillpower2
                            PCHF Administrator
                            • Sep 2016
                            • 15205

                            #28
                            Originally posted by Slytod
                            Seems like they are still blaming Microsoft even though it seems that it is only their GeForce cards that are affected.
                            Unfortunately not as AMD cards are also affected see thread here + AMD products are equally affected by the same WUDFRd.sys driver that you are.

                            An 11 month old thread post on the Nvidea forums regarding the same issue here there are a couple of suggestions there but please note that I have not used them so cannot say whether they will help, if you do try any of them be sure to create a new system restore point before each one that you try.

                            Comment

                            • Slytod
                              PCHF Member
                              • Jan 2017
                              • 269

                              #29
                              Interesting. It’s been year or two since I last checked but at the time I didn’t come across any AMD references. Well that at least clarifies things a bit and stops me contemplating buying an AMD replacement graphics board that I can ill afford. Cheers.

                              It’ll probably be mid-week before I can get around to trying anything suggested in the reddit thread, but thanks for that. I’ll see what they have to suggest.

                              Comment

                              • phillpower2
                                PCHF Administrator
                                • Sep 2016
                                • 15205

                                #30
                                No worries, please keep us posted and any other questions ask away (y)

                                Comment

                                Working...