PDA

View Full Version : Latest Windows Upgrade offer


Robin Bignall
December 29th 12, 02:22 AM
This is the latest Win 8 upgrade offer in the UK. At 24.99 UKP it's a
good price.
http://www.microsoftstore.com/store/msuk/en_GB/pdp/productID.257641900/pgm.81522200

To get to it I clicked on the $39.99 latest offer in the US

http://windows.microsoft.com/en-US/windows/buy

and then selected "Or get the upgrade on DVD from the Microsoft Store".

Notice it transferred to the UK store but the only option is download
and install. No DVD, and I can't see an option to download and save for
installation later.
My hardware won't do an upgrade install. I need the DVD to do a clean
install if and when I want to get around to it. Bummer!
--
Robin Bignall
Herts, England

Paul
December 29th 12, 02:34 AM
Robin Bignall wrote:
> This is the latest Win 8 upgrade offer in the UK. At 24.99 UKP it's a
> good price.
> http://www.microsoftstore.com/store/msuk/en_GB/pdp/productID.257641900/pgm.81522200
>
> To get to it I clicked on the $39.99 latest offer in the US
>
> http://windows.microsoft.com/en-US/windows/buy
>
> and then selected "Or get the upgrade on DVD from the Microsoft Store".
>
> Notice it transferred to the UK store but the only option is download
> and install. No DVD, and I can't see an option to download and save for
> installation later.
> My hardware won't do an upgrade install. I need the DVD to do a clean
> install if and when I want to get around to it. Bummer!

When I did the electronic purchase for $39.99, the files downloaded into
C:\ESD on the purchasing machine (my laptop).

Initially I was concerned about losing the files. I didn't know
where they were, looked in %temp% and so on.

Anyway, if you run the tool again, it presents the same options
for post-usage of the C:\ESD folder. It will make an ISO9660 file
for you. It can also load a USB flash key with the files. I used the
USB key option, but also had it prepare the ISO9660 file for storage
on this machine.

My desktop machine is where I installed the resulting 64 bit download.
The order machine runs a 64 bit OS, so the purchase would be
for 64 bit download as well. Then, I transferred over to the desktop
machine, to do the actual install (previously, the desktop used
a 32 bit OS). And, as a precaution, I also ran the upgrade tool
on this machine, to make sure there were no outstanding issues
(no complaints about NX/XD support).

So while the download is scary, and initially you'd be worried about
losing the contents of C:\ESD, in fact the tool is re-entrant, and
you can go back and prepare other media formats. Like DVD (using
build-in windows burner), ISO9660, or USB key (prepared the same
way as the previous "Windows 7, microsoftstore" tool would do it).

Paul

John Doe
December 29th 12, 03:15 AM
Robin Bignall <docrobin ntlworld.com> wrote:

> This is the latest Win 8 upgrade offer

> the only option is download and install. No DVD, and I can't
> see an option to download and save for installation later. My
> hardware won't do an upgrade install. I need the DVD to do a
> clean install if and when I want to get around to it. Bummer!

That problem is not uncommon. Don't ask me why, but you have to
download from a version of Windows with a built-in CD burner, post
Windows XP, like Vista or 7 or 8, if you want a saved copy of the
ISO. To get a copy of the 64-bit version, all you have to do is
use a 64-bit version of Windows 7 to do the download, using
(Windows8-Setup.exe) I think.

BillW50
December 29th 12, 09:16 AM
In ,
Paul typed:
> Robin Bignall wrote:
>> This is the latest Win 8 upgrade offer in the UK. At 24.99 UKP it's
>> a good price.
>> http://www.microsoftstore.com/store/msuk/en_GB/pdp/productID.257641900/pgm.81522200
>>
>> To get to it I clicked on the $39.99 latest offer in the US
>>
>> http://windows.microsoft.com/en-US/windows/buy
>>
>> and then selected "Or get the upgrade on DVD from the Microsoft
>> Store". Notice it transferred to the UK store but the only option is
>> download
>> and install. No DVD, and I can't see an option to download and save
>> for installation later.
>> My hardware won't do an upgrade install. I need the DVD to do a
>> clean install if and when I want to get around to it. Bummer!
>
> When I did the electronic purchase for $39.99, the files downloaded
> into C:\ESD on the purchasing machine (my laptop).
>
> Initially I was concerned about losing the files. I didn't know
> where they were, looked in %temp% and so on.
>
> Anyway, if you run the tool again, it presents the same options
> for post-usage of the C:\ESD folder. It will make an ISO9660 file
> for you. It can also load a USB flash key with the files. I used the
> USB key option, but also had it prepare the ISO9660 file for storage
> on this machine.
>
> My desktop machine is where I installed the resulting 64 bit download.
> The order machine runs a 64 bit OS, so the purchase would be
> for 64 bit download as well. Then, I transferred over to the desktop
> machine, to do the actual install (previously, the desktop used
> a 32 bit OS). And, as a precaution, I also ran the upgrade tool
> on this machine, to make sure there were no outstanding issues
> (no complaints about NX/XD support).
>
> So while the download is scary, and initially you'd be worried about
> losing the contents of C:\ESD, in fact the tool is re-entrant, and
> you can go back and prepare other media formats. Like DVD (using
> build-in windows burner), ISO9660, or USB key (prepared the same
> way as the previous "Windows 7, microsoftstore" tool would do it).
>
> Paul

Did you find a way to avoid downloading Windows 8? I didn't see this
option. When I purchased a Windows 8 Upgrade for one of my Dell Latitude
ST machines, it started to download a copy. I didn't need it since I
already have the retail boxed set of Windows 8 Pro Upgrade. So I paused
the download. I didn't see anyway to unload it and get rid of the
utility.

I didn't spend a lot of time on this problem since I was going to do a
clean install of Windows 8 anyway and thus everything on that drive just
didn't matter. But I am going to probably upgrade some other computers
here before January 31st. So I am going to have to figure something out
to avoid this problem. Worse comes to worse, I could always restore from
a backup. ;-)

