craigb

Moshkito

craigb
...
Going from Office 2007 to Office 2016 and Visual Studio 2005 to VS 2015 will probably require watching a bunch of tutorials (already downloaded) as well!  
 
...

Make sure you read the fine print on the Office 2016. Anything that you "create" in it, basically is owned by Microsoft, since you are using a "free product" and they provide the ability for you to be more effective and duah and dah and deh ... with it.

1.  Anything I create using Office 2016 belongs to ME, not Microsoft.
2.  It certainly wasn't free.
 
Not really sure what you meant to say either...

Exactly....

I thought I'd read that superfetch doesn't touch SSDs. Am I mis-remembering that?

bitflipper
I thought I'd read that superfetch doesn't touch SSDs. Am I mis-remembering that?

Not sure, but it sure doesn't need to!
 
Also remember: Avoid defragging an SSD, it's not necessary and can actually (very slightly) shorten the life of the drive. 

craigb

bitflipper
I thought I'd read that superfetch doesn't touch SSDs. Am I mis-remembering that?

Not sure, but it sure doesn't need to!
 
Also remember: Avoid defragging an SSD, it's not necessary and can actually (very slightly) shorten the life of the drive. 

I was thinking about that last night. Since there is not a mechanical move of a head, there should only be a slight time difference for fragmented SSD's and only have any impact when LARGE files are scattered. Taken at face value of a simple move of a file part during defrag, it should not cause undue read or write (given 1 read/1write per move). But since SSD's lifecycles are dependent on read and write at each particular memory address it could be much better to have fragmented files. In theory, file fragments could be scattered over the whole SSD memory address instead of reading from the same block repeatedly - like OS files. Kinda like preventing burn-in on the old CRT monitors.
 
Just a thought.

There you go again, thinking! 

bitflipper
I thought I'd read that superfetch doesn't touch SSDs. Am I mis-remembering that?

I believe it used to get automatically turned off if you had an SSD.
 
But regardless if it is touching anything or not, quite a few of us had an issue with W10 memory and that particular problem went away when the service was disabled.

craigb
There you go again, thinking! 

Dang it. I have to remember to call my sponsor when I feel a thought coming on! Oops, that would be thinking about my sponsor though. Argh. :)

By the way, am I the only one calling this OS "Windows Two?" 

Ok, so no one liked that joke.  Fine.  I'll be helpful anyway!
 
My desktop install of Windows 10 (a clean install of Windows 8.1 then an immediate upgrade to 10) went smooth.  My old laptop (a.k.a. the Brick) not so much.  Here's what I've learned:
 
If you have issues with Windows 10 getting stuck (usually at 99% after hours of installing), make sure you have an Anti-Virus program that's both compatible with Windows 10 and turned off for the install.  Mine had some Symantec offering that, even with everything off and disabled, STILL was quarantining install files...   It's now removed from the system.  Next, change the Windows Update service to type "Manual" (in Control Panel, Services) and stop it (using Task Manager, Processes).  Reboot and try again.  An alternate way (to the reboot method) is to kill the process SetupHost.exe.  After a bit, the Windows Upgrade Assistant will put up a window saying something went wrong with a button to try again.
 
That's where I've gotten to so far... It's trying again as I type this.

And that worked!