Make sure that any programs (i.e. BOINC) that you want to auto start when OZS starts up are set in msconfig prior to upgrade. I made the mistake of blanking the BOINC boxes and I see no way to turn them back on. I may have to reinstall BOINC.

As far as I know, this is regulated through the registry, not through Msconfig/startup.

Before trying anything else, open BOINC Manager, and then depending on BOINC version:
7.4 and before, Tools->Options
7.6 and later, Options->Other options...

Now uncheck "Run Manager at login?" and OK if checked and then do that again to check this option.
Or just check "Run Manager at login?" if unchecked, then OK.

This will start BOINC at Windows login.

It's even more subtle than that. For user-mode installations (which all GPU crunchers with BOINC v7 will be using, and all new users will use by default), BOINC Manager always runs at login:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run]
"boincmgr"="\"C:\\BOINC\\boincmgr.exe\" /a /s"

Because that registry key is "Microsoft__Windows__Run", they might fiddle with it (via msconfig or otherwise). It would be useful for somebody to check whether that 'run' key is successfully created by the BOINC installer, with a fresh install on a clean Windows 10 system.

The "Run Manager at login?" option that Jord cites actually controls a 'suppress autorun' flag at

[HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager]
"DisableAutoStart"=dword:00000001

When BOINC starts up (as stated, at every Windows login), the first thing it does is to check DisableAutoStart, and if set, it immediately stops again. I'd be surprised if Microsoft interfered with that mechanism in the private key.

Make sure that any programs (i.e. BOINC) that you want to auto start when OZS starts up are set in msconfig prior to upgrade. I made the mistake of blanking the BOINC boxes and I see no way to turn them back on. I may have to reinstall BOINC.

As far as I know, this is regulated through the registry, not through Msconfig/startup.

Before trying anything else, open BOINC Manager, and then depending on BOINC version:
7.4 and before, Tools->Options
7.6 and later, Options->Other options...

Now uncheck "Run Manager at login?" and OK if checked and then do that again to check this option.
Or just check "Run Manager at login?" if unchecked, then OK.

This will start BOINC at Windows login.

That box was already checked. If you run msconfig in Win 7 and press the startup tab, you can check/uncheck which programs start up at any particular time. If I'm upgrading/updating something and had to recycle and didn't want BOINC to start at the next recycle, I just uncheck the 2 boxes. You can do this and have the machine recycle at that time or not. If those 2 boxes are unchecked at the time of the upgrade, as in my case, then BOINC will not auto start, regardless of what is specified in the manager.

---

I don't buy computers, I build them!!

Make sure that any programs (i.e. BOINC) that you want to auto start when OZS starts up are set in msconfig prior to upgrade. I made the mistake of blanking the BOINC boxes and I see no way to turn them back on. I may have to reinstall BOINC.

As far as I know, this is regulated through the registry, not through Msconfig/startup.

Before trying anything else, open BOINC Manager, and then depending on BOINC version:
7.4 and before, Tools->Options
7.6 and later, Options->Other options...

Now uncheck "Run Manager at login?" and OK if checked and then do that again to check this option.
Or just check "Run Manager at login?" if unchecked, then OK.

This will start BOINC at Windows login.

That box was already checked. If you run msconfig in Win 7 and press the startup tab, you can check/uncheck which programs start up at any particular time. If I'm upgrading/updating something and had to recycle and didn't want BOINC to start at the next recycle, I just uncheck the 2 boxes. You can do this and have the machine recycle at that time or not. If those 2 boxes are unchecked at the time of the upgrade, as in my case, then BOINC will not auto start, regardless of what is specified in the manager.

In Task Manager there is a start up tab. You can right click items and select disable to have them not run on the next boot. I don't have the Windows 10 system in front of me right now, but adding new start up items can probably be done there as well.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Task Manager did not show BOINC in the Win 10 task manager startup tab even after starting BOINC. It did show under the processes tab, but you cannot alter it to show in startup tab. I uninstalled BOINC, recycled the machine, and installed BOINC 7.6.6 cleanly, and recycled the machine again without launching BOINC. When the OS came back up, BOINC was in the startup tab and started normally. So the conditions that I initially stated are essentially true. If you uncheck the 2 BOINC boxes via msconfig, for whatever reasons, prior to the upgrade, it will not be carried over to the task manager, therefore will not show in the startup tab.

---

I don't buy computers, I build them!!

