virtualbox-V7.0.6-6.2-x86_64.rpm (suse-tw)
16gb ram AMD-8core w. 8gb nvidia video
Win10_22H2_English_x64.iso

Allocated 2gb ram to the guest w10 virtual system, plus something like
35gb disk space (auto default). The install seemed to go well but the
last launch attempt ended with this:

"Windows Setup could not configure Windows to run on this computer's
hardware"

I know my iron ain't exactly new but this....WTF??? During install I
had clicked "I don't have an acticode" (I do for w7 but have never used
it and never will).

On 4/15/2023 10:46 PM, bad sector wrote:
> virtualbox-V7.0.6-6.2-x86_64.rpm (suse-tw)
> 16gb ram  AMD-8core w. 8gb nvidia video
> Win10_22H2_English_x64.iso
>
> Allocated 2gb ram to the guest w10 virtual system, plus something like 35gb disk space (auto default). The install seemed to go well but the last launch attempt ended with this:
>
> "Windows Setup could not configure Windows to run on this computer's hardware"
>
> I know my iron ain't exactly new but this....WTF???  During install I had clicked "I don't have an acticode" (I do for w7 but have never used it and never will).
>

They can sniff the CPU via instruction set testing if they want.
That's the problem with emulation. The CPUID may declare the processor
as a Pentium III, but some instruction set sniffing shows what
is really available.

Normally, the W8/W10/W11 requirements are checked during the
compatibility checking before the installation starts.

Maybe something like SSE2 is required (which might be used by
software developers for block-move operations).

However, recently, some applications in Ring3, have been making
SSE 4.2 a requirement.

*******

This is an example, from a post about six months ago.
The bottom link is available for Windows and Linux, but I
don't know how to use it or anything.

Actually, it's worse than that. Waterfox needs SSE 4.2 .

https://www.ghacks.net/2021/10/20/waterfox-g4-sse4-2-processor/

"Waterfox requires a SSE4.2 compatible CPU

Waterfox G4 has a limitation... "

https://www.reddit.com/r/waterfox/comments/qcxfb7/two_options_what_to_do_if_your_cpu_doesnt_support/

"SSE 4.2 emulation

If you still want to try running Waterfox G4, you can try looking into this direction

https://steamcommunity.com/sharedfiles/filedetails/?id=2362590754

https://www.intel.com/content/www/us/en/developer/articles/tool/software-development-emulator.html
"

And you can see people are working the issue on their own.

https://github.com/mirh/opemu-linux

Somehow, you need to find out what is missing. I'm just guessing
at this, as yours is the first report of this behavior I've heard of.
When an install is done, there are at least a couple logfile written
in dev-Greek, which log what happened on a failure. I would not expect to see in
such a log "platform has no SSE 4.2", because that would be too easy.

SSE 4.2 is merely the most outrageous requirement I've seen to date,
but it might not be the only one.

Paul

On 4/16/23 04:46, bad sector wrote:
> virtualbox-V7.0.6-6.2-x86_64.rpm (suse-tw)
> 16gb ram

should be enough according to:
https://www.microsoft.com/en-us/windows/windows-10-specifications

> AMD-8core

you need one of these CPUs:
https://learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-10-1511-supported-amd-processors

Think you may need to enable in vbox:
- PEA/NX
- Nested AMD-V

> w. 8gb nvidia video

I tend to set max Video Memory, Graphics controller VBoxSVG and enable
3D Acceleration.

> Win10_22H2_English_x64.iso

There seems to be some reporting something similar after upgrade:
https://forums.virtualbox.org/viewtopic.php?t=108525
https://forums.virtualbox.org/viewtopic.php?t=108737
https://www.virtualbox.org/ticket/21590

You can use KVM instead with VirtManager, should work quite well as long
as the CPU is supported for ms-Win10.

--
//Aho

On 4/16/23 12:03, bad sector wrote:
> On 4/16/23 10:41, Paul wrote:
>
>> The timing of the failure is curious. I'd be tempted to do the
>> install with the network cable unplugged, and I bet it will
>> complete and there would be a desktop. It could be some patching
>> operation which has blown the compatibility. The compatibility
>> checking on a DVD image, is supposed to be done before the
>> install "kicks off".
>>
>>     Paul
>
> Bingo! I followed your hunch and repeated the install off-line. First
> attempt failed, it could not find some file, so I 'refreshed' the iso
> file from another copy. Second run it found what it needed but did of
> course want a connection at every turn, all declined. I now have a w10
> VM, later today L'll test it with a conection to see if it stay up,
> gotta run now. Thanks.
>

