New
#11
I know that a lot of people's opinion of what life cycle of the device means. We have to wait an see what Microsoft Legal defines life cycle of the device and windows as a service is. I was just hoping for the release of that information a lot sooner then Windows 10 RTM date that why I asked. Windows 10 RTM is suppose to be released in June. So, they should have both defined way before then.
I`m sure they will announce something before Windows 10 is released.
Windows 10 will not be released to the public in June.
Anything released to the public in June will still be just a preview.
Short for release to manufacturing, the version of a software product that is given to manufacturers to bundle into future versions of their hardware products. RTM versions are typically released to manufacturers before they are released to the general public so that the manufacturers can work out any bugs the software may encounter with hardware devices. The release of an RTM version does not necessarily mean that the creators have worked out all the problems with the software; there still may be more versions of the product before it is released to the general public.
As stated earlier, all this is discussed in Tenforums.
https://www.tenforums.com/
Legal terms :/
It's well known Microsoft has extended services and probably more on the horizon that are going to be subscription based,
It's not mandatory to use them although some basic apps will not be totally removable but won't be activated unless you use a service.
The os in general as in subscription for updates to the 10 os would be the only real question mark
Or re-installing 10 on the same device if components change like hdd's after a year
I personally had 10 brick/ paperweight one hdd already because a update build reset fast start to On.
I'd probably never try a windows update from 8.1 to 10 but there wouldn't be any love loss if 8.1 got killed along with anther cheap hdd which is sitting waiting on the next build to be released to see what it's like,
If it gets bricked I'll completely pass on 10 final no matter what 2 bricked hdd's is enough to tell me it's not worth the irritation.
I already do not use 8.1 it's not even installed.
Off topic
Thrashzone,
Sometimes gparted can fix bricked drives.
I found out the reason for the brick drive, it is because most systems have two or more partition already done by the user or the oem. What happens windows 10 doesn't see the end of the partition correctly. So, that causes it not to boot.
Also, if gparted fails, you might want to try to installing pclinuxos. Install as a full replacement to what ever operating system was on the drive. (Remember to remove any other drives with operating systems installed before you do that). Let it install with all its defaults (One exception make sure you choose to replace your windows or other operating systems with pclinuxos on the bad disk) , after installed boot up to a couple of times. Now using a Mini wizard partition boot disk, you should be able to delete all those partitions and create new ntfs partitions like you had before or want now. Then you can install windows 10 or 8 or 7 or keep it as spare ntfs drive. I found out pclinuxos has a very unusual way of installing and can fix boot issues and it also won't let you create or adjust partitions.
One tip, you may need to run in the command prompt from the windows installation disk or repair disk.
bootrec /fixboot
bootrec /fixmbr
Most you posted was tried and failed,
I need a newer mobo capable of sending the wake command so the drive is really in a deep sleep put there by 10tp.
Sorry it didn't work. I read that method did work for some having the same issue.
The only other thing I can think of is putting the drive in an USB 2.0 External hard drive enclosure,
Now, insert the mini wizard partition boot cd. Shut down the computer. Boot up the mini-partiton wizard boot disk. After the disk info shows, plug in your External drive to a usb 2.0 slot. Then wait a moment, then choose reload disk from mini-partition wizard menu. If accessible delete all the partitions. Then write a new ntfs partitions.
Thanks that was actually the first thing I tried :)
Mobo not able to send wake command nothing reads the disk which isn't a big deal as I said but something that happened to me personally on a 5-6 y.o machine and hdd
The solution was posted but does require a newer model machine or hardware to accomplish the task.
My guess would be that the life-cycle of a device phrase that MS apparently used was intended to limit the installation of the free version of Win10 to one "device" -- be it SDD or HDD, in a manner such that the activation hash sequence incorporated the serial number of the "device".
Thus, if a couple of years later, you decided you wanted to "upgrade" to a newer/larger SSD/HDD, regardless of how you did the migration from the old drive to the new, when you connected the new drive, soon thereafter, you would get some kind of dreaded "deactivation" message -- indicating that you would have to go online and PURCHASE a Win10 version to continue using that device.
This way, MS would get all those "old" Win7 machines to upgrade to Win10 for free, and when their hard drives started to die, would then make a fortune charging all those people "upgrade fees" to allow them to keep using Win10 but on a newer drive.
But ... as I said ... it's only a guess.