If you have a home page other than M$S, edge will not go to that page. I had to include the home page button from the settings.

Don't forget this is considered a new program, you have to set it up using the "Settings", to include bringing your Favorites from IE into Edge. (Also, IE is still available and it will still run any add-in you want it to...only Edge will not run add-ins)

Win 10 will not run Java plug-ins, they have been blocked by M$S.

See above response

Cannot use what used to be the Windows Update, it has been de-activated by the OS and I haven’t figured how to get to it yet. We should have access to it if using pro or ultimate.

Use the search, type "update" and it will bring up a choice to Update Settings and going there you can check for updates regardless of Win10 class.
That search function works very well.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Task Manager did not show BOINC in the Win 10 task manager startup tab even after starting BOINC. It did show under the processes tab, but you cannot alter it to show in startup tab. I uninstalled BOINC, recycled the machine, and installed BOINC 7.6.6 cleanly, and recycled the machine again without launching BOINC. When the OS came back up, BOINC was in the startup tab and started normally. So the conditions that I initially stated are essentially true. If you uncheck the 2 BOINC boxes via msconfig, for whatever reasons, prior to the upgrade, it will not be carried over to the task manager, therefore will not show in the startup tab.

Shows up in both the Startup Tab and the Apps part of Processes Tab for me.

I do not think you can add directly to the Start Up Tab in Task Manager.

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

Task Manager did not show BOINC in the Win 10 task manager startup tab even after starting BOINC. It did show under the processes tab, but you cannot alter it to show in startup tab. I uninstalled BOINC, recycled the machine, and installed BOINC 7.6.6 cleanly, and recycled the machine again without launching BOINC. When the OS came back up, BOINC was in the startup tab and started normally. So the conditions that I initially stated are essentially true. If you uncheck the 2 BOINC boxes via msconfig, for whatever reasons, prior to the upgrade, it will not be carried over to the task manager, therefore will not show in the startup tab.

I had thought I saw a way to add items to the start up from there. Perhaps that was only in one of the beta release or one of the medications I am on. Likely the later.
If one wanted to prevent BOINC from processing while updating to Windows 10 it would probably be best to set BOINC activity to suspend in that case.

I'm still in the early stages of getting all the documents together to tell my coworkers "This is how you do task X now". Once I finish that I plan to load up non-Pro and see about getting the automagic updates disabled like in Pro.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The "Get Win 10" icon has disappeared from two of our computers. On one of them, (Farragut, my parents' HP Desktop machine), I then uninstalled and reinstalled KB3035583 in the hopes of getting the icon to return. That was yesterday afternoon. On Prometheus, I discovered the icon missing upon bootup this morning. I then launched Windows Update, and there staring back at me was the invitation to reserve my free copy of Win 10 Pro for my system. I will recheck that on Farragut, later.

In the meantime, as posted yesterday, I did download and burn the .iso file to DVD and now have a hard copy to reinstall 10 should anything horrible happen. I will also be grabbing the Win 10 Home .iso for the three Win 7 Home systems my family has.

I plan to upgrade to 10 in December, when there are enough patches and updates available to prove the thing is stable. I'll let others here be braver than I, and will continue reading the posts in this Thread. :-) Good luck in whatever each of you all decide to choose to do. :-)


TL

---

TimeLord04
Have TARDIS, will travel...
Come along K-9!
Join Calm Chaos

I just upgraded to Win 10 Last night7-29-15. All went smooth and no problems so far. There was no work units lost or any other Boinc/Seti problems. I keep my fingers crossed. Install took about 1 hour on SSD.

---

http://time.com/3977862/windows-10-solitaire/

Unbelievable.

Steve

Also, if you do a clean install, you will have to pay for the Windows 10 DVD Player app:

http://www.microsoft.com/en-us/windows/windows-10-specifications#featdep

•If you have Windows 7 Home Premium, Windows 7 Professional, Windows 7 Ultimate, Windows 8 Pro with Media Center, or Windows 8.1 Pro with Media Center and you install Windows 10, Windows Media Center will be removed. For a limited time (the “eligible period”), on systems upgraded to Windows 10 from one of these older versions of Windows (a “qualified system”), a DVD playback app (“windows DVD player”) will be installed. Note: the Windows DVD Player may not be installed immediately; it will be installed after the first successful Windows Update. The Windows DVD Player will be available for purchase from the Window Store for systems that (i) are qualified systems but the eligible period lapsed; (ii) are non-qualified systems; or (iii) were qualified systems but windows 10 was subsequently clean installed (in this case, Windows Update cannot detect that it was previously a qualified system).

