yup worked. Online though. Phone people really not interested. Weird thing is I can't now find what the actual win10 key is as it clearly changed it from the win7 key. A bit worried about reinstalls in the future!
Printable View
yup worked. Online though. Phone people really not interested. Weird thing is I can't now find what the actual win10 key is as it clearly changed it from the win7 key. A bit worried about reinstalls in the future!
Reinstalls won’t be a problem as the hardware id of your system has probably been logged and therefore a reinstall will activate. In my house we have quite a few laptops, all were upgraded from W7 and I have had to do a clean install of W10 and it’s always activated with no issues.Quote:
Originally Posted by ik9000
Yep, if you try and use a key finding program to grab your Windows key from the registry etc you get a generic key that is the same on everyone's PC. It doesn't work like that, your hardware serial numbers, MAC address etc are now hashed and stored at Microsoft, so as long as you don't change too many devices (and certainly not the motherboard) it will just re-install fine.Quote:
Originally Posted by ik9000
If you do change the motherboard, you will need to re-insert your Windows 7 key.
Ah that makes sense. I found a script that did find the key that apparently is the thing windows10 is referring to and unlike those found by so many "solutions" offered online the last 5 digits match the ones visible in the system info and slmgr output which is more reasurring, but either way it does sound like it now relies on the digital licence. It's saying it's a full retail licence (which it should be) so presumably it will let me transfer it to a new machine in future.
With a retail licence you can usually transfer the SSD to the new machine and it will work just fine. Windows seems much better at coping with hardware changes than it used to.Quote:
Originally Posted by ik9000
If you just re-install onto the existing machine, you just hit "skip" on the bit where it asks for the licence key and then once installed it will just sort itself out.
Yes, the awful HAL that older Windows versions was a proper barrier to this...Quote:
Originally Posted by DanceswithUnix
Need to update to the last version of Windows 10?Quote:
Originally Posted by Teece
I just upgraded a pc to win10. I fresh installed it on a new SSD and used my win7 pro product key, which worked to give me win10 pro.
I'm doing okay so far, I'm using a local account though so I think most of microsoft's pushy stuff can't come onto me like normal. I think without pro I'd struggle a lot.
Err, no - I was just saying that the Hardware Abstraction Layer in older versions of Windows (7, at least) would not tolerate you just plugging an HD with an existing install on it into a new machine.Quote:
Originally Posted by JosephRiggins
I've got a local account on plain old regular W10, never signed in either and don't get any MS stuff pushed my way.Quote:
Originally Posted by DemonAndrew
The first Windows 10 feature update since switching - version 2004 - has arrived (it wasn't showing up until now despite knowing it was out) and it decided to immediately complain that there was an issue it needs to fix. I know I could just tell it to delay it for longer, but I'm curious to see how it handles it this first time.
Upon telling it to fix the issues it quickly launched a window saying that it can't update because of it being unable - for some reason - to update the system's reserved partition. I'm going to give it a reboot in case that will get it going, but it's certainly an odd error for it to pop up.
EDIT: Nope, that didn't change anything. And neither did reverting the Environmental Variables back to normal (I had set the Temp folders to a HDD in the hope that it means as much longevity for the SSD as possible).
Still the same error that it can't update the System Reserved Partition. Time to go hunting for the solution then (haven't actually searched yet).
EDIT 2: Looks like it may be a lack of space issue (and it's it's also MBR rather than GPT like I thought it was). Unfortunately after following the instructions it fails on step 10 with it denying access to the System Volume Information folder of Y.
Like this result on the Microsoft forums suggests, there's nothing on that page to suggest what to do in that case, but the responses are suggesting to use partition managing software to decrease the start of the C: partition at the front and increase the System Reserved/Y: Partition at the back respectively by 500MB.
EDIT 3: Done the resize and extended using the Partition Wizard software suggested in the above link, as it seems that that it frees up some space AFTER the C: partition when you resize it like that (as I would have expected), but it then just moves the C: partition forward to be able to extend the System Reserved Partition into the extra space before the C: partition - EaseUS' Partition Master isn't that smart.
Update process is going fine, so it confirms it was indeed a space issue. Although to avoid potential further issues, I actually increased the space by 1GB rather than 500MB.
EDIT 4: And I spoke too soon. Error 0xc1900223. Will do another search.
EDIT 5: A search and quick skim of the results seems to suggest that the above means a problem downloading the update. Now however, it's decided I'm up -to-date again, so I'll have to see if it will update as it should the next time it decides that 2004 is there.
But temporary files is the sort of thing an SSD excels at?!? I have to wonder just what you are doing that you think you will wear the drive in any meaningful way.Quote:
Originally Posted by Output
According to the program Crucial supplied for my cheap MX500 1TB SATA drive, after 2 years I have used 10% of it's lifetime erase/write cycles. I would guess a lot of that activity is from game patching. Either way, my drive seems to think it has another 18 years of flash writes left at the current rate, that's with no attempts to be gentle on it at all.
Good luck with the Windows update. ISTR not long after doing the Windows 10 upgrade from 7 wiping the drive and doing a fresh install. I can't remember what prompted that, I tend to be a bit trigger happy with Windows re-installs, but it has been fine updating since.
Quick update, Ive now done tthe full migration to Win10, and so far so good.
Took me a while to sort out a few niggles like no Photo Preview, but thats OK now. Also had a query with my NAS which was appearing only in Twonky, but I figured that out too, and can now fully access all the files in Windows Explorer, simply by accessing the NAS from a different part of the left hand tree !! A bit weird....
Now I have to remove my old 250GB SSD, format it and stick it in my wifes laptop and put Win 10 on that too.
Pricey game this OS upgrading lark :(
I think my decision was mostly based on a Windows 7/10 site/forum post somewhere, where it basically suggested that. The way I understood things was basically that SSDs are better for the faster launching and running or programmes in general, but could easily get writes used up - especially if you take into account the way some web browsers apparently write updates way too frequently (although then again, that's probably not hitting the temp files anyway and still be hitting the SSD), but it seemed like a logical decision to have installers and other temporary files using an HDD to lessen writes.Quote:
Originally Posted by DanceswithUnix
I guess overall it was paranoia due to some strories over the years of SSDs suddenly dying. Realistically, my usage probably isn't going to have a meaningful impact and it might not have changed the actual behaviour of programmes in the way I was thinking with the move anyway.
Mine's a Sandisk Ultra 3D 2TB. The main intention of getting it really was faster programme and game launches (and faster OS booting if possible) but with plenty of space to actually hold plenty of Steam games (and any growing Windows installation in general) on it.Quote:
Originally Posted by DanceswithUnix
I guess I'm just still wary of a sudden failure and to be proven right that HDDs are more reliable or something. But maybe it was only those OCZ SSDs a number of years ago that were really a problem at the time (not that I ever had one, this is my first SSD).
If I recall correctly, I only moved over to my SSD in January of February 2019 though (after buying it in Black Friday sales a couple of months earlier), so it's hopefully got a long future.
Thank You. I realise a clean install is a possibility that may have to happen down the line for best effect (just like it was for earlier Windows Operating Systems like 7 and XP), but with all the settings already in place I'm hoping to avoid it for as long as possible if it does have to happen.Quote:
Originally Posted by DanceswithUnix
At the very least, I'd hope it to be at least a year away as I'd rather not have to go through everything from scratch to make sure it's just how I want it to be - especially as I've probably forgotten what various tweaks I may have made over the years were (and why) that while they may have transferred over from Win7, obviously wouldn't already be set on a Win10 install.
Although one tweak I know that didn't transfer across and that I intend to look into re-applying at some point is the removal of the the arrows on shortcuts on the Desktop and hte like. It just always looked so much neater - that's just a cosmetic change really though, so more of a "would like to have" rather than "need to have".
TL;DR: I'm still paranoid about SSD longevity I guess.
Nice going. :)Quote:
Originally Posted by g8ina
As Spreadie sort of predicted, I think I'll have to say it: Windows 10 isn't as bad as I thought it would be.
However I would like to qualify that, in that it likely still would have been as bad as I thought if it wasn't for the various changes they have made to Win10 since its original launch, along with ShutUp10 existing. If neither of those were in place, I still think it would have been as bad as I thought, so I think waiting so long was still the right decision.
lol, yeah I guessed. Random hardware failures suck, so you want backups for that. For wear rate, which is a predictable failure, then unless you are doing something massively write heavy just don't worry about it.Quote:
Originally Posted by Output
Really, write endurance hasn't been a problem for about half a decade. I wouldn't worry about it, and I actually have one of those infamous OCZ drives though I don't put files I care about on that laptop :D
True, making backups is always a wise decision. And no, as far as I am aware I'm not doing anything actually write-heavy, but with how some programmes are written, it's not outside the realm of possibility that something will be writing a lot more than you'd think it might, without even realising it.Quote:
Originally Posted by DanceswithUnix
Oddly enough, I was one of the lucky ones with a Seagate 1.5TB HDD despite how many of those were reported to fail. It's been solid the whole time in the years I've had it. Things are gradually moving from it to another HDD though, as I'd rather free up the slot for a bigger 3.5" drive at some point (despite there being no real rush as I have plenty of free bays).Quote:
Originally Posted by DanceswithUnix