Magic, the problems are only appearing after the anniversary update. Not sure you already have, it's been out since the beginning of August.
MrS
Yes any open work will be closed and any workunits will be stopped while the pc is updated to the Anniversary Edition Win10 updates, and yes if closing them means work is lost then yes it is lost. I did not set it to do or not to do them, but it is slowly happening on all of my pc's, one every other day or so. It is taking an hour or so for most of my pc's, they are mostly 6 core AMD cpu's with 16gb of ram in each one and a 120gb SSD. I do have a few dual quad core Xeon based pc's but they haven't been upgraded to the Anniversary Edition yet. ALL of my pc's that could be upgraded to Win10 for free were done before it expired, and yes I do know that people CAN still upgrade for free, or could a week or so ago, if they really wanted too.
I don't think the anniversary update itself is of much concern - obviously it takes some time and will require a reboot. It's the regular updates afterwards which are the issue now.
Magic, the problems are only appearing after the anniversary update. Not sure you already have, it's been out since the beginning of August.
MrS
Oh yeah I have done that anniversary update on all of mine.
It does the download and then I tell it when to do the reboot and I do mine one at a time so I can suspend the tasks and get back up and running asap.
I never let things slide since I not only do all this Einstein GPU work but I do even more for Cern including alpha work.
I only had one that used to be Windows 8.1 but I sure was glad to get rid of that.......I didn't mind Win7 but did the upgrade on those just to stay up to date and help others doing that (I'm an *Insider* for microsoft)
Generally I'm a fan of Win 10.. but this is really going too far. What if you have unsaved work open? Will the OS simply kill countless of productive work worldwide? Or would that keep it from rebooting unattended? BTW: currently I'm glad the anniversary update keeps throwing an error on my main PC.
MrS
I don't have an exhaustive dataset; but after one forced reboot I logged back in to find a paint window with an unsaved screenshot still open with the data in it. Dunno if that's limited to some MS apps or if they've found a general solution to unsaved data over a reboot.
That would be neat - if they want to reboot unattended and without questioning, they should return the machine to a state as close to the original one as possible. And if a user was logged in before the reboot they should log him in again, with the same screen-lock status as it was. I don't think this is the right forum for such demands, though.
And if a user was logged in before the reboot they should log him in again, with the same screen-lock status as it was. I don't think this is the right forum for such demands, though.
Making demands, no, it is not the right forum. Helping each other run BOINC, it is. I reviewed the (skimpy) description of the function in which they offer to log you back in again after update restarts if you authorize use of the credentials, and decided it appeared to claim to do so ending in a locked status (which is what I want).
I can't yet advocate it, as I've not experienced an unrequested update restart yet to let me observe the behavior, but if enabling that option safely lets me avoid losing hours of BOINC processing in the night, this whole matter is somewhat less obnoxious to me.
In case you want to try it, it is under Windows Update Settings|Advanced Options|Use my sign in info to automatically finish setting up my device after an update.
Microsoft has this to say about it
Quote:
Some updates require you to restart your PC and sign in to Windows in order to finish installing the update, which means you might sign in to Windows and find you can’t use your PC until the update is finished. Windows 10 helps prevent this from happening by allowing Windows to use your sign in info to create a special token. This token is used to automatically sign in after a restart, finish setting up your PC, and then lock your PC to help keep your account and personal info safe.
I reviewed the (skimpy) description of the function in which they offer to log you back in again after update restarts if you authorize use of the credentials, and decided it appeared to claim to do so ending in a locked status (which is what I want).
I can't yet advocate it, as I've not experienced an unrequested update restart yet to let me observe the behavior, but if enabling that option safely lets me avoid losing hours of BOINC processing in the night, this whole matter is somewhat less obnoxious to me.
The last day or two a regular update for Windows 10 anniversary edition machines was distributed. My first machine to get updated was one for which I had not set the token-based option to log back in after restart for an update. On that machine I lost about 15 hours of processing time before I noticed and got it fixed.
On the second machine the option functioned as desired. As I had neglected to set my current overclocking commands active in my delayed startup file I did lose about 15% productivity for about 10 hours, but I think I have fixed that problem.
The third machine is the one I am typing to you on and I believe with current settings it will do a restart in a few hours and I believe I have my startup file correctly configured to set my current overclocks.
The third machine is the one I am typing to you on and I believe with current settings it will do a restart in a few hours and I believe I have my startup file correctly configured to set my current overclocks.
In the Update settings section of Windows 10 Anniversary Edition Settings, there is an "Active Hours" setting. Mine was set to 8:00 a.m. through 5:00 p.m. which may be the default. Earlier today I had seen the alert that updates were available, and I requested that they be installed but left the required restart to be performed automatically, wanting to see when and how it would be done.
Base on my temperature logging application, BOINC processing ceased promptly at 5:30 p.m. It resumed at 5:36 p.m., and without my having touched a key, the restart/login/lock option worked. I have a batch file triggered by my user ID login which runs Nvidia Inspector command line commands to set my desired overclocks, and by 5:36 p.m. BOINC work had resumed running at full speed.
By good luck (helped out by the view on BOINCTasks from another machine) I was watching the screen as it rebooted. While there was the light blue screen with percentage progress reporting finishing up the update stuff before the actual login, there was never a view of my desktop. Ten minutes later I used the usual entry method for a locked session.
As someone had posted some hopeful sounding observations regarding active tasks being restored, I left behind as a test case two browers and two editors. The editors deliberately had an extra line of text not yet saved.
After the restart, only one of my four test applications appeared--Google Chrome. And it did have the set of tabs I had left open (which is not my default startup set of tabs).
Firefox was not already opened, and did not remember where I had been when I opened it.
Textpad was not opened, and lost my text added after last save.
Microsoft Word was not opened, but when I opened it advised me that it had an autosave available, which did have the extra line.
In summary, it restarted fine, and got me going again in BOINC just as I would like, without leaving an open desktop or suchlike ludicrously obvious security problem. It is likely there is a somewhat more obscure security problem, however. But on my trial set, there was not enough preservation of open applications to be helpful.
As my predominant concern regarding Einstein of this difficult to block Windows update restart was lost Einstein output--possibly for days if I were away on a trip--this outcome reduces my dismay materially.
ExtraTerrestrial Apes
)
Yes any open work will be closed and any workunits will be stopped while the pc is updated to the Anniversary Edition Win10 updates, and yes if closing them means work is lost then yes it is lost. I did not set it to do or not to do them, but it is slowly happening on all of my pc's, one every other day or so. It is taking an hour or so for most of my pc's, they are mostly 6 core AMD cpu's with 16gb of ram in each one and a 120gb SSD. I do have a few dual quad core Xeon based pc's but they haven't been upgraded to the Anniversary Edition yet. ALL of my pc's that could be upgraded to Win10 for free were done before it expired, and yes I do know that people CAN still upgrade for free, or could a week or so ago, if they really wanted too.
I don't think the anniversary
)
I don't think the anniversary update itself is of much concern - obviously it takes some time and will require a reboot. It's the regular updates afterwards which are the issue now.
MrS
Scanning for our furry friends since Jan 2002
ExtraTerrestrial Apes
)
Oh yeah I have done that anniversary update on all of mine.
It does the download and then I tell it when to do the reboot and I do mine one at a time so I can suspend the tasks and get back up and running asap.
I never let things slide since I not only do all this Einstein GPU work but I do even more for Cern including alpha work.
I only had one that used to be Windows 8.1 but I sure was glad to get rid of that.......I didn't mind Win7 but did the upgrade on those just to stay up to date and help others doing that (I'm an *Insider* for microsoft)
ExtraTerrestrial Apes
)
I don't have an exhaustive dataset; but after one forced reboot I logged back in to find a paint window with an unsaved screenshot still open with the data in it. Dunno if that's limited to some MS apps or if they've found a general solution to unsaved data over a reboot.
That would be neat - if they
)
That would be neat - if they want to reboot unattended and without questioning, they should return the machine to a state as close to the original one as possible. And if a user was logged in before the reboot they should log him in again, with the same screen-lock status as it was. I don't think this is the right forum for such demands, though.
MrS
Scanning for our furry friends since Jan 2002
ExtraTerrestrial Apes
)
Making demands, no, it is not the right forum. Helping each other run BOINC, it is. I reviewed the (skimpy) description of the function in which they offer to log you back in again after update restarts if you authorize use of the credentials, and decided it appeared to claim to do so ending in a locked status (which is what I want).
I can't yet advocate it, as I've not experienced an unrequested update restart yet to let me observe the behavior, but if enabling that option safely lets me avoid losing hours of BOINC processing in the night, this whole matter is somewhat less obnoxious to me.
In case you want to try it, it is under Windows Update Settings|Advanced Options|Use my sign in info to automatically finish setting up my device after an update.
Microsoft has this to say about it
archae86 wrote:I reviewed the
)
The last day or two a regular update for Windows 10 anniversary edition machines was distributed. My first machine to get updated was one for which I had not set the token-based option to log back in after restart for an update. On that machine I lost about 15 hours of processing time before I noticed and got it fixed.
On the second machine the option functioned as desired. As I had neglected to set my current overclocking commands active in my delayed startup file I did lose about 15% productivity for about 10 hours, but I think I have fixed that problem.
The third machine is the one I am typing to you on and I believe with current settings it will do a restart in a few hours and I believe I have my startup file correctly configured to set my current overclocks.
archae86 wrote:The third
)
In the Update settings section of Windows 10 Anniversary Edition Settings, there is an "Active Hours" setting. Mine was set to 8:00 a.m. through 5:00 p.m. which may be the default. Earlier today I had seen the alert that updates were available, and I requested that they be installed but left the required restart to be performed automatically, wanting to see when and how it would be done.
Base on my temperature logging application, BOINC processing ceased promptly at 5:30 p.m. It resumed at 5:36 p.m., and without my having touched a key, the restart/login/lock option worked. I have a batch file triggered by my user ID login which runs Nvidia Inspector command line commands to set my desired overclocks, and by 5:36 p.m. BOINC work had resumed running at full speed.
By good luck (helped out by the view on BOINCTasks from another machine) I was watching the screen as it rebooted. While there was the light blue screen with percentage progress reporting finishing up the update stuff before the actual login, there was never a view of my desktop. Ten minutes later I used the usual entry method for a locked session.
As someone had posted some hopeful sounding observations regarding active tasks being restored, I left behind as a test case two browers and two editors. The editors deliberately had an extra line of text not yet saved.
After the restart, only one of my four test applications appeared--Google Chrome. And it did have the set of tabs I had left open (which is not my default startup set of tabs).
Firefox was not already opened, and did not remember where I had been when I opened it.
Textpad was not opened, and lost my text added after last save.
Microsoft Word was not opened, but when I opened it advised me that it had an autosave available, which did have the extra line.
In summary, it restarted fine, and got me going again in BOINC just as I would like, without leaving an open desktop or suchlike ludicrously obvious security problem. It is likely there is a somewhat more obscure security problem, however. But on my trial set, there was not enough preservation of open applications to be helpful.
As my predominant concern regarding Einstein of this difficult to block Windows update restart was lost Einstein output--possibly for days if I were away on a trip--this outcome reduces my dismay materially.