--
Bill
Gateway M465e ('06 era) - OE-QuoteFix v1.19.2
Centrino Core2 Duo T5600 1.83GHz - 4GB - Windows XP SP2

Robin Bignall
December 29th 12, 06:16 PM
On Sat, 29 Dec 2012 02:16:07 -0600, "BillW50" > wrote:

>In ,
>Paul typed:
>> Robin Bignall wrote:
>>> This is the latest Win 8 upgrade offer in the UK. At 24.99 UKP it's
>>> a good price.
>>> http://www.microsoftstore.com/store/msuk/en_GB/pdp/productID.257641900/pgm.81522200
>>>
>>> To get to it I clicked on the $39.99 latest offer in the US
>>>
>>> http://windows.microsoft.com/en-US/windows/buy
>>>
>>> and then selected "Or get the upgrade on DVD from the Microsoft
>>> Store". Notice it transferred to the UK store but the only option is
>>> download
>>> and install. No DVD, and I can't see an option to download and save
>>> for installation later.
>>> My hardware won't do an upgrade install. I need the DVD to do a
>>> clean install if and when I want to get around to it. Bummer!
>>
>> When I did the electronic purchase for $39.99, the files downloaded
>> into C:\ESD on the purchasing machine (my laptop).
>>
>> Initially I was concerned about losing the files. I didn't know
>> where they were, looked in %temp% and so on.
>>
Got it, Paul. Copied c:\esd to E: as a precaution.

>> Anyway, if you run the tool again, it presents the same options
>> for post-usage of the C:\ESD folder. It will make an ISO9660 file
>> for you. It can also load a USB flash key with the files. I used the
>> USB key option, but also had it prepare the ISO9660 file for storage
>> on this machine.
>>
>> My desktop machine is where I installed the resulting 64 bit download.
>> The order machine runs a 64 bit OS, so the purchase would be
>> for 64 bit download as well. Then, I transferred over to the desktop
>> machine, to do the actual install (previously, the desktop used
>> a 32 bit OS). And, as a precaution, I also ran the upgrade tool
>> on this machine, to make sure there were no outstanding issues
>> (no complaints about NX/XD support).
>>
>> So while the download is scary, and initially you'd be worried about
>> losing the contents of C:\ESD, in fact the tool is re-entrant, and
>> you can go back and prepare other media formats. Like DVD (using
>> build-in windows burner), ISO9660, or USB key (prepared the same
>> way as the previous "Windows 7, microsoftstore" tool would do it).
>>
>> Paul
>
>Did you find a way to avoid downloading Windows 8? I didn't see this
>option. When I purchased a Windows 8 Upgrade for one of my Dell Latitude
>ST machines, it started to download a copy. I didn't need it since I
>already have the retail boxed set of Windows 8 Pro Upgrade. So I paused
>the download. I didn't see anyway to unload it and get rid of the
>utility.
>
I didn't see a way of stopping the download, Bill, even though I ordered
a backup DVD as well.

--
Robin Bignall
Herts, England

...winston[_2_]
December 29th 12, 08:23 PM
When you purchase the upgrade an email is sent to email adddress entered during the purchase process. It contains a link for you to
return and download the iso file to create an installation dvd. (Note: ensure your isp doesn't filter the email to your web server
account's junk folder or your local email client doesn't filter to your local email client junk folder).

The architecture of the pc o/s (32 or 64 bit) downloading the iso file determines which version of Win8 is received.(i.e. if you
use a 32 bit o/s to download you'll get the 32 bit version of Win8...likewise use 64 bit o/s, you'll obtain 64 bit Win8)

Upgrades are intended for upgrading 'on-top' of an existing o/s. While it is technically feasible to perform a clean install
(install to a bare drive) with the upgrade iso...if your current o/s is XP or Vista the upgrade will perform (since no other route
is possible from XP or Vista) a clean install.

The real question, if you care to elaborate further:
- Why won't your hardware do an upgrade install ?

--
....winston
msft mvp consumer apps

"Robin Bignall" wrote in message ...

This is the latest Win 8 upgrade offer in the UK. At 24.99 UKP it's a
good price.
http://www.microsoftstore.com/store/msuk/en_GB/pdp/productID.257641900/pgm.81522200

To get to it I clicked on the $39.99 latest offer in the US

http://windows.microsoft.com/en-US/windows/buy

and then selected "Or get the upgrade on DVD from the Microsoft Store".

Notice it transferred to the UK store but the only option is download
and install. No DVD, and I can't see an option to download and save for
installation later.
My hardware won't do an upgrade install. I need the DVD to do a clean
install if and when I want to get around to it. Bummer!
--
Robin Bignall
Herts, England

Robin Bignall
December 29th 12, 09:42 PM
On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
wrote:

>The real question, if you care to elaborate further:
>- Why won't your hardware do an upgrade install ?

I went through this way upthread, Winston. During the upgrade process
the installer issues reboot requests. My hardware, for some reason,
ignores them. So, what should have been done during the reboot does not
get done and the install fails. Clean installs do not issue reboots.

I have checked my motherboard to see if anyone else has reported this
(Paul had a search too) and I can find nothing. This is a new, modern
M/B -- Gigabyte GA-X79-UD3.

(What you actually see during the install is the installer window saying
something like "Press 'next' to reboot your system". You press, the
window shuts and immediately reopens again. It expects that a reboot
has been done, but it hasn't, so whatever should have happened during
the reboot has not happened. The installer tries to continue but says
it can't find the files it's looking for and exits. If you do a manual
reboot at that 'next', the system does not pick up that an installer was
supposed to be running. If you restart the installer it starts at the
beginning again.)
--
Robin Bignall
Herts, England

BillW50
December 29th 12, 11:22 PM
On 12/29/2012 11:16 AM, Robin Bignall wrote:
> On Sat, 29 Dec 2012 02:16:07 -0600, > wrote:
>> Did you find a way to avoid downloading Windows 8? I didn't see this
>> option. When I purchased a Windows 8 Upgrade for one of my Dell Latitude
>> ST machines, it started to download a copy. I didn't need it since I
>> already have the retail boxed set of Windows 8 Pro Upgrade. So I paused
>> the download. I didn't see anyway to unload it and get rid of the
>> utility.
>>
> I didn't see a way of stopping the download, Bill, even though I ordered
> a backup DVD as well.

Thanks Robin. I think it is there somewhere. I am going to be ordering
some more so I have to avoid this later. :-(

--
Bill
Gateway M465e ('06 era) - Thunderbird v12
Centrino Core2 Duo T7400 2.16 GHz - 4GB - Windows 8

BillW50
December 29th 12, 11:56 PM
On 12/29/2012 1:23 PM, ...winston wrote:
> When you purchase the upgrade an email is sent to email adddress entered
> during the purchase process. It contains a link for you to return and
> download the iso file to create an installation dvd. (Note: ensure your
> isp doesn't filter the email to your web server account's junk folder or
> your local email client doesn't filter to your local email client junk
> folder).

Not in my case and apparently not for others. It wanted to force you to
download Windows 8 whether you liked it or not. I could pause it, but
that is about all the control I had. I restored from a recent backup, so
all was fine. Although one shouldn't have to resort to such drastic
measures.

--
Bill
Gateway M465e ('06 era) - Thunderbird v12
Centrino Core2 Duo T7400 2.16 GHz - 4GB - Windows 8

Paul
December 30th 12, 12:51 AM
BillW50 wrote:
> On 12/29/2012 1:23 PM, ...winston wrote:
>> When you purchase the upgrade an email is sent to email adddress entered
>> during the purchase process. It contains a link for you to return and
>> download the iso file to create an installation dvd. (Note: ensure your
>> isp doesn't filter the email to your web server account's junk folder or
>> your local email client doesn't filter to your local email client junk
>> folder).
>
> Not in my case and apparently not for others. It wanted to force you to
> download Windows 8 whether you liked it or not. I could pause it, but
> that is about all the control I had. I restored from a recent backup, so
> all was fine. Although one shouldn't have to resort to such drastic
> measures.
>

According to this (scroll to the end of step 14)...

http://eightforums.com/tutorials/11885-windows-8-upgrade-assistant-download-run.html

"14. This is the product key number (license) for your purchased Windows 8 upgrade.
I would recommend that you click on the View Receipt link to Print or Save a
copy of your "order summary" that includes your product key number for safe
keeping. When finished, click on Next. (see screenshot below)

If you have already downloaded an ISO file with the upgrade assistant for this
same edition of Windows 8 you purchased now, and are just purchasing (up to 5)
another product key number for it, then you can close the Windows 8 Upgrade
Assistant now to avoid having to go through the download process (step 16 below)
again.
"

So that's their advice.

I would expect though, the Assistant is going to remember the download did not
complete, so the tool won't be exactly "stateless" the next time it starts.

Paul

Gene E. Bloch[_2_]
December 30th 12, 02:28 AM
On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:

> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
> wrote:
>
>>The real question, if you care to elaborate further:
>>- Why won't your hardware do an upgrade install ?
>
> I went through this way upthread, Winston. During the upgrade process
> the installer issues reboot requests. My hardware, for some reason,
> ignores them. So, what should have been done during the reboot does not
> get done and the install fails. Clean installs do not issue reboots.
>
> I have checked my motherboard to see if anyone else has reported this
> (Paul had a search too) and I can find nothing. This is a new, modern
> M/B -- Gigabyte GA-X79-UD3.
>
> (What you actually see during the install is the installer window saying
> something like "Press 'next' to reboot your system". You press, the
> window shuts and immediately reopens again. It expects that a reboot
> has been done, but it hasn't, so whatever should have happened during
> the reboot has not happened. The installer tries to continue but says
> it can't find the files it's looking for and exits. If you do a manual
> reboot at that 'next', the system does not pick up that an installer was
> supposed to be running. If you restart the installer it starts at the
> beginning again.)

Reading your scenario above, it looks to me like you made the same
mistake I did a while back.

The deal is that the second and subsequent boots are *not* from the DVD.
When you are asked to press any key to reboot, *don't do it*. Let it
boot from the partially completed installation on the hard drive.

These days I cross my arms over my chest when the shutdown starts and
keep them there until reboot happens. That keeps me out of trouble.

--
Gene E. Bloch (Stumbling Bloch)

..winston
December 30th 12, 02:51 AM
--
....winston
msft mvp


"BillW50" wrote in message ...
>
Not in my case and apparently not for others. It wanted to force you to
download Windows 8 whether you liked it or not. I could pause it, but
that is about all the control I had. I restored from a recent backup, so
all was fine.
>

No matter which route you take...an email will be sent to the email address of record used during the purchase process with the
following information:
<qp>
This email will contain your order number, product key number, a link to download Windows 8 again, and a link to order a DVD.
</qp>

Robin Bignall
December 30th 12, 08:02 PM
On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
> wrote:

>On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>
>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>> wrote:
>>
>>>The real question, if you care to elaborate further:
>>>- Why won't your hardware do an upgrade install ?
>>
>> I went through this way upthread, Winston. During the upgrade process
>> the installer issues reboot requests. My hardware, for some reason,
>> ignores them. So, what should have been done during the reboot does not
>> get done and the install fails. Clean installs do not issue reboots.
>>
>> I have checked my motherboard to see if anyone else has reported this
>> (Paul had a search too) and I can find nothing. This is a new, modern
>> M/B -- Gigabyte GA-X79-UD3.
>>
>> (What you actually see during the install is the installer window saying
>> something like "Press 'next' to reboot your system". You press, the
>> window shuts and immediately reopens again. It expects that a reboot
>> has been done, but it hasn't, so whatever should have happened during
>> the reboot has not happened. The installer tries to continue but says
>> it can't find the files it's looking for and exits. If you do a manual
>> reboot at that 'next', the system does not pick up that an installer was
>> supposed to be running. If you restart the installer it starts at the
>> beginning again.)
>
>Reading your scenario above, it looks to me like you made the same
>mistake I did a while back.
>
>The deal is that the second and subsequent boots are *not* from the DVD.
>When you are asked to press any key to reboot, *don't do it*. Let it
>boot from the partially completed installation on the hard drive.
>
Yes, I know that, but there is no partially-completed installation,
Gene. And the Win8 installer does not say 'press any key to reboot'. It
just issues a 'restart' command and shuts down, leaving itself pending,
but the hardware ignores the command. The installer then restarts
assuming the reboot has happened.

Anyway, today I decided to try installing the Win8 that I bought and
downloaded to the desk top yesterday. It started, and went to get
updates. Then it told me that it would reboot when I pressed 'next'.
When I did, the installer window closed. Needless to say, it didn't
reboot, and the installer window opened again (assuming the reboot had
been done) and showed me the licence. I accepted that and then it
started installing..10%..30%..60%. I thought it was going to work. At
80% it said 'in a few moments your computer will reboot'. The few
moments passed, then up came a grey, unassuming OK box that simply said
'Windows 8 has failed to install'. No error code.
That was that.

If I go to shutdown and select 'restart' the system will reboot. If
some installation ends up with 'restart now' and 'restart later' boxes,
and I choose the former, it reboots. But if a program such as an
installer issues a 'restart' command internally, my hardware ignores it.
That is the problem.
--
Robin Bignall
Herts, England

Gene E. Bloch[_2_]
December 31st 12, 12:04 AM
On Sun, 30 Dec 2012 19:02:34 +0000, Robin Bignall wrote:

> On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
> > wrote:
>
>>On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>>
>>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>>> wrote:
>>>
>>>>The real question, if you care to elaborate further:
>>>>- Why won't your hardware do an upgrade install ?
>>>
>>> I went through this way upthread, Winston. During the upgrade process
>>> the installer issues reboot requests. My hardware, for some reason,
>>> ignores them. So, what should have been done during the reboot does not
>>> get done and the install fails. Clean installs do not issue reboots.
>>>
>>> I have checked my motherboard to see if anyone else has reported this
>>> (Paul had a search too) and I can find nothing. This is a new, modern
>>> M/B -- Gigabyte GA-X79-UD3.
>>>
>>> (What you actually see during the install is the installer window saying
>>> something like "Press 'next' to reboot your system". You press, the
>>> window shuts and immediately reopens again. It expects that a reboot
>>> has been done, but it hasn't, so whatever should have happened during
>>> the reboot has not happened. The installer tries to continue but says
>>> it can't find the files it's looking for and exits. If you do a manual
>>> reboot at that 'next', the system does not pick up that an installer was
>>> supposed to be running. If you restart the installer it starts at the
>>> beginning again.)
>>
>>Reading your scenario above, it looks to me like you made the same
>>mistake I did a while back.
>>
>>The deal is that the second and subsequent boots are *not* from the DVD.
>>When you are asked to press any key to reboot, *don't do it*. Let it
>>boot from the partially completed installation on the hard drive.
>>
> Yes, I know that, but there is no partially-completed installation,
> Gene. And the Win8 installer does not say 'press any key to reboot'. It
> just issues a 'restart' command and shuts down, leaving itself pending,
> but the hardware ignores the command. The installer then restarts
> assuming the reboot has happened.
>
> Anyway, today I decided to try installing the Win8 that I bought and
> downloaded to the desk top yesterday. It started, and went to get
> updates. Then it told me that it would reboot when I pressed 'next'.
> When I did, the installer window closed. Needless to say, it didn't
> reboot, and the installer window opened again (assuming the reboot had
> been done) and showed me the licence. I accepted that and then it
> started installing..10%..30%..60%. I thought it was going to work. At
> 80% it said 'in a few moments your computer will reboot'. The few
> moments passed, then up came a grey, unassuming OK box that simply said
> 'Windows 8 has failed to install'. No error code.
> That was that.
>
> If I go to shutdown and select 'restart' the system will reboot. If
> some installation ends up with 'restart now' and 'restart later' boxes,
> and I choose the former, it reboots. But if a program such as an
> installer issues a 'restart' command internally, my hardware ignores it.
> That is the problem.

Sorry that my guess wasn't correct. I read your statements as a bit
ambiguous, and on the off-chance that one of my interpretations was
correct, it seemed to be worth posting my idea. I wish it had helped...

As you might guess, I therefore have no useful ideas. Your problem seems
bizarre enough. Even the idea of BIOS settings doesn't make sense (to
me, anyway), since shutdown as a command doesn't mean sleep or
whatever...

Additionally, I don't think I understand that if the computer hasn't
rebooted, it manages to run the installer again. Does that mean it
doesn't even shut down? You said "It just issues a 'restart' command and
shuts down"; I thought that meant the computer, but now I am guessing
that it means the program.

--
Gene E. Bloch (Stumbling Bloch)

Robin Bignall
December 31st 12, 12:25 AM
On Sun, 30 Dec 2012 15:04:02 -0800, "Gene E. Bloch"
> wrote:

>On Sun, 30 Dec 2012 19:02:34 +0000, Robin Bignall wrote:
>
>> On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
>> > wrote:
>>
>>>On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>>>
>>>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>>>> wrote:
>>>>
>>>>>The real question, if you care to elaborate further:
>>>>>- Why won't your hardware do an upgrade install ?
>>>>
>>>> I went through this way upthread, Winston. During the upgrade process
>>>> the installer issues reboot requests. My hardware, for some reason,
>>>> ignores them. So, what should have been done during the reboot does not
>>>> get done and the install fails. Clean installs do not issue reboots.
>>>>
>>>> I have checked my motherboard to see if anyone else has reported this
>>>> (Paul had a search too) and I can find nothing. This is a new, modern
>>>> M/B -- Gigabyte GA-X79-UD3.
>>>>
>>>> (What you actually see during the install is the installer window saying
>>>> something like "Press 'next' to reboot your system". You press, the
>>>> window shuts and immediately reopens again. It expects that a reboot
>>>> has been done, but it hasn't, so whatever should have happened during
>>>> the reboot has not happened. The installer tries to continue but says
>>>> it can't find the files it's looking for and exits. If you do a manual
>>>> reboot at that 'next', the system does not pick up that an installer was
>>>> supposed to be running. If you restart the installer it starts at the
>>>> beginning again.)
>>>
>>>Reading your scenario above, it looks to me like you made the same
>>>mistake I did a while back.
>>>
>>>The deal is that the second and subsequent boots are *not* from the DVD.
>>>When you are asked to press any key to reboot, *don't do it*. Let it
>>>boot from the partially completed installation on the hard drive.
>>>
>> Yes, I know that, but there is no partially-completed installation,
>> Gene. And the Win8 installer does not say 'press any key to reboot'. It
>> just issues a 'restart' command and shuts down, leaving itself pending,
>> but the hardware ignores the command. The installer then restarts
>> assuming the reboot has happened.
>>
>> Anyway, today I decided to try installing the Win8 that I bought and
>> downloaded to the desk top yesterday. It started, and went to get
>> updates. Then it told me that it would reboot when I pressed 'next'.
>> When I did, the installer window closed. Needless to say, it didn't
>> reboot, and the installer window opened again (assuming the reboot had
>> been done) and showed me the licence. I accepted that and then it
>> started installing..10%..30%..60%. I thought it was going to work. At
>> 80% it said 'in a few moments your computer will reboot'. The few
>> moments passed, then up came a grey, unassuming OK box that simply said
>> 'Windows 8 has failed to install'. No error code.
>> That was that.
>>
>> If I go to shutdown and select 'restart' the system will reboot. If
>> some installation ends up with 'restart now' and 'restart later' boxes,
>> and I choose the former, it reboots. But if a program such as an
>> installer issues a 'restart' command internally, my hardware ignores it.
>> That is the problem.
>
>Sorry that my guess wasn't correct. I read your statements as a bit
>ambiguous, and on the off-chance that one of my interpretations was
>correct, it seemed to be worth posting my idea. I wish it had helped...
>
>As you might guess, I therefore have no useful ideas. Your problem seems
>bizarre enough. Even the idea of BIOS settings doesn't make sense (to
>me, anyway), since shutdown as a command doesn't mean sleep or
>whatever...
>
>Additionally, I don't think I understand that if the computer hasn't
>rebooted, it manages to run the installer again. Does that mean it
>doesn't even shut down? You said "It just issues a 'restart' command and
>shuts down"; I thought that meant the computer, but now I am guessing
>that it means the program.

Yes, the installer program.
It closes the installer window, calls for a reboot from the system, and
then immediately reopens the window again and carries on, not knowing
that the reboot hasn't happened. But because it hasn't happened,
whatever should have been done during the reboot, but which hasn't been
done, causes the install to eventually fail.

It happens almost immediately if I try to install from DVD. The
installer fails at the very next step after getting updates, because it
can't find the licence on C: that it's installing to. Thus, one of the
things that must happen on the reboot is the copying of the licence from
DVD to C:. When installing from desktop, the licence is already on C:,
so it finds it and breaks down at a later, failing reboot at 80% done.

I hope that's fairly clear. Why it's happening on my hardware, I
haven't a clue. Nobody else has found it or brought it up as far as I
can tell. There's nothing in BIOS, and it's maddening: it means that to
get W8 I shall have to do a clean install. That's a lot of work; more
than 60 programs to reinstall.
--
Robin Bignall
Herts, England

Gene E. Bloch[_2_]
December 31st 12, 12:54 AM
On Sun, 30 Dec 2012 23:25:14 +0000, Robin Bignall wrote:

> On Sun, 30 Dec 2012 15:04:02 -0800, "Gene E. Bloch"
> > wrote:
>
>>On Sun, 30 Dec 2012 19:02:34 +0000, Robin Bignall wrote:
>>
>>> On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
>>> > wrote:
>>>
>>>>On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>>>>
>>>>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>>>>> wrote:
>>>>>
>>>>>>The real question, if you care to elaborate further:
>>>>>>- Why won't your hardware do an upgrade install ?
>>>>>
>>>>> I went through this way upthread, Winston. During the upgrade process
>>>>> the installer issues reboot requests. My hardware, for some reason,
>>>>> ignores them. So, what should have been done during the reboot does not
>>>>> get done and the install fails. Clean installs do not issue reboots.
>>>>>
>>>>> I have checked my motherboard to see if anyone else has reported this
>>>>> (Paul had a search too) and I can find nothing. This is a new, modern
>>>>> M/B -- Gigabyte GA-X79-UD3.
>>>>>
>>>>> (What you actually see during the install is the installer window saying
>>>>> something like "Press 'next' to reboot your system". You press, the
>>>>> window shuts and immediately reopens again. It expects that a reboot
>>>>> has been done, but it hasn't, so whatever should have happened during
>>>>> the reboot has not happened. The installer tries to continue but says
>>>>> it can't find the files it's looking for and exits. If you do a manual
>>>>> reboot at that 'next', the system does not pick up that an installer was
>>>>> supposed to be running. If you restart the installer it starts at the
>>>>> beginning again.)
>>>>
>>>>Reading your scenario above, it looks to me like you made the same
>>>>mistake I did a while back.
>>>>
>>>>The deal is that the second and subsequent boots are *not* from the DVD.
>>>>When you are asked to press any key to reboot, *don't do it*. Let it
>>>>boot from the partially completed installation on the hard drive.
>>>>
>>> Yes, I know that, but there is no partially-completed installation,
>>> Gene. And the Win8 installer does not say 'press any key to reboot'. It
>>> just issues a 'restart' command and shuts down, leaving itself pending,
>>> but the hardware ignores the command. The installer then restarts
>>> assuming the reboot has happened.
>>>
>>> Anyway, today I decided to try installing the Win8 that I bought and
>>> downloaded to the desk top yesterday. It started, and went to get
>>> updates. Then it told me that it would reboot when I pressed 'next'.
>>> When I did, the installer window closed. Needless to say, it didn't
>>> reboot, and the installer window opened again (assuming the reboot had
>>> been done) and showed me the licence. I accepted that and then it
>>> started installing..10%..30%..60%. I thought it was going to work. At
>>> 80% it said 'in a few moments your computer will reboot'. The few
>>> moments passed, then up came a grey, unassuming OK box that simply said
>>> 'Windows 8 has failed to install'. No error code.
>>> That was that.
>>>
>>> If I go to shutdown and select 'restart' the system will reboot. If
>>> some installation ends up with 'restart now' and 'restart later' boxes,
>>> and I choose the former, it reboots. But if a program such as an
>>> installer issues a 'restart' command internally, my hardware ignores it.
>>> That is the problem.
>>
>>Sorry that my guess wasn't correct. I read your statements as a bit
>>ambiguous, and on the off-chance that one of my interpretations was
>>correct, it seemed to be worth posting my idea. I wish it had helped...
>>
>>As you might guess, I therefore have no useful ideas. Your problem seems
>>bizarre enough. Even the idea of BIOS settings doesn't make sense (to
>>me, anyway), since shutdown as a command doesn't mean sleep or
>>whatever...
>>
>>Additionally, I don't think I understand that if the computer hasn't
>>rebooted, it manages to run the installer again. Does that mean it
>>doesn't even shut down? You said "It just issues a 'restart' command and
>>shuts down"; I thought that meant the computer, but now I am guessing
>>that it means the program.
>
> Yes, the installer program.
> It closes the installer window, calls for a reboot from the system, and
> then immediately reopens the window again and carries on, not knowing
> that the reboot hasn't happened. But because it hasn't happened,
> whatever should have been done during the reboot, but which hasn't been
> done, causes the install to eventually fail.
>
> It happens almost immediately if I try to install from DVD. The
> installer fails at the very next step after getting updates, because it
> can't find the licence on C: that it's installing to. Thus, one of the
> things that must happen on the reboot is the copying of the licence from
> DVD to C:. When installing from desktop, the licence is already on C:,
> so it finds it and breaks down at a later, failing reboot at 80% done.
>
> I hope that's fairly clear. Why it's happening on my hardware, I
> haven't a clue. Nobody else has found it or brought it up as far as I
> can tell. There's nothing in BIOS, and it's maddening: it means that to
> get W8 I shall have to do a clean install. That's a lot of work; more
> than 60 programs to reinstall.

:-(

By now, that emoticon is all I can offer, sadly.

I hope the rest of the New Year season goes well for you, i.e., have a
happy New Year otherwise...

--
Gene E. Bloch (Stumbling Bloch)

Paul
December 31st 12, 01:02 AM
Robin Bignall wrote:
> On Sun, 30 Dec 2012 15:04:02 -0800, "Gene E. Bloch"
> > wrote:
>
>> On Sun, 30 Dec 2012 19:02:34 +0000, Robin Bignall wrote:
>>
>>> On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
>>> > wrote:
>>>
>>>> On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>>>>
>>>>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>>>>> wrote:
>>>>>
>>>>>> The real question, if you care to elaborate further:
>>>>>> - Why won't your hardware do an upgrade install ?
>>>>> I went through this way upthread, Winston. During the upgrade process
>>>>> the installer issues reboot requests. My hardware, for some reason,
>>>>> ignores them. So, what should have been done during the reboot does not
>>>>> get done and the install fails. Clean installs do not issue reboots.
>>>>>
>>>>> I have checked my motherboard to see if anyone else has reported this
>>>>> (Paul had a search too) and I can find nothing. This is a new, modern
>>>>> M/B -- Gigabyte GA-X79-UD3.
>>>>>
>>>>> (What you actually see during the install is the installer window saying
>>>>> something like "Press 'next' to reboot your system". You press, the
>>>>> window shuts and immediately reopens again. It expects that a reboot
>>>>> has been done, but it hasn't, so whatever should have happened during
>>>>> the reboot has not happened. The installer tries to continue but says
>>>>> it can't find the files it's looking for and exits. If you do a manual
>>>>> reboot at that 'next', the system does not pick up that an installer was
>>>>> supposed to be running. If you restart the installer it starts at the
>>>>> beginning again.)
>>>> Reading your scenario above, it looks to me like you made the same
>>>> mistake I did a while back.
>>>>
>>>> The deal is that the second and subsequent boots are *not* from the DVD.
>>>> When you are asked to press any key to reboot, *don't do it*. Let it
>>>> boot from the partially completed installation on the hard drive.
>>>>
>>> Yes, I know that, but there is no partially-completed installation,
>>> Gene. And the Win8 installer does not say 'press any key to reboot'. It
>>> just issues a 'restart' command and shuts down, leaving itself pending,
>>> but the hardware ignores the command. The installer then restarts
>>> assuming the reboot has happened.
>>>
>>> Anyway, today I decided to try installing the Win8 that I bought and
>>> downloaded to the desk top yesterday. It started, and went to get
>>> updates. Then it told me that it would reboot when I pressed 'next'.
>>> When I did, the installer window closed. Needless to say, it didn't
>>> reboot, and the installer window opened again (assuming the reboot had
>>> been done) and showed me the licence. I accepted that and then it
>>> started installing..10%..30%..60%. I thought it was going to work. At
>>> 80% it said 'in a few moments your computer will reboot'. The few
>>> moments passed, then up came a grey, unassuming OK box that simply said
>>> 'Windows 8 has failed to install'. No error code.
>>> That was that.
>>>
>>> If I go to shutdown and select 'restart' the system will reboot. If
>>> some installation ends up with 'restart now' and 'restart later' boxes,
>>> and I choose the former, it reboots. But if a program such as an
>>> installer issues a 'restart' command internally, my hardware ignores it.
>>> That is the problem.
>> Sorry that my guess wasn't correct. I read your statements as a bit
>> ambiguous, and on the off-chance that one of my interpretations was
>> correct, it seemed to be worth posting my idea. I wish it had helped...
>>
>> As you might guess, I therefore have no useful ideas. Your problem seems
>> bizarre enough. Even the idea of BIOS settings doesn't make sense (to
>> me, anyway), since shutdown as a command doesn't mean sleep or
>> whatever...
>>
>> Additionally, I don't think I understand that if the computer hasn't
>> rebooted, it manages to run the installer again. Does that mean it
>> doesn't even shut down? You said "It just issues a 'restart' command and
>> shuts down"; I thought that meant the computer, but now I am guessing
>> that it means the program.
>
> Yes, the installer program.
> It closes the installer window, calls for a reboot from the system, and
> then immediately reopens the window again and carries on, not knowing
> that the reboot hasn't happened. But because it hasn't happened,
> whatever should have been done during the reboot, but which hasn't been
> done, causes the install to eventually fail.
>
> It happens almost immediately if I try to install from DVD. The
> installer fails at the very next step after getting updates, because it
> can't find the licence on C: that it's installing to. Thus, one of the
> things that must happen on the reboot is the copying of the licence from
> DVD to C:. When installing from desktop, the licence is already on C:,
> so it finds it and breaks down at a later, failing reboot at 80% done.
>
> I hope that's fairly clear. Why it's happening on my hardware, I
> haven't a clue. Nobody else has found it or brought it up as far as I
> can tell. There's nothing in BIOS, and it's maddening: it means that to
> get W8 I shall have to do a clean install. That's a lot of work; more
> than 60 programs to reinstall.

The BIOS probably makes some of the controls accessible as ACPI objects.
Lots of those are assigned standard numbers. And names like "power button".

You'd need to boot something like the recovery console (or something like
whatever WinPE is), and run the equivalent of Everest, and get a listing
of ACPI objects. And see if you recognize anything out of sorts there.