Is there some reason why you would not forget about the M$ DVD player and instead use VLC Media Player to play DVDs? I have never had a problem with VLC playing a DVD movie.

^^^^^^ He's got you there :)

---

I came down with a bad case of i don't give a crap

http://time.com/3977862/windows-10-solitaire/

Unbelievable.

Steve

Also, if you do a clean install, you will have to pay for the Windows 10 DVD Player app:

http://www.microsoft.com/en-us/windows/windows-10-specifications#featdep

•If you have Windows 7 Home Premium, Windows 7 Professional, Windows 7 Ultimate, Windows 8 Pro with Media Center, or Windows 8.1 Pro with Media Center and you install Windows 10, Windows Media Center will be removed. For a limited time (the “eligible period”), on systems upgraded to Windows 10 from one of these older versions of Windows (a “qualified system”), a DVD playback app (“windows DVD player”) will be installed. Note: the Windows DVD Player may not be installed immediately; it will be installed after the first successful Windows Update. The Windows DVD Player will be available for purchase from the Window Store for systems that (i) are qualified systems but the eligible period lapsed; (ii) are non-qualified systems; or (iii) were qualified systems but windows 10 was subsequently clean installed (in this case, Windows Update cannot detect that it was previously a qualified system).

Is there some reason why you would not forget about the M$ DVD player and instead use VLC Media Player to play DVDs? I have never had a problem with VLC playing a DVD movie.

Yes. There is a reason. I actually don't mind Windows Media Player. It's there and it works.

Win 10 Pro (upgrade from Win 7 Pro) is now installed on my xw9400, after an all-day struggle involving several apparent dead-ends somewhere between the download and the notification that it was ready to install (which never was displayed). The Windows Update log actually showed about 5 failed installs (with 2 different error codes), even though I never got to the point of attempting the actual install.

