Ms you are going BONKERS -- Can't create recovery drive !!!!!!!

I have also posted here on my experience of re-doing my comp from 10240 to 10240. Did the ESD to ISO 'trick' as well.

@Frank1 - yes, the data disk is not what is being talked about here.
Try this one for an explanation
What are the system recovery options in Windows? - Windows Help

Mystere said:

I grabbed the ESD from the upgrade and converted it to ISO

Thanks Mr E, that's what I thought - just a sanity check on my part.

Bill
.

Mystere said:

No, the only way to get the free upgrade is to upgrade. After you have upgraded, you can install clean if there is a problem. I would suggest that you do so (I did, just a few days ago) It will automatically activate even though it's a clean install, *IF* you have already done an upgrade.

Hi there
That's an answer to the WRONG question.

My question is this -- after you've done your installs and got all your programs running again just how you want them --whether Clean install or otherwise it's still possible to BREAK something so the system simply won't boot.

Now often before you could boot your recovery disk and simply try REPAIR WINDOWS - which unless you had a major hose up would normally work.

I KNOW you can do a full blown Image restore but IMO that's overkill for typical users who probably wouldn't know how to take one in any case --especially if they had to fiddle around to create a type of WINPE disk (Macrium Free V6) to get a backup program in the first place.

Surely however Ms wants to distribute the OS -- Integrity of the OS and recovery of a broken OS to a working state again should IMO be a VERY important part of the whole setup -- not just left out as an afterthought.

(Of course sensible users will take backups - but these days Ms needs to make the OS IDIOT PROOF as far as possible - and removing a feature that existed (and was used) in previous OS'es seems a bit Bovine to say the least.

If they bring it back in RTM --well we haven't had any time to test it yet -- but I suppose Ms likes to "Test in Production" !!.

Cheers
jimbo

I think "sensible users" will not use pre-release software for any critical operations. As such, 10240 is just a toy - and if it is broken already, you can get another one FOC! :)

Fafhrd said:

I think "sensible users" will not use pre-release software for any critical operations. As such, 10240 is just a toy - and if it is broken already, you can get another one FOC! :)

Hi there

Maybe not quite true as well -- next week or even within a day or two W10 will be rolled out FOR REAL to maybe 100,000's / probably many many more of users who have signed up for the free upgrade --things are IMO 100% BOUND TO GO WRONG -- wait for howls of anguish in the next few days.

ISO's I'm sure will be released but until then I can envisage a situation where loads of users will be stuck with BROKEN computers --especially as they probably will have wiped those silly Restore partitions on W7 / W8 when OEM's stopped dishing out physical recovery media.

Cheers
jimbo

The only payment direct to a Microsoft Sales Agency was the £14.99 for the Windows 8 upgrade, on my Windows 7 Home Compaq Presario CQ57, still running well with 8.1 Pro, and I still have my Hewlett Packard base.wim stored in my recovery Partition (and backed up) The nearest this laptop has come to Windows 10 is a VMware VM of n early technical preview, long wiped. Any other Microsoft software I use are legitimate trials, e.g. 8.1 Enterprise, ancient Office software with educational licences from when I worked in Education or ancient promotional software from when I worked in the computer business. I'm too long in the tooth to get hoodwinked by beta software ruining my system.

I expect you are right when you say " howls of anguish in the next few days" though, Jimbo. Good job we (i.e. XForum regulars) are here to help them sort out their messes when they do!

I wonder why it is not working. The recovery media creator seems to put a 3GB+ file (with one of the obscure GUID type filename) in the C: drive System Volume Information folder. It seems to be a VSS (Volume Shadow Copy Service file).

Is the C: drive available, too fragmented or too full to hold the file perhaps, or is the System Volume Information folder otherwise inaccessible?