It's possible the installer isn't using the ACPI object offered by the
BIOS, and there's a lack of communications between the two of them.

Just for laughs, you could enter the BIOS, and see if there is an
APM versus ACPI option (APM is an older standard for passing stuff
from OS to BIOS). Or even, check the BIOS and see if there
is an "ACPI 2.0" [Enable] option. Going backwards to APM, might
restore communications between the installer and BIOS. Of, going
forward, and enabling ACPI 2.0, might help (if, say, the installer
no longer recognizes any standard before ACPI 2.0). The goofy thing
is, Asus motherboards *disable* ACPI 2.0 by default. It's one of
the things on my "must fix" list, when I get a new motherboard.

Paul

Robin Bignall
December 31st 12, 01:43 AM
On Sun, 30 Dec 2012 19:02:45 -0500, Paul > wrote:

>Robin Bignall wrote:
>> On Sun, 30 Dec 2012 15:04:02 -0800, "Gene E. Bloch"
>> > wrote:
>>
>>> On Sun, 30 Dec 2012 19:02:34 +0000, Robin Bignall wrote:
>>>
>>>> On Sat, 29 Dec 2012 17:28:16 -0800, "Gene E. Bloch"
>>>> > wrote:
>>>>
>>>>> On Sat, 29 Dec 2012 20:42:20 +0000, Robin Bignall wrote:
>>>>>
>>>>>> On Sat, 29 Dec 2012 12:23:54 -0700, "...winston" >
>>>>>> wrote:
>>>>>>
>>>>>>> The real question, if you care to elaborate further:
>>>>>>> - Why won't your hardware do an upgrade install ?
>>>>>> I went through this way upthread, Winston. During the upgrade process
>>>>>> the installer issues reboot requests. My hardware, for some reason,
>>>>>> ignores them. So, what should have been done during the reboot does not
>>>>>> get done and the install fails. Clean installs do not issue reboots.
>>>>>>
>>>>>> I have checked my motherboard to see if anyone else has reported this
>>>>>> (Paul had a search too) and I can find nothing. This is a new, modern
>>>>>> M/B -- Gigabyte GA-X79-UD3.
>>>>>>
>>>>>> (What you actually see during the install is the installer window saying
>>>>>> something like "Press 'next' to reboot your system". You press, the
>>>>>> window shuts and immediately reopens again. It expects that a reboot
>>>>>> has been done, but it hasn't, so whatever should have happened during
>>>>>> the reboot has not happened. The installer tries to continue but says
>>>>>> it can't find the files it's looking for and exits. If you do a manual
>>>>>> reboot at that 'next', the system does not pick up that an installer was
>>>>>> supposed to be running. If you restart the installer it starts at the
>>>>>> beginning again.)
>>>>> Reading your scenario above, it looks to me like you made the same
>>>>> mistake I did a while back.
>>>>>
>>>>> The deal is that the second and subsequent boots are *not* from the DVD.
>>>>> When you are asked to press any key to reboot, *don't do it*. Let it
>>>>> boot from the partially completed installation on the hard drive.
>>>>>
>>>> Yes, I know that, but there is no partially-completed installation,
>>>> Gene. And the Win8 installer does not say 'press any key to reboot'. It
>>>> just issues a 'restart' command and shuts down, leaving itself pending,
>>>> but the hardware ignores the command. The installer then restarts
>>>> assuming the reboot has happened.
>>>>
>>>> Anyway, today I decided to try installing the Win8 that I bought and
>>>> downloaded to the desk top yesterday. It started, and went to get
>>>> updates. Then it told me that it would reboot when I pressed 'next'.
>>>> When I did, the installer window closed. Needless to say, it didn't
>>>> reboot, and the installer window opened again (assuming the reboot had
>>>> been done) and showed me the licence. I accepted that and then it
>>>> started installing..10%..30%..60%. I thought it was going to work. At
>>>> 80% it said 'in a few moments your computer will reboot'. The few
>>>> moments passed, then up came a grey, unassuming OK box that simply said
>>>> 'Windows 8 has failed to install'. No error code.
>>>> That was that.
>>>>
>>>> If I go to shutdown and select 'restart' the system will reboot. If
>>>> some installation ends up with 'restart now' and 'restart later' boxes,
>>>> and I choose the former, it reboots. But if a program such as an
>>>> installer issues a 'restart' command internally, my hardware ignores it.
>>>> That is the problem.
>>> Sorry that my guess wasn't correct. I read your statements as a bit
>>> ambiguous, and on the off-chance that one of my interpretations was
>>> correct, it seemed to be worth posting my idea. I wish it had helped...
>>>
>>> As you might guess, I therefore have no useful ideas. Your problem seems
>>> bizarre enough. Even the idea of BIOS settings doesn't make sense (to
>>> me, anyway), since shutdown as a command doesn't mean sleep or
>>> whatever...
>>>
>>> Additionally, I don't think I understand that if the computer hasn't
>>> rebooted, it manages to run the installer again. Does that mean it
>>> doesn't even shut down? You said "It just issues a 'restart' command and
>>> shuts down"; I thought that meant the computer, but now I am guessing
>>> that it means the program.
>>
>> Yes, the installer program.
>> It closes the installer window, calls for a reboot from the system, and
>> then immediately reopens the window again and carries on, not knowing
>> that the reboot hasn't happened. But because it hasn't happened,
>> whatever should have been done during the reboot, but which hasn't been
>> done, causes the install to eventually fail.
>>
>> It happens almost immediately if I try to install from DVD. The
>> installer fails at the very next step after getting updates, because it
>> can't find the licence on C: that it's installing to. Thus, one of the
>> things that must happen on the reboot is the copying of the licence from
>> DVD to C:. When installing from desktop, the licence is already on C:,
>> so it finds it and breaks down at a later, failing reboot at 80% done.
>>
>> I hope that's fairly clear. Why it's happening on my hardware, I
>> haven't a clue. Nobody else has found it or brought it up as far as I
>> can tell. There's nothing in BIOS, and it's maddening: it means that to
>> get W8 I shall have to do a clean install. That's a lot of work; more
>> than 60 programs to reinstall.
>
>The BIOS probably makes some of the controls accessible as ACPI objects.
>Lots of those are assigned standard numbers. And names like "power button".
>
>You'd need to boot something like the recovery console (or something like
>whatever WinPE is), and run the equivalent of Everest, and get a listing
>of ACPI objects. And see if you recognize anything out of sorts there.
>
>It's possible the installer isn't using the ACPI object offered by the
>BIOS, and there's a lack of communications between the two of them.
>
>Just for laughs, you could enter the BIOS, and see if there is an
>APM versus ACPI option (APM is an older standard for passing stuff
>from OS to BIOS). Or even, check the BIOS and see if there
>is an "ACPI 2.0" [Enable] option. Going backwards to APM, might
>restore communications between the installer and BIOS. Of, going
>forward, and enabling ACPI 2.0, might help (if, say, the installer
>no longer recognizes any standard before ACPI 2.0). The goofy thing
>is, Asus motherboards *disable* ACPI 2.0 by default. It's one of
>the things on my "must fix" list, when I get a new motherboard.
>
I'll have a look tomorrow, Paul.
--
Robin Bignall
Herts, England

