[Update] Windows 10 Discussion - Page 43

BenMcr · 05-06-2015, 14:00

Quote:

Originally Posted by heero_yuy

I still don't understand why they changed it from something that worked perfectly well (F8) and everybody knew how to use and try to hide it so you need to re-activate it BEFORE you know you need to use it. Perverse logic at best.

Reading some of the information, it's down to the change to UEFI and SSDs

http://www.techrepublic.com/blog/win...nto-safe-mode/

Quote:

I suppose that if you are running Windows 8 on a SSD-based UEFI system where as Microsoft says the F8 window is less than 200 milliseconds, you won't be able to use F8 to get to Safe Mode

F8 only works if you catch the right point in the boot process. With newer machines it's all much quicker than it used to be i.e potentially down from a many seconds window to 1 second or less. So it's less likely you can hit the kit at the right point consistently to trigger the menu.

qasdfdsaq · 05-06-2015, 14:51

Quote:

Originally Posted by BenMcr

There is an alternative:

http://windows.microsoft.com/en-gb/w...ings-safe-mode

Quote:

If you can't start (boot) your PC, follow these instructions to get to the Windows Recovery Environment. You'll need to connect a keyboard to complete the steps.

That's just crazy. How on earth would you expect any non-expert user to ever manage that?!?!

Quote:

If you don’t have installation media, use the power button to restart your computer three times. This will start the Windows Recovery Environment.

Lol.

---------- Post added at 14:48 ---------- Previous post was at 14:46 ----------

Quote:

Originally Posted by heero_yuy

I still don't understand why they changed it from something that worked perfectly well (F8) and everybody knew how to use and try to hide it so you need to re-activate it BEFORE you know you need to use it. Perverse logic at best.

To be fair the whole idea is that YOU never NEED to use it.

Windows recovery is designed to be either fully automated, or not intended to be something an end user is able to do one their own anyway.

---------- Post added at 14:51 ---------- Previous post was at 14:48 ----------

Quote:

Originally Posted by BenMcr

Reading some of the information, it's down to the change to UEFI and SSDs

http://www.techrepublic.com/blog/win...nto-safe-mode/

F8 only works if you catch the right point in the boot process. With newer machines it's all much quicker than it used to be i.e potentially down from a many seconds window to 1 second or less. So it's less likely you can hit the kit at the right point consistently to trigger the menu.

That just sounds like a load of rubbish. Not least because UEFI + SSD systems are still a minority now in 2015, let alone when Windows 8 was released.

But on top of that, the "F8 window" has never been long or consistent on any system in the past and it's never been used as an excuse before... not to mention on any multi-OS systems it's at least 30 seconds by default. Sounds more like they're retrospectively making up a fake explanation to cover up yet another dumb "tablet optimized" decision they don't want to admit.

Because face it, removing a keyboard function and replacing it with a touchscreen F8 interface stinks of the whole turning-every-PC-into-a-tablet design philosophy of Windows 8. If it was really anything to do with the timing window being too short they'd have just made activated by a hold-down-the-button-continuously feature like all the other startup/safe mode/bypass modes are.

Dave42 · 05-06-2015, 23:53

windows 10 build 10130 ISO's now available

http://windows.microsoft.com/en-us/windows/preview-iso

SnoopZ · 06-06-2015, 12:38

I want a new build, too many bugs in 10130 here.

Sirius · 06-06-2015, 12:50

Quote:

Originally Posted by SnoopZ

I want a new build, too many bugs in 10130 here.

I can see me not upgrading until well after the release date. All i see at the moment is bug after bug after bug being reported. It just does not give me confidence to trust them at release date.

dave6x · 06-06-2015, 13:00

Quote:

Originally Posted by Sirius

I can see me not upgrading until well after the release date. All i see at the moment is bug after bug after bug being reported. It just does not give me confidence to trust them at release date.

Agreed. I've always had a rule in the past that I won't touch a MS Windows OS until at least the first Service Pack or equivalent!

johnhook · 06-06-2015, 13:17

I am upgrading but keeping my windows 8.1 intact as well. Sometimes a build is released focusing on certain aspects the last couple I think GUI the last few builds the other bugs a consequence of the other

On top of that to be quite honest I think the free upgraders are basically playing OEM and doing the RTM compatibility tests for them I am not concerned about the lack of time between now and then. We could be 6 weeks or more away from an RC build

Dave42 · 06-06-2015, 15:22

Quote:

Originally Posted by Sirius

I can see me not upgrading until well after the release date. All i see at the moment is bug after bug after bug being reported. It just does not give me confidence to trust them at release date.

Paul Thurrott and Mary Jo Foley been saying they be patches on release day too that's what they working on now mainly is bug fixes

Sirius · 06-06-2015, 21:26

Quote:

Originally Posted by Dave42

Paul Thurrott and Mary Jo Foley been saying they be patches on release day too that's what they working on now mainly is bug fixes

Patches on release day

I will wait till they have a fully working product that does not need patches on release day.

qasdfdsaq · 07-06-2015, 01:41

Quote:

Originally Posted by Sirius

I will wait till they have a fully working product that does not need patches on release day.

Windows as a service means that Windows 10 will constantly be getting patches by design, forever.

Dave42 · 07-06-2015, 01:54

Quote:

Originally Posted by qasdfdsaq

Windows as a service means that Windows 10 will constantly be getting patches by design, forever.

exactly and the fixes will come quicker which is a good thing

MalteseFalcon · 07-06-2015, 08:00

Nobody ever releases something that works straight out of the box though, look at all the computer games released every year. You can pretty much guarantee putting a game in on launch day, and there will be a 2 GB download straight away for that game.

alferret · 07-06-2015, 09:14

Had my notification earlier in the week. Got it on my main PC but not on my media centre

both running Win7 x64.
Still undecidied if I am going to migrate to 10 tho. But I do like the sound of the increase in games framerate.

Sirius · 07-06-2015, 11:05

Quote:

Originally Posted by qasdfdsaq

Windows as a service means that Windows 10 will constantly be getting patches by design, forever.

As with most software, but at the moment the existing bugs if carried over to release date will make it a no go on release date for me.

---------- Post added at 11:05 ---------- Previous post was at 11:04 ----------

Quote:

Originally Posted by Dave42

exactly and the fixes will come quicker which is a good thing

Well lets see if the bugs they have now are fixed for release date, some of them have been in windows 10 at least 2 of there updates over the last month.

For instance the start menu keeps stopping and needs a reboot to fix, a start menu they are hyping all the time.

Before you say its my machine it does it on 2 laptops and on my test machine.

Dave42 · 07-06-2015, 11:12

Quote:

Originally Posted by Sirius

As with most software, but at the moment the existing bugs if carried over to release date will make it a no go on release date for me.

---------- Post added at 11:05 ---------- Previous post was at 11:04 ----------

Well lets see if the bugs they have now are fixed for release date, some of them have been in windows 10 at least 2 of there updates over the last month.

For instance the start menu keeps stopping and needs a reboot to fix, a start menu they are hyping all the time.

Before you say its my machine it does it on 2 laptops and on my test machine.

well that's what they are mainly working on now bug fixes so should be fixes by 29th of July