I knew it. A couple of minutes on-line and NO-GO.
Reinstalled off-line several times, could never
duplicate the successful one, not even for off-line use.

THEN I had the idea to try w7 on the new vBox-7 which
nopw has a new usb listing button where you can check
sharing. I installed the Me80 driver and just wher
it says to turn the Me80 ON I quickly also checked the
Me80 usb item box. It worked, it mighthave wiorked anyway
but I wasn't taking chances. For the first time I now
have full Me80 driver and bundleware functionality
in windows.

I'll get back to w10 later.

On 4/16/2023 5:57 AM, J.O. Aho wrote:
> On 4/16/23 04:46, bad sector wrote:
>> virtualbox-V7.0.6-6.2-x86_64.rpm (suse-tw)
>> 16gb ram
>
> should be enough according to:
> https://www.microsoft.com/en-us/windows/windows-10-specifications
>
>> AMD-8core
>
> you need one of these CPUs:
> https://learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-10-1511-supported-amd-processors
>
> Think you may need to enable in vbox:
> - PEA/NX
> - Nested AMD-V
>
>
>  > w. 8gb nvidia video
>
> I tend to set max Video Memory, Graphics controller VBoxSVG and enable 3D Acceleration.
>
>> Win10_22H2_English_x64.iso
>
> There seems to be some reporting something similar after upgrade:
> https://forums.virtualbox.org/viewtopic.php?t=108525
> https://forums.virtualbox.org/viewtopic.php?t=108737
> https://www.virtualbox.org/ticket/21590
>
> You can use KVM instead with VirtManager, should work quite well as long as the CPU is supported for ms-Win10.
>

Leave it to Microsoft... A later list has some earlier CPUs.

https://learn.microsoft.com/en-us/windows-hardware/design/minimum/supported/windows-10-21h1-supported-amd-processors

AMD Athlon X4 940 == phenom II x4 940 black edition

https://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X4%20940%20Black%20Edition%20-%20HDZ940XCJ4DGI%20%28HDZ940XCGIBOX%29.html

SSE / Streaming SIMD Extensions
SSE2 / Streaming SIMD Extensions
SSE3 / Streaming SIMD Extensions
SSE4a ?
AMD64 / AMD 64-bit technology
AMD-V / AMD Virtualization technology

https://bit-tech.net/reviews/tech/cpus/amd-phenom-ii-x4-940-and-920-review/2/

"SSE4a

SSE4a instruction support is included - just like the 65nm Phenom - and
includes one instruction (POPCNT) only found in Intel's SSE4.2 (Nehalem CPUs),
as well as three other ones unique to AMD. However, it doesn't include support
for video encoding motion estimation (Fast Block Difference and Horizontal
Minimum Search), that greatly helped performance where supported: Divx 6.8 and
TMPEG for example.
"

Having 8 cores, the OPs CPU is a Bulldozer or a SteamRoller,
and a bit more modern than a Phenom II (up to six cores?).
Phenom II is a K10. And the core count on 8-core devices is dubious,
in the sense that the device looks like four cores, with
two "processing heads" on each one. This might mean fewer taps
on some level of caching.

https://en.wikipedia.org/wiki/List_of_AMD_CPU_microarchitectures

As for VirtualBox, it should work better on Linux than on Windows,
because of HyperV.

The timing of the failure is curious. I'd be tempted to do the
install with the network cable unplugged, and I bet it will
complete and there would be a desktop. It could be some patching
operation which has blown the compatibility. The compatibility
checking on a DVD image, is supposed to be done before the
install "kicks off".

Paul

On 4/16/23 10:41, Paul wrote:

> The timing of the failure is curious. I'd be tempted to do the
> install with the network cable unplugged, and I bet it will
> complete and there would be a desktop. It could be some patching
> operation which has blown the compatibility. The compatibility
> checking on a DVD image, is supposed to be done before the
> install "kicks off".
>
>    Paul

Bingo! I followed your hunch and repeated the install off-line. First
attempt failed, it could not find some file, so I 'refreshed' the iso
file from another copy. Second run it found what it needed but did of
course want a connection at every turn, all declined. I now have a w10
VM, later today L'll test it with a conection to see if it stay up,
gotta run now. Thanks.