Robin Bignall
December 31st 12, 04:57 PM
On Mon, 31 Dec 2012 00:43:21 +0000, Robin Bignall
> wrote:

>>The BIOS probably makes some of the controls accessible as ACPI objects.
>>Lots of those are assigned standard numbers. And names like "power button".
>>
The only mention of ACPI in BIOS is 'ACPI sleep state' which is set to
S3.

In device mgr:
'computer' says 'ACPI x86-based PC'
'system devices' says 'ACPI fixed feature button' and 'ACPI power
button'.
The specs on the site below say it's ACPI 2.0a.

>>You'd need to boot something like the recovery console (or something like
>>whatever WinPE is), and run the equivalent of Everest, and get a listing
>>of ACPI objects. And see if you recognize anything out of sorts there.
>>
>>It's possible the installer isn't using the ACPI object offered by the
>>BIOS, and there's a lack of communications between the two of them.
>>
Heaven knows what to do about that. This is a modern UEFI motherboard.
http://www.gigabyte.com/products/product-page.aspx?pid=4050#ov

Very weird, the whole shebang!
--
Robin Bignall
Herts, England

Paul
December 31st 12, 05:35 PM
Robin Bignall wrote:
> On Mon, 31 Dec 2012 00:43:21 +0000, Robin Bignall
> > wrote:
>
>>> The BIOS probably makes some of the controls accessible as ACPI objects.
>>> Lots of those are assigned standard numbers. And names like "power button".
>>>
> The only mention of ACPI in BIOS is 'ACPI sleep state' which is set to
> S3.
>
> In device mgr:
> 'computer' says 'ACPI x86-based PC'
> 'system devices' says 'ACPI fixed feature button' and 'ACPI power
> button'.
> The specs on the site below say it's ACPI 2.0a.
>
>>> You'd need to boot something like the recovery console (or something like
>>> whatever WinPE is), and run the equivalent of Everest, and get a listing
>>> of ACPI objects. And see if you recognize anything out of sorts there.
>>>
>>> It's possible the installer isn't using the ACPI object offered by the
>>> BIOS, and there's a lack of communications between the two of them.
>>>
> Heaven knows what to do about that. This is a modern UEFI motherboard.
> http://www.gigabyte.com/products/product-page.aspx?pid=4050#ov
>
> Very weird, the whole shebang!

