|
I post this here, in case someone else runs into this weird problem with the Fall Update of Windows 10:
After the update, I found that on every second start or restart of the computer, the task bar became irresponsive. Clicking on the task bar had no effect. I could not even click on Start in the lower left corner to shut down or restart the machine.
After wrestling with the issue for some time, I decided to check all device drivers. It turns out the Fall Update left me with the wrong driver for my NVidea video card. After updating the NVidea driver, the problem is gone.
Keep this in mind if you have a NVidea card in your machine.
Get me coffee and no one gets hurt!
|
|
|
|
|
I have lost my front facing camera due to the fall update - but I can't be bothered to fix it.
|
|
|
|
|
Maybe another driver issue? In my case I could not ignore the problem. The effect was too severe.
Get me coffee and no one gets hurt!
|
|
|
|
|
Definitely a driver issue - and also something called the "HP Accelerometer" program keeps telling me it is not compatible with this OS.
(It was prior to the update...)
|
|
|
|
|
I've encountered a couple of minor issues:
Sync is not available for your account
Resolved by removing my Office365 account from the "Access work or school" page.
Shut down doesn't
Trying to shut down the computer turned off the monitors and keyboard, but left the power on with the disk light solid. The only way to turn off was to hold the power button down for five seconds. On starting it up again, there was a "critical" error in the event log telling me that Windows restarted without being shut down cleanly.
Resolved by turning off "fast start" - a setting which is still only available in the "classic" control panel. 
Applications launching before sign-in
I restart my computer in the evening. When I sign in the next morning, all of my startup applications are already running. A scheduled task set to run at login shows a last run time of the previous evening.
Resolved by turning off the "Use my sign-in info to automatically finish setting up my device after an update or restart", under Settings ⇒ Accounts ⇒ Sign-in options.
IIS Error
One of my AppPools failed with a "Cannot read configuration file" error pointing to \\?\<EMPTY>.
The upgrade had left an invalid symbolic link in C:\inetpub\temp\appPools. Resolved by deleting the contents of the appPools directory.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I think some of the problems are based on Win 10 doing some half baked shutdowns that don't actually shut down.
Based on some searches, I created an icon <shutdown> with the target as "C:\Windows\System32\shutdown.exe /s /f /t 0" and it works. There is a similar one for a restart icon
"C:\Windows\System32\shutdown.exe /r /f /t 0"
These seem to work a treat. I have also found that rebooting an extra time after an upgrade seems to make things work more reliably. YMMV.
Ken
|
|
|
|
|
Been having shut down issues myself ... didn't bother yet to google about it, glad to find possible solution here 
One other issue I noticed ... laptop boots/wakes up every time (as far as I can tell) with airplane mode enabled (also didn't bother to find solution yet since I'm not totally sure if it isn't some sort of security "feature"  ).
modified 19-Nov-18 21:01pm.
|
|
|
|
|
I've had a similar issue with August 2017 update; but this was with Lenovo's sound card drivers.
I installed Windows 10 Fall Update on last week end, and happily did not encounter any issue (yet).
"I'm neither for nor against, on the contrary." John Middle
|
|
|
|
|
I guess just loading a bad NVidia Open CL driver like last time wasn't enough of a gotcha. 
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
once upon a time nads hinted at turning w10 into a service,
and every w10 update has had major issues (way more than any previous versions' updates ever)
it's not the haters - this is being reported in the press: ms are killing themselves
tell me, how are ms going write a SLA for that?
and ffs, how can they with a straight face ask businesses to adopt 10?
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
Reading about these issues, I think I'll wait. Installed it on a VM of mine (guinea pig), but how does MS expect us to survive the more frequent releases?
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 found we use SQL triggers a bit too much...
336 triggers on 1450 tables... (~23%)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
We hardly use triggers at all. Interesting that you have more than 5.
|
|
|
|
|
0 triggers on 0 tables (NaN%)
|
|
|
|
|
Isn't it 100%?
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Yes but it's also 42%, and 9001%, etc..
|
|
|
|
|
You obviously need one table per trigger to keep track of them. Then add a trigger for each table if any trigger changes. FTFY.
... such stuff as dreams are made on
|
|
|
|
|
Actually some of the triggers are there to log data changes (on important tables)...
Others are for data integrity...
And others are for sync with externals...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
I'd start looking for a new job before the house of cards falls down.
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: (~23%)
We got you beat. 247 triggers on 741 tables, exactly 1/3, although not intentional.
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
I avoid them as triggers too easily lend themselves to database-vendor specific code.
Installing Signature...
Do not switch off your computer.
|
|
|
|
|
My former bosses have about 10 - 15 triggers on each and every table, some of them thousands of lines long. A nightmare.
Especially after that experience: 0.0 triggers per table and not a single trigger more.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
That sounds awful... Our triggers are short (sometimes 2-3 triggers on the same event, just because they all do something else)...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The major part of the application logic took place in those triggers. Guess why I run out of job interviews when I hear 'Access' or ' Former Acess project that has ben ported to xxx'.
I have lived with several Zen masters - all of them were cats.
|
|
|
|
|
Hey! I'm (still) working on an Access project ported to SQL Server. Don't knock it if you haven't tried it!
Triggers are useful, but to embed business logic? Then even I would run away...
8)
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
