Just powered up the W10 lappy after a short period of disuse to find that the "Settings" window won't launch - I was trying to get to the Windows Update window at the time, because that function didn't seem to be working either.

 

Advice on the web was that both problems are  possibly "Policy" related and probably caused by an earlier update.

 

Of course, cleverly, none of this can be confirmed on the local machine as the Windows Update/History function is kiboshed.

 

Even going to the command line (As recommended in some forums),  I've found that the Command Line substitute for Windows Update, Wuauclt - the windows Update command line utilty, doesn't appear to work.

 

Any positive advice on this appreciated - as this is my second major isuue with W10 within a week.

 

 

Nick

Solveded.

 

Running the command line " net stop wuauclt " and getting the response "Not done. System error 5" gave me the clue. . . . or not.

 

 

You have to turn the Windows Update service off in Control Panel and then restart.

 

The thing then restarts (iIcluding Windows Update in the background) and then precedes t0 download shed loads of "Missed" updates, restarting several times whilst it configures the system (Mine took about 15 minutes with 3 re-starts), before it eventually arrives at the sign-in window. Hoorah !

 

So, for those who are interested, the menu descent is Control Panel - System and Security - Administrative Tools - Services followed by locating Winupdate in the "Extended Services" category , clicking on it to bring it up, and then clicking on the "Stop" button to turn it off, Exit the meu system and restart the machine.

 

 

Nick

Or simply get to services via the run command

Why does it have to be so difficult?

As I said previously, I had difficulty making valid command line instructions work from any directory, including the root.

 

So I went with what worked - that part of the graphical interface that did work. So happens  that it is better known than little used commands in the command line ?

 

 

Nick

W10 generally works for me except for updates.

 

I've a W10 desktop and a netbook and they both need a lot of work to get to pickup the  updates.

 

With previous versions there were numerous ways to get the updates to trigger or even download the files and do it manually but not with 10. Even getting to the logs is monumental PITA.

About a month ago while surfing, I lost "internet" on my notebook running Win10, I tried connecting it directly to router, still no good, other devices in house see internet okay via WiFi. Initially internet had become "flaky" then "limited" and then no internet. I grabbed wife's old lappy and went looking for fixes, found that it did seem to be one of the things that happened after upgrading to Win10, but none of the suggested fixes worked, so I restored to a date in late June - now all is good!  Having been faced with that inconvenience I then went looking for the Aniv update, and grabbed it - still all is good with the continued annoying "very busy/hang up" that were never in evidence when running Win7 64bit.

 

Why, as soon as you request a new internet address, does the "not responsing" notification get displayed - and then the new site/page gets launched?

 

Edit:- actually if I am being honest, when I found that I had lost access to the internet, I just continued with some other ploy and smugly waited for my wife to start complaining about the same problem as she would have been using her iPad - after 30 minutes I gave up and checked up on what she was up to that did not need internet access only to find that she was not having any internet access problems!

Edited 22 August, 20169 yr by rum4mo

Probably Wifi driver issues.

The ones pumped out by Windows update aren't always quite the same as those by the computer manufacturers. Manufacturers tend to tweak them, so the generic ones direct from the Wifi chipset manufacturer don't work correctly.

Used to happen a lot with Dell stuff which only worked correctly with the driver from Dells own update site.

Dad was forever having issues when he had his Dell laptop with this

Best thing to do is update to the Anniversary Edition, it resolved all of the minor glitches that I had, Windows 10 is now more stable and better than the previous and first editions.

Probably Wifi driver issues.

The ones pumped out by Windows update aren't always quite the same as those by the computer manufacturers. Manufacturers tend to tweak them, so the generic ones direct from the Wifi chipset manufacturer don't work correctly.

Used to happen a lot with Dell stuff which only worked correctly with the driver from Dells own update site.

Dad was forever having issues when he had his Dell laptop with this

I remember when I had a working Dell desktop replacement big laptop computer (graphs card died, next 2nd hand graphics card now dead), there was a short period in time when if using the ident/build reference number, you could check/get latest updates to Dell drivers - then all went quiet!  Move forward to my small Acer Aspire one notebook computer, same thing - now no mention of that one's model number range, so - oh bother! (I did check that initially)

I remember when I had a working Dell desktop replacement big laptop computer (graphs card died, next 2nd hand graphics card now dead), there was a short period in time when if using the ident/build reference number, you could check/get latest updates to Dell drivers - then all went quiet! Move forward to my small Acer Aspire one notebook computer, same thing - now no mention of that one's model number range, so - oh bother! (I did check that initially)

Dell still do it and have an update app, but but have a limited support cycle for older kit.

You can use the service tag detector on their site. If an update fails, manually download and install it.

The Dell update app on that laptop, after a couple of years or so, just made some complaint why it could not now do anything for me wrt updating things. So long ago that I've forgotten, maybe this winter, I will find time to "bake" both the original and the replacement graphics cards to try to fix their "duff solder/soldering" issue(s) and try to update it - or more probably bin it!

 

I think that that nVidia soldering issue ended up with "class action" in USA, here in Europe, we just need to live with it!