|
Disable the Windows Update service. Then manually turn it on and check for updates whenever your schedule allows, afterwards turning it back off. I have had good luck with this approach, but don't guarantee it. I miss Win 7s approach of telling you when updates were available, but not forcing you to update.
|
|
|
|
|
David O'Neil wrote: Disable the Windows Update service.
I've noticed that it re-enables itself. I'm looking into writing a service killer that checks every 60 seconds, as there are other services involved in the auto-update as well -- I don't have the link at the moment, when I find it again, I'll finish my service killer applet and post it here, mwahaha.
|
|
|
|
|
You'll get my five. That would be a used tool.
Right now Action Center is giving one recommendation, saying some apps stopped working but not giving any details. I'm keeping my eye on it. I also noticed a restart of the service once. I'm wondering if it does so at a full reboot. Since I hibernate all the time except once around the time it restarted, maybe that is the triggering factor.
|
|
|
|
|
David O'Neil wrote: Action Center
If you want to get rid of that I wrote this a couple years ago (only tested on Win7):
:: Action Center Disable
:: Disables ActionCenter and ActionCenterCPL
::
@ECHO OFF
SC stop wscsvc
SC config wscsvc start=disabled
TAKEOWN /F "%SystemRoot%\system32\ActionCenter.dll"
ICACLS "%SystemRoot%\system32\ActionCenter.dll" /grant:r administrators:F
REN "%SystemRoot%\system32\ActionCenter.dll" ActionCenter.bak
TAKEOWN /F "%SystemRoot%\system32\ActionCenterCPL.dll"
ICACLS "%SystemRoot%\system32\ActionCenterCPL.dll" /grant:r administrators:F
REN "%SystemRoot%\system32\ActionCenterCPL.dll" ActionCenterCPL.bak
ECHO Operations completed.
PAUSE > NUL
As long as you're logged in as admin it works great and if you ever want to re-enable just rename the *.bak to *.dll. Even if you don't re-enable the service Windows will do that automatically if it detects the DLLs as I found out.
|
|
|
|
|
|
Doesn't have anything to do with shut down - MS did its thing without shutdown or hibernate taking place, and WU service was at manual instead of disabled when I just checked. 
|
|
|
|
|
|
David O'Neil wrote: There may be other solutions as well. Looking forward to your solution if you get to it.
Reading the comments for Windows Update Blocker, it seems like it doesn't always work. At least no one reported malware, but then again, I wouldn't trust the average user.
Gads, the W10 Forums page link -- complicated stuff!
We'll see when I get around to trying my own solution -- it's on the low priority list right now.
Marc
|
|
|
|
|
Found a poor man's version that I think works. Create a bat file with the following:
@echo off
:while1
sc stop wuauserv
sc config wuauserv start= disabled
timeout 60
goto :while1
Open a command prompt as admin and run the bat.
Any improvements are appreciated - I've never been a knowledgeable bat file creator. I suspect with some more work I could hide the command prompt from the taskbar using AutoHotKey, but I'm lazy. But I can place it on a new desktop that I never look at!
Tested it by setting wuauserv to manual in between the 60 second intervals. Had to F5 the Services pane after the 60 seconds hit. Successfully disabled the service!
Will other services you hinted about also need to be stopped, or will just the main wuauserv be enough to kill the updates?
I'll place a copy of this in the lounge in case others want to play.
|
|
|
|
|
Okay, so since I know all about Windows updates, I decided to not do an f'ing thing today, reboot every time to install updates. Every damn time the update fails. But don't worry, that's just how Windows updates goes... lets see:
Cumulative update is awaiting restart.....
for the nth time I'll restart and the f***er still doesn't install. But that's okay, it's the way updates work.
What a POS
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I am still using Win 7 good as old days and as it is PC I had the liberty to choose.But I am thinking about buying new laptop hope that I should delay that a little further.
|
|
|
|
|
Microsoft do seem to have a habit of putting one feature into an OS that's guaranteed to p*** people off in a big way.
With Vista it was that godawful UAC system which soon had people screaming at their laptops: "Yes, I AM trying to run a goddamn program on MY goddamn computer, you stupid bloody OS! Why do you think I bought the bloody thing?"
Net result: an otherwise good version of Windows became quite possibly the most unpopular of the lot.
With 10, it's the overly assertive update system that raises the hackles. Yes, updates are necessary and that's often going to involve a restart and a little bit of nagging but the way that it has been implemented in 10 can only be described as downright rude.
Net result: there are still a lot of people out there pining for the good old days of 7.
98.4% of statistics are made up on the spot.
|
|
|
|
|
I totally understand the frustration, also having vented here (or in the lounge) about losing unsaved work (on multiple occasions) due to an unwanted forced restart on Winten. Sadly, I see there is still no guaranteed way to prevent it. 
There is also the issue of resetting registry permissions and policies on some updates, but that's another rant!
"Go forth into the source" - Neal Morse
|
|
|
|
|
Sad to read such rants here on CP. "programmers" that don't know how to save work, how to install old drivers, how to setup Windows-Update (or are ranting about old versions and long solved problems), whining about how "good" Windows 7 was, it's a shame.
All workers should know the tools for the Job. As a programmer the OS is a big "tool" to know…
I think Noob-User discussions don't belong here...
|
|
|
|
|
What's sad is you missed the entire context of the rant.
Windows 7 *was* less invasive. Windows 8 was a steaming pile of ****, and Windows 10 primary feature is Microsoft trying to figure out someway to package it as a service.
Save work: I do save my work, but many times I have debug sessions going on for days (embedded systems). You think it's okay to reboot because of policy?
Install old drivers - why would I even have to do that?
You're an elephanting idiot.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
So if you plan a debug-session just set out updates (it's max is 35 days) - so no restart or Installation will happen.
If you don't need old drivers everything is fine - if you Need, you can install even drivers that didn't work anymore on Windows7 for very old devices on Windows 10.
I have no problem, if you have some unrational "believe" or sympathy for old OSes. From an objective point of view Windows 10 isn't perfect but much better than it's predecessors -and the experience arround updates is constantly improving.
P.S. I don't think you an idiot - just a little "nostalgic" about something you shouldn't be in professional life. Win7 time is over - accept it...
|
|
|
|
|
You are missing my point entirely. thrice, so, rather than hash a dead horse, have a nice day.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
modelTables.Single(kvp => kvp.Key == model.GetType()).Value.ForEach(mt => mt.BeginProgrammaticUpdate());
vs simply:
modelTables[model.GetType()].ForEach(mt => mt.BeginProgrammaticUpdate());
Oh yeah, I did! 
At least there's an assert that the key exists in the dictionary.
Or equally amusing:
(from rec in context.GetTable<T>() select rec).ForEach(m => AppendRow(dv, (T)m));
vs.
context.GetTable<T>().ForEach(m => AppendRow(dv, (T)m));
|
|
|
|
|
Marc Clifton wrote: At least there's an assert that the key exists in the dictionary.
You'll get a different exception, but you will get an exception in both cases if the key doesn't exist. 
But the first version has the added advantage of iterating over the entire dictionary, and calling model.GetType() once for every single item within it. Probably not a huge issue, but not the best for performance.
Also from x in collection select x seems to be fairly common with novice LINQ developers. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Also from x in collection select x seems to be fairly common with novice LINQ developers.
And when I wrote that, I definitely was. Still learning actually. Just now re-discovered that Select has version that includes the index!
|
|
|
|
|
So you were looking for models that are single you old cad:
Quote: modelTables.Single
|
|
|
|
|
RickZeeland wrote: So you were looking for models that are single you old cad:
As of June 24th, 2018, not any more! 
|
|
|
|
|
So that must be:
Quote: Love and marriage, love and marriage
They go together like a horse and carriage
This I tell you, brother
You can't have one without the other
Congratulations !
|
|
|
|
|
My favorite columnist, the late Paul DiLascia used to write in the header of his code, "If this code works it was written by Paul DiLascia. If not, I don't know who wrote it."
modified 11-May-18 17:28pm.
|
|
|
|
|
Rick York wrote: "If this code works it was written by Paul DiLascia. If not, I don't know who wrote it."
An a shorter version: "If this code works, it wasn't written by you!"
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