OK, had a look at the manual, and anything useful is gone.

*******

The first review here, mentions a problem with power cutting out
on the board.

http://www.newegg.com/Product/Product.aspx?Item=13-128-532

"At first I couldn't even get a windows install going on the machine
and I kept getting hard resets out of nowhere. I did a little research
and found that there was an updated bios that effectively limited power
to certain parts of the board. I just wanted to get it working so I
installed the new bios and all was well."

But looking through the BIOS releases on the web page you show,
there's nothing there admitting to any problems. And "kept
getting hard resets" is the exact opposite of your symptoms,
because in your case, you're not getting a reset pulse.

What do you have plugged into the machine ? Any iPod chargers ?
Any unique plug-in cards in the slots ? I'm just looking for
something that might interfere with the logic in the power
cycling section.

I couldn't find anything in the Newegg reviews, that
matched your symptoms.

You should be running a relatively recent BIOS, because when
your board first shipped, there was a danger of the voltage
regulator on board burning up (while extreme overclocking).
It would seem that the later BIOS changes the power limiter
setting (as if it just wasn't set on the early BIOS). F7
is probably safe, as the release notes mention "improved protection mechanism".
I guess terse working comes from their marketing department
("admit to nothing").

Paul

Robin Bignall
December 31st 12, 06:32 PM
On Mon, 31 Dec 2012 11:35:41 -0500, Paul > wrote:

>Robin Bignall wrote:
>> On Mon, 31 Dec 2012 00:43:21 +0000, Robin Bignall
>> > wrote:
>>
>>>> The BIOS probably makes some of the controls accessible as ACPI objects.
>>>> Lots of those are assigned standard numbers. And names like "power button".
>>>>
>> The only mention of ACPI in BIOS is 'ACPI sleep state' which is set to
>> S3.
>>
>> In device mgr:
>> 'computer' says 'ACPI x86-based PC'
>> 'system devices' says 'ACPI fixed feature button' and 'ACPI power
>> button'.
>> The specs on the site below say it's ACPI 2.0a.
>>
>>>> You'd need to boot something like the recovery console (or something like
>>>> whatever WinPE is), and run the equivalent of Everest, and get a listing
>>>> of ACPI objects. And see if you recognize anything out of sorts there.
>>>>
>>>> It's possible the installer isn't using the ACPI object offered by the
>>>> BIOS, and there's a lack of communications between the two of them.
>>>>
>> Heaven knows what to do about that. This is a modern UEFI motherboard.
>> http://www.gigabyte.com/products/product-page.aspx?pid=4050#ov
>>
>> Very weird, the whole shebang!
>
>OK, had a look at the manual, and anything useful is gone.
>
>*******
>
>The first review here, mentions a problem with power cutting out
>on the board.
>
>http://www.newegg.com/Product/Product.aspx?Item=13-128-532
>
> "At first I couldn't even get a windows install going on the machine
> and I kept getting hard resets out of nowhere. I did a little research
> and found that there was an updated bios that effectively limited power
> to certain parts of the board. I just wanted to get it working so I
> installed the new bios and all was well."
>
>But looking through the BIOS releases on the web page you show,
>there's nothing there admitting to any problems. And "kept
>getting hard resets" is the exact opposite of your symptoms,
>because in your case, you're not getting a reset pulse.
>
>What do you have plugged into the machine ? Any iPod chargers ?
>Any unique plug-in cards in the slots ? I'm just looking for
>something that might interfere with the logic in the power
>cycling section.
>
Nope, nothing special. A PCI modem for phone that I've had for years. A
USB 2 D-Link 7-way USB box with the wireless mouse, keyboard and numeric
pad plugged in. But I tried to install W8 before getting the D-link,
with wireless in regular USB2 slots on M/B. Same problem.

>I couldn't find anything in the Newegg reviews, that
>matched your symptoms.
>
>You should be running a relatively recent BIOS, because when
>your board first shipped, there was a danger of the voltage
>regulator on board burning up (while extreme overclocking).
>It would seem that the later BIOS changes the power limiter
>setting (as if it just wasn't set on the early BIOS). F7
>is probably safe, as the release notes mention "improved protection mechanism".
>I guess terse working comes from their marketing department
>("admit to nothing").
>
I don't overclock and BIOS is dated May, 2012. Level F10.

All very peculiar. Everything else runs fine, installers and all. Just
not Windows.

--
Robin Bignall
Herts, England

Google