I finally took the media tool route, which worked quite smoothly. However, the first thing I discovered is that Win 10 seems to only recognize 1 core on each of my Opteron 2389 quad-core processors. The Device Manager shows all 8 cores, but everywhere else in the system it only seems to recognize 2. There was nothing in the Win 10 compatibility checks on that machine that even hinted at such a limitation, so I don't know what the issue is. I'll try to dig into it tomorrow, I guess. (I'm too bleary-eyed tonight.) If there's no solution, it won't be long before the rollback to Win 7 commences.

The good news is that BOINC and Seti@home seem to be running just fine on the 2 available cores and 4 GPUs. Initially, Win 10 automatically installed the latest NVIDIA 353.62 drivers before I ever even had an opportunity to turn off the driver updates. However, after setting that option, I went back and installed the earlier 353.30 drivers. I'm hopeful that the "Never install driver software" will block Win 10 from making any further changes.

EDIT: Oh, and let me second Jord's comments about Express vs. Manual settings. If you value your privacy at all, don't choose Express. Those defaults are mind boggling to me! I think I turned off every one except the one to report errors.

A preliminary check on my xw9400 this morning is not encouraging. There was a notification waiting, saying that a new driver was available for a GTX 660 and would be installed automatically whenever the device was not in use. However, checking the BOINC Event Log, it appears that BOINC was restarted at 3:42 AM with all 4 GPUs now using driver 353.62. So, it appears Bernie may be right that the "Never install driver software from Windows Update" doesn't actually apply to Windows Update, only to newly installed devices.

I'm also guessing (with deeper digging to come later) that the BOINC restart was due to a full reboot to install other updates along with the driver update, since the update history showed several other Win 10 updates applied, along with two separate GTX 660 successful updates and one failed GTX 750Ti update (which is really confusing). All this despite the fact that I also had set the option to notify me first before any reboot to install updates.

That reboot, BOINC restart and driver change also apparently wreaked some havoc with running tasks. Each GPU had a single AP and single MB task running. The APs, which normally take about an hour to run, were all apparently hung up, with elapsed times in the 3-5 hour range, and remaining time steadily climbing. Suspending and resuming the project reset the elapsed times and the AP tasks apparently continued to normal completion. Now, checking the task list for the machine, I see that two MB tasks crapped out with "SETI@home error -6 Bad workunit header". The event log also shows a number of error messages right after the restart, such as:

7/31/2015 3:44:33 AM | SETI@home | task postponed 180.000000 sec: Cuda runtime, memory related failure, threadsafe temporary Exit
7/31/2015 3:45:04 AM | SETI@home | task postponed 180.000000 sec: Cuda device initialisation failed
7/31/2015 3:45:05 AM | SETI@home | task postponed 180.000000 sec: Cuda initialisation failure, temporary exit

These types of messages continued intermittently until about 3:50 AM (UTC -7).

So, all in all, not a pleasant start to the day. Hopefully, I'll have some time later on to dig a bit deeper.

I finally took the media tool route, which worked quite smoothly. However, the first thing I discovered is that Win 10 seems to only recognize 1 core on each of my Opteron 2389 quad-core processors. The Device Manager shows all 8 cores, but everywhere else in the system it only seems to recognize 2. There was nothing in the Win 10 compatibility checks on that machine that even hinted at such a limitation, so I don't know what the issue is. I'll try to dig into it tomorrow, I guess. (I'm too bleary-eyed tonight.) If there's no solution, it won't be long before the rollback to Win 7 commences.

I was looking intro this and found this here, that is a CPU SIMD requirement for Windows 8/8.1 but also for 10. As far as I have found your 2389 does support SSE2 and NX, but I haven't found anything about PAE yet, but then that's probably because yours is a 64bit processor, and this is a requirement for 32bit processors.
In the mean time, you could check if NX (could also be named XD) is enabled in the BIOS.

Also, previous versions of Windows had maximum amounts of physical processors one could install. Found this buried deep in a Microsoft forum:
Windows 10 supports maximum memory configurations that were formerly available only in the realm of servers. Windows 10 Home supports up to 128GB of RAM on the x64 platform. Windows 10 Pro and Enterprise both support up to 512GB on the x64 platform. The x86 versions of Windows 10 support a maximum of 4GB of RAM. Windows 10 supports a maximum of two physical CPUs, but the number of logical processors or cores varies based on the processor architecture. A maximum of 32 cores is supported in 32-bit versions of Windows 8, whereas up to 256 cores are supported in the 64-bit versions.

So at least that ain't it either.

It sounds to me like Windows didn't install with full multiprocessor detection.
Or it's a lack of updated CPU chipset drivers. Did you install those at the end of Windows install?

---

I finally took the media tool route, which worked quite smoothly. However, the first thing I discovered is that Win 10 seems to only recognize 1 core on each of my Opteron 2389 quad-core processors. The Device Manager shows all 8 cores, but everywhere else in the system it only seems to recognize 2. There was nothing in the Win 10 compatibility checks on that machine that even hinted at such a limitation, so I don't know what the issue is. I'll try to dig into it tomorrow, I guess. (I'm too bleary-eyed tonight.) If there's no solution, it won't be long before the rollback to Win 7 commences.

I was looking intro this and found this here, that is a CPU SIMD requirement for Windows 8/8.1 but also for 10. As far as I have found your 2389 does support SSE2 and NX, but I haven't found anything about PAE yet, but then that's probably because yours is a 64bit processor, and this is a requirement for 32bit processors.
In the mean time, you could check if NX (could also be named XD) is enabled in the BIOS.

Also, previous versions of Windows had maximum amounts of physical processors one could install. Found this buried deep in a Microsoft forum:
Windows 10 supports maximum memory configurations that were formerly available only in the realm of servers. Windows 10 Home supports up to 128GB of RAM on the x64 platform. Windows 10 Pro and Enterprise both support up to 512GB on the x64 platform. The x86 versions of Windows 10 support a maximum of 4GB of RAM. Windows 10 supports a maximum of two physical CPUs, but the number of logical processors or cores varies based on the processor architecture. A maximum of 32 cores is supported in 32-bit versions of Windows 8, whereas up to 256 cores are supported in the 64-bit versions.

So at least that ain't it either.

It sounds to me like Windows didn't install with full multiprocessor detection.
Or it's a lack of updated CPU chipset drivers. Did you install those at the end of Windows install?

Thanks for that digging, and those tips. I also ran across something that indicated that Win 8.1 would not support some of the older AMD processors (though Win 8 did), but that was only in the 64-bit OS. However, I'm only running 32-bit, and Win 10 did install, so I guess the support is there. It just seems to be a bit crippled.

I just checked the BIOS and found no setting that would enable/disable NX, so if the 2389 supports it, I would hope that it's on by default. Interestingly, when I was making a list of instruction sets on all my PCs a couple years ago, prior to running a Lunatics installer for the first time, I came up with all of those Wikipedia-listed items (MMX, SSE, SSE2, SSE3, SSE4a, Enhanced 3DNow!, NX bit, AMD64, AMD-V) except the NX bit. Perhaps that's because it's just a bit and not a full-blown instruction set. I'll have to see if I can dig into that further.

I did try using Device Manager (which shows all 8 cores as working) to see if I could get it to update the driver, but it says the latest driver is installed. Again, that's something that perhaps I can dig into further. This could be a long, tedious process......or, then again, I could just revert to Win 7 (or even go back further, to two weeks ago, when that was a perfectly happy XP box). ;^)

EDIT: Oh, and I did briefly have Win 7 Home Premium on that machine for a few days when I first replaced XP, where I discovered that single-processor limitation for the Home editions. It did recognize all four cores on that one processor, though. But then I switched to Win 7 Pro (no problems there) and now Win 10 Pro. All of them 32-bit editions.

Interestingly, when I was making a list of instruction sets on all my PCs a couple years ago, prior to running a Lunatics installer for the first time, I came up with all of those Wikipedia-listed items (MMX, SSE, SSE2, SSE3, SSE4a, Enhanced 3DNow!, NX bit, AMD64, AMD-V) except the NX bit. Perhaps that's because it's just a bit and not a full-blown instruction set. I'll have to see if I can dig into that further.

The link I gave to Wikipedia says Opteron 2300-series "Barcelona" (65 nm)

All models support: MMX, SSE, SSE2, SSE3, SSE4a, Enhanced 3DNow!, NX bit, AMD64, AMD-V (SVM & Rapid Virtualization Indexing)
I did see the CPU World link that doesn't show NX. But as you said, if you didn't have it, you couldn't have installed Windows 10, as it looks for these in the CPU prior to installation.

I did try using Device Manager (which shows all 8 cores as working) to see if I could get it to update the driver, but it says the latest driver is installed.

Well, if you know the motherboard that the CPUs live on, I can do another round of look-see. Two see more than one. Or something alike that. ;-)

---

Okay, a quick one you should be able to check, whether Windows installed two single processors, or two multiprocessors.

See https://msdn.microsoft.com/en-us/library/windows/hardware/ff547188%28v=vs.85%29.aspx, it's for Vista and above. Just check with Event Viewer in the System Log for Event ID 6009 (you can order the Event ID column by number) and open it. What does the line say?

If not something with Multiprocessor Free at the end, you didn't install Windows with multiprocessor support.

---

The link I gave to Wikipedia says Opteron 2300-series "Barcelona" (65 nm)

Actually, if you scroll further down that page, you'll find Opteron 2300-series "Shanghai" (45 nm)

Well, if you know the motherboard that the CPUs live on, I can do another round of look-see. Two see more than one. Or something alike that. ;-)

The motherboard model number is SP#442030-001. That "-001" is important because, technically, that first version of the motherboard doesn't support the 23xx processors. I found that out the hard way when I first tried to upgrade from dual-core to quad-core shortly after I acquired the machine. Only the later "-003" and "-004" models came quad-core ready. However, a bit of solder on a jumper and a BIOS update with Flashrom (to "write enable" the Boot Block), made everything right with the world....at least until now!

Okay, a quick one you should be able to check, whether Windows installed two single processors, or two multiprocessors.

See https://msdn.microsoft.com/en-us/library/windows/hardware/ff547188%28v=vs.85%29.aspx, it's for Vista and above. Just check with Event Viewer in the System Log for Event ID 6009 (you can order the Event ID column by number) and open it. What does the line say?

If not something with Multiprocessor Free at the end, you didn't install Windows with multiprocessor support.

Yeah, several ID 6009 events in the log, one for each boot it looks like. All read:
Microsoft(R) Windows(R) 10.00. 10240 Multiprocessor Free

I actually think that if it was only seeing a single processor, I'd at least see all 4 cores (as I did with Win 7 Home) and that Device Manager wouldn't show all 8. It's really that Device Manager display that has me quite puzzled, as if one part of the OS knows there are 8 cores there, while the rest of it doesn't, or is somehow blocking access.