Yesterday, following disabling hibernation, I thought I had resolved
every problem that had been plagfuing me for several weeks.

This morning I cannot get it start up at all.
It reaches a black screen with a single row of small grey "windows"
near the top and the usual twirling blue circle.

As I write I have tried restarting it while holding down the F8 key in
the hopes of getting into Safe mode.

It is not promising.

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On 7/3/2023 5:56 AM, pinnerite wrote:
> Yesterday, following disabling hibernation, I thought I had resolved
> every problem that had been plagfuing me for several weeks.
>
> This morning I cannot get it start up at all.
>
> It reaches a black screen with a single row of small grey "windows"
> near the top and the usual twirling blue circle.
>
> As I write I have tried restarting it while holding down the F8 key in
> the hopes of getting into Safe mode.
>
> It is not promising.
>
>

It helps if you tell people the brand and model of your computer. Go
find the user manual to figure out how to reset the computer. Some
computers use different key combinations at startup to go into the BIOS.

On Mon, 3 Jul 2023 06:22:55 -0400
😎 Mighty Wannabe ✅ <@.> wrote:

> On 7/3/2023 5:56 AM, pinnerite wrote:
> > Yesterday, following disabling hibernation, I thought I had resolved
> > every problem that had been plagfuing me for several weeks.
> >
> > This morning I cannot get it start up at all.
> >
> > It reaches a black screen with a single row of small grey "windows"
> > near the top and the usual twirling blue circle.
> >
> > As I write I have tried restarting it while holding down the F8 key in
> > the hopes of getting into Safe mode.
> >
> > It is not promising.
> >
> >
>
>
> It helps if you tell people the brand and model of your computer. Go
> find the user manual to figure out how to reset the computer. Some
> computers use different key combinations at startup to go into the BIOS.
>
>
My windows 10 is a virtual machine running on VirtualBox.

Anyway I got in via Safe Mode and closed down before trying again.
That started a cycle of BSODs and reboots with no improvement.
Thr reboots start assoon as i enter my PIN.

Eventually I found out how to stop the automatic reboots.

I am now going to see what happens now. :)

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On Mon, 3 Jul 2023 16:45:31 +0100
pinnerite <pinnerite@gmail.com> wrote:

> On Mon, 3 Jul 2023 06:22:55 -0400
> 😎 Mighty Wannabe ✅ <@.> wrote:
>
> > On 7/3/2023 5:56 AM, pinnerite wrote:
> > > Yesterday, following disabling hibernation, I thought I had resolved
> > > every problem that had been plagfuing me for several weeks.
> > >
> > > This morning I cannot get it start up at all.
> > >
> > > It reaches a black screen with a single row of small grey "windows"
> > > near the top and the usual twirling blue circle.
> > >
> > > As I write I have tried restarting it while holding down the F8 key in
> > > the hopes of getting into Safe mode.
> > >
> > > It is not promising.
> > >
> > >
> >
> >
> > It helps if you tell people the brand and model of your computer. Go
> > find the user manual to figure out how to reset the computer. Some
> > computers use different key combinations at startup to go into the BIOS.
> >
> >
> My windows 10 is a virtual machine running on VirtualBox.
>
> Anyway I got in via Safe Mode and closed down before trying again.
> That started a cycle of BSODs and reboots with no improvement.
> Thr reboots start assoon as i enter my PIN.
>
> Eventually I found out how to stop the automatic reboots.
>
> I am now going to see what happens now. :)
>
Well I have had two normal reboots and it now seems stable.

You know, what really pisses me off is that Microsoft can jump to a
BSOD but cannot display the reason on the screen!

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On 7/3/23 12:13, this is what pinnerite wrote:
> On Mon, 3 Jul 2023 16:45:31 +0100
> pinnerite <pinnerite@gmail.com> wrote:
>
>> On Mon, 3 Jul 2023 06:22:55 -0400
>> 😎 Mighty Wannabe ✅ <@.> wrote:
>>
>>> On 7/3/2023 5:56 AM, pinnerite wrote:
>>>> Yesterday, following disabling hibernation, I thought I had resolved
>>>> every problem that had been plagfuing me for several weeks.
>>>>
>>>> This morning I cannot get it start up at all.
>>>>
>>>> It reaches a black screen with a single row of small grey "windows"
>>>> near the top and the usual twirling blue circle.
>>>>
>>>> As I write I have tried restarting it while holding down the F8 key in
>>>> the hopes of getting into Safe mode.
>>>>
>>>> It is not promising.
>>>>
>>>>
>>>
>>>
>>> It helps if you tell people the brand and model of your computer. Go
>>> find the user manual to figure out how to reset the computer. Some
>>> computers use different key combinations at startup to go into the BIOS.
>>>
>>>
>> My windows 10 is a virtual machine running on VirtualBox.
>>
>> Anyway I got in via Safe Mode and closed down before trying again.
>> That started a cycle of BSODs and reboots with no improvement.
>> Thr reboots start assoon as i enter my PIN.
>>
>> Eventually I found out how to stop the automatic reboots.
>>
>> I am now going to see what happens now. :)
>>
> Well I have had two normal reboots and it now seems stable.
>
> You know, what really pisses me off is that Microsoft can jump to a
> BSOD but cannot display the reason on the screen!
>
>
I always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 7/3/2023 12:13 PM, pinnerite wrote:
> On Mon, 3 Jul 2023 16:45:31 +0100
> pinnerite <pinnerite@gmail.com> wrote:
>
>> On Mon, 3 Jul 2023 06:22:55 -0400
>> 😎 Mighty Wannabe ✅ <@.> wrote:
>>
>>> On 7/3/2023 5:56 AM, pinnerite wrote:
>>>> Yesterday, following disabling hibernation, I thought I had resolved
>>>> every problem that had been plagfuing me for several weeks.
>>>>
>>>> This morning I cannot get it start up at all.
>>>>
>>>> It reaches a black screen with a single row of small grey "windows"
>>>> near the top and the usual twirling blue circle.
>>>>
>>>> As I write I have tried restarting it while holding down the F8 key in
>>>> the hopes of getting into Safe mode.
>>>>
>>>> It is not promising.
>>>>
>>>>
>>>
>>> It helps if you tell people the brand and model of your computer. Go
>>> find the user manual to figure out how to reset the computer. Some
>>> computers use different key combinations at startup to go into the BIOS.
>>>
>>>
>> My windows 10 is a virtual machine running on VirtualBox.
>>
>> Anyway I got in via Safe Mode and closed down before trying again.
>> That started a cycle of BSODs and reboots with no improvement.
>> Thr reboots start assoon as i enter my PIN.
>>
>> Eventually I found out how to stop the automatic reboots.
>>
>> I am now going to see what happens now. :)
>>
> Well I have had two normal reboots and it now seems stable.
>
> You know, what really pisses me off is that Microsoft can jump to a
> BSOD but cannot display the reason on the screen!
>
>

Don't expect a Windows OS running in a virtual box to behave 100% the
same as in a real Windows hardware box. Windows computer is so cheap
these days, you are wasting your time and torturing yourself with a
virtual box.

pinnerite <pinnerite@gmail.com> wrote:

> Yesterday, following disabling hibernation, I thought I had resolved
> every problem that had been plagfuing me for several weeks.
>
> This morning I cannot get it start up at all.
>
> It reaches a black screen with a single row of small grey "windows"
> near the top and the usual twirling blue circle.
>
> As I write I have tried restarting it while holding down the F8 key in
> the hopes of getting into Safe mode.
>
> It is not promising.

Virtualbox lets you save backups (VHD files at the current state). You
can load an old VHD when something gets screwed up in the current one.

https://www.google.com/search?q=virtualbox+backups

Of course, if you are running backups on your computer, those should
capture the .vhd files, too. If you leave your VMs loaded constantly,
make sure the backup software support VSS (Volume Shadow Service). Then
just shutdown or exit the VM, restore the .vhd from your backups, and
restart the VM to be where you were at for state at that time of the
backup.

<Aside>
If you can afford the core(s) and RAM allocation to a constantly running
VM, you can use seamless mode instead of always having a window open to
the guest OS.

https://www.howtogeek.com/171145/use-virtualboxs-seamless-mode-or-vmwares-unity-mode-to-seamlessly-run-programs-from-a-virtual-machine/
</Aside>

On Mon, 3 Jul 2023 17:13:37 +0100
pinnerite <pinnerite@gmail.com> wrote:

> On Mon, 3 Jul 2023 16:45:31 +0100
> pinnerite <pinnerite@gmail.com> wrote:
>
> > On Mon, 3 Jul 2023 06:22:55 -0400
> > 😎 Mighty Wannabe ✅ <@.> wrote:
> >
> > > On 7/3/2023 5:56 AM, pinnerite wrote:
> > > > Yesterday, following disabling hibernation, I thought I had resolved
> > > > every problem that had been plagfuing me for several weeks.
> > > >
> > > > This morning I cannot get it start up at all.
> > > >
> > > > It reaches a black screen with a single row of small grey "windows"
> > > > near the top and the usual twirling blue circle.
> > > >
> > > > As I write I have tried restarting it while holding down the F8 key in
> > > > the hopes of getting into Safe mode.
> > > >
> > > > It is not promising.
> > > >
> > > >
> > >
> > >
> > > It helps if you tell people the brand and model of your computer. Go
> > > find the user manual to figure out how to reset the computer. Some
> > > computers use different key combinations at startup to go into the BIOS.
> > >
> > >
> > My windows 10 is a virtual machine running on VirtualBox.
> >
> > Anyway I got in via Safe Mode and closed down before trying again.
> > That started a cycle of BSODs and reboots with no improvement.
> > Thr reboots start assoon as i enter my PIN.
> >
> > Eventually I found out how to stop the automatic reboots.
> >
> > I am now going to see what happens now. :)
> >
> Well I have had two normal reboots and it now seems stable.
>
> You know, what really pisses me off is that Microsoft can jump to a

Well it now runs for a while but eventually BSODs.

I have been running Microsft's OSs since they first arrived.
But when Windows 98 arrived, all my firm's computers would crash from
between 10 and 20 times a day. Then I was introduced to Linux and usd
it for a vcentrealb server. We had been operating peer to peer up to
then. It was so stable I wanted to use it everywhere but most
professional software is only compilerd for Windows.

Luckily I found Win4lin, a hypevisor. that sported Windows 98 as a
guest. From that moment on, no more crashes. When Windows 95 arrived
Win4lin couldn't handle it but by that time VMware and VirtualBox were
coming over the horizon.

All my data is stored on the Linux host and accessible by both Linux
and Windows. Windows XP is a second virtual machine that has never
given trouble.

I am sticking with virtual Windows machines.

Thanks for the advice.

Regards, Alan

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:

>On 7/3/23 12:13, this is what pinnerite wrote:
>> You know, what really pisses me off is that Microsoft can jump to a
>> BSOD but cannot display the reason on the screen!
>>
>>
>I always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.

It's also captured in Event Viewer, as well as being visible in apps
such as Nirsoft's BlueScreenView. Both of those methods are especially
handy for people who configure their Windows systems to automatically
reboot when they encounter a BSOD.

Char Jackson <none@none.invalid> wrote:
> On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
>
> >On 7/3/23 12:13, this is what pinnerite wrote:
> >> You know, what really pisses me off is that Microsoft can jump to a
> >> BSOD but cannot display the reason on the screen!
> >>
> >>
> >I always thought the BSOD had a reason down at the bottom. A bit
> >obtuse, maybe too techy but there.
>
> It's also captured in Event Viewer, as well as being visible in apps
> such as Nirsoft's BlueScreenView. Both of those methods are especially
> handy for people who configure their Windows systems to automatically
> reboot when they encounter a BSOD.

Thanks for the heads up! I seemed to remember such a feature, but
didn't find anything about it in my notes.

Can you post *where* that feature (do (not) reboot after a BSOD) is
set? Thanks.

I looked in 'msconfig' ('System Configuration'), especially the 'Boot'
tab, but didn't see anything obvious.

On 7/3/23 02:56, pinnerite wrote:
> Yesterday, following disabling hibernation, I thought I had resolved
> every problem that had been plagfuing me for several weeks.
>
> This morning I cannot get it start up at all.
>
> It reaches a black screen with a single row of small grey "windows"
> near the top and the usual twirling blue circle.
>
> As I write I have tried restarting it while holding down the F8 key in
> the hopes of getting into Safe mode.
>
> It is not promising.
>
>

Hi Pinnerite,

The easy stuff first.

1) pop the power cord out the back and let sit
for 15 minutes. If a laptop, remove eh power
cord and the battery. If the battery is
buried inside, hold the power button down
and count to five really slow

2) if it reboots properly, disable Fast Startup
https://www.makeuseof.com/windows-11-turn-on-or-off-fast-startup/

and reboot again with

<win><R> shutdown /r /f /tr 00

-T

On 7/3/2023 1:12 PM, 😎 Mighty Wannabe ✅ wrote:
> On 7/3/2023 12:13 PM, pinnerite wrote:
>> On Mon, 3 Jul 2023 16:45:31 +0100
>> pinnerite <pinnerite@gmail.com> wrote:
>>
>>> On Mon, 3 Jul 2023 06:22:55 -0400
>>> 😎 Mighty Wannabe ✅ <@.> wrote:
>>>
>>>> On 7/3/2023 5:56 AM, pinnerite wrote:
>>>>> Yesterday, following disabling hibernation, I thought I had resolved
>>>>> every problem that had been plagfuing me for several weeks.
>>>>>
>>>>> This morning I cannot get it start up at all.
>>>>> It reaches a black screen with a single row of small grey "windows"
>>>>> near the top and the usual twirling blue circle.
>>>>>
>>>>> As I write I have tried restarting it while holding down the F8 key in
>>>>> the hopes of getting into Safe mode.
>>>>>
>>>>> It is not promising.
>>>>>
>>>>>
>>>>
>>>> It helps if you tell people the brand and model of your computer. Go
>>>> find the user manual to figure out how to reset the computer. Some
>>>> computers use different key combinations at startup to go into the BIOS.
>>>>
>>>>
>>> My windows 10 is a virtual machine running on VirtualBox.
>>>
>>> Anyway I got in via Safe Mode and closed down before trying again.
>>> That started a cycle of BSODs and reboots with no improvement.
>>> Thr reboots start assoon as i enter my PIN.
>>>
>>> Eventually I found out how to stop the automatic reboots.
>>>
>>> I am now going to see what happens now. :)
>>>
>> Well I have had two normal reboots and it now seems stable.
>>
>> You know, what really pisses me off is that Microsoft can jump to a
>> BSOD but cannot display the reason on the screen!
>>
>>
>
>
> Don't expect a Windows OS running in a virtual box to behave 100% the same as in a real Windows hardware box. Windows computer is so cheap these days, you are wasting your time and torturing yourself with a virtual box.
>

Actually, it can behave exactly the same.

The diff is, VirtualBox and VMWare, being commercial entities, they
include "hardening" in their implementation. They are potentially "meddling"
with bits of it, in the name of science.

If you use QEMU KVM on Linux, that's closer to "raw operation".
You may find, for example, that the "boot balls" on the screen, when
viewed in QEMU KVM, are a bit smoother.

For poor Alan, configuring QEMU is a metric bitch. There are like,
a hundred CPU options for emulated CPUs (and only two of the options are useful!!!).
All sorts of things have to be adjusted. It must have taken me a couple days and
some experiments, before it was "moderately happy".

And the disadvantage of QEMU KVM, is no USB passthru, so Windows 10
can run his Fujitsu cut-sheet scanner. This is why we don't use QEMU KVM.
The number of hosting softwares with USB passthru, is strictly limited.
Then, on top of that, not all use the same arch. VirtualBox uses USB packet
routing, and does not care what kind of device you connect. As far as I
know, Hyper-V on Window as the host, it will passthru a USB flash stick,
but not a USB cut-sheet scanner. It uses "Class based passthru", and not
all classes are supported.

Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
The last copy that "just works".

But I don't want to dissuade Alan. The more experiments, the merrier.
We might discover how to tame the damn thing.

Paul

Frank Slootweg <this@ddress.is.invalid> wrote:

> Can you post *where* that feature (do (not) reboot after a BSOD) is
> set?

C:\Windows\System32\sysdm.cpl
Advanced tab -> Startup and Recovery
Under System Failure, deselect the "Automatically restart" option.

There is where you also configure just how much you want stored in the
dump file. I don't get a lot of BSODs anymore, so I have it set to
"Small memory dump" which copies all of memory into the .dmp file. I
don't need all RAM dumped into a logfile. I've yet been fortunate
enough to not needing to involve an OS programmer to fix a recurring
BSOD, and had to figure it out myself, so most of a large dump is
useless to me. If I ever had to resort to contracting an OS programmer
to analyze a full dump, I'd instead just start over with a fresh install
if restoring to backup images didn't eliminate the cause.

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/varieties-of-kernel-mode-dump-files

Lists the different types of debug levels. For now, a small (mini) dump
is all I will be able to use, anyway. With tools like Nirsoft's
BlueScreenView, it only analyzes minidumps. The tool looks only under
C:\Windows\Minidump for the debug files. When I configure the size of
dump to save, preselected paths are listed.

Small dump -> C:\Windows\Minidump
All other dumps -> C:\Windows\MEMORY.DMP
^^^^^^^^^^___ Actually shown as %SYSTEMROOT%

There's no point for me to save more than the small or mini dump since
anymore is just a waste of drive space. If some tech wants a bigger
dump, I'd have to change the dump settings, like to Complete, and then
reproduce the crash hoping it crashed for the same cause as before.

Just to note, not all crashes will add an event into the Event Viewer
logs, and Windows won't always save a dump file. If it's Windows itself
that crashed, it may never reach the code that records a crash event,
especially if it is a hang instead of a crash.

NirSoft's BlueScreenView tries to help by highlighting where the crash
might've occurred, but I've seen those where the highlighted items are
just the affected drives or sys modules, and something else caused them
to crash. You need to find cause, not the victims.

While I have the option "Write an event to the system log", all that
does is show you an entry in Event Viewer when the OS crashed. You have
to look before that at other events to see what might've caused the
crash, like a critical error with a video driver or game.

In message <20230703105635.2c15f87c85460f8f01fb0679@gmail.com>,
pinnerite <pinnerite@gmail.com> writes
>Yesterday, following disabling hibernation, I thought I had resolved
>every problem that had been plagfuing me for several weeks.
>
>This morning I cannot get it start up at all.
>
>It reaches a black screen with a single row of small grey "windows"
>near the top and the usual twirling blue circle.
<snip>

A belated thought: Could your monitor be non-optimally adjusted, so that
there is more explanatory text that you can't see because it's just
above the visible area of your screen?
--
John Hall "[It was] so steep that at intervals the street broke into steps,
like a person breaking into giggles or hiccups, and then resumed
its sober climb, until it had another fit of steps."
Ursula K Le Guin "The Beginning Place"

VanguardLH <V@nguard.lh> wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
>
> > Can you post *where* that feature (do (not) reboot after a BSOD) is
> > set?
>
> C:\Windows\System32\sysdm.cpl
> Advanced tab -> Startup and Recovery
> Under System Failure, deselect the "Automatically restart" option.

Thanks!

This time I've documented it in my notes. Hopefully I can find it when
I need it again! :-)

BTW, you can still get to the 'System Properties' applet on Windows
11, but doing it via sysdm.cpl is of course much quicker, than taking
the detour via Control Panel or/and Settings! :-)

[...]

On Mon, 3 Jul 2023 18:40:32 -0400
Paul <nospam@needed.invalid> wrote:

//
> Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
> stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
> The last copy that "just works".
>
> But I don't want to dissuade Alan. The more experiments, the merrier.
> We might discover how to tame the damn thing.
>
> Paul

I am using V7 of Virtualbox. (7.0.8) It has a one irritant.

I also run Windows XP under it. It is rock solid.
I don't run more more than one VM at a time for obvious reasons.

Last night I left an update 21H2 running (for the third time).
When I checked this morning I had a BSOD.
After rebooting Win 10 informed me that it was undoing something.
After rebooting again I was able to get some work done.

I finally decided to uninstall anything that was installed prior to the
instability, including the latest updates.

After rebooting it then reported that it was making repairs!

Eventually it came up. I caried on working and then left the machine
alone for a bit. When I got back, another BSOD.

I think I made a mistake in not turning off automatic updates.
Every time I try to uninstall an update Windows reinstalls ut.

Right now it froze and I was forced to reset it.
Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
turn off your computer".

....and then crashed with a BSOD!

So, next to start in Safe Mode. Hold down shift and click start.
An hour later and I still have a black square!

More to follow. :(

Alan

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

On 7/6/2023 9:01 AM, pinnerite wrote:
> On Mon, 3 Jul 2023 18:40:32 -0400
> Paul <nospam@needed.invalid> wrote:
>
> //
>> Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
>> stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
>> The last copy that "just works".
>>
>> But I don't want to dissuade Alan. The more experiments, the merrier.
>> We might discover how to tame the damn thing.
>>
>> Paul
> I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
>
> I also run Windows XP under it. It is rock solid.
> I don't run more more than one VM at a time for obvious reasons.
>
> Last night I left an update 21H2 running (for the third time).
> When I checked this morning I had a BSOD.
> After rebooting Win 10 informed me that it was undoing something.
> After rebooting again I was able to get some work done.
>
> I finally decided to uninstall anything that was installed prior to the
> instability, including the latest updates.
>
> After rebooting it then reported that it was making repairs!
>
> Eventually it came up. I caried on working and then left the machine
> alone for a bit. When I got back, another BSOD.
>
> I think I made a mistake in not turning off automatic updates.
> Every time I try to uninstall an update Windows reinstalls ut.
>
> Right now it froze and I was forced to reset it.
> Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
> turn off your computer".
>
> ...and then crashed with a BSOD!
>
> So, next to start in Safe Mode. Hold down shift and click start.
> An hour later and I still have a black square!
>
> More to follow. :(
>
> Alan
>

You are a masochist. Why don't you just buy a new, cheap Windows box
with the latest legal Windows OS already installed?

On 7/6/2023 9:01 AM, pinnerite wrote:
> On Mon, 3 Jul 2023 18:40:32 -0400
> Paul <nospam@needed.invalid> wrote:
>
> //
>> Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
>> stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
>> The last copy that "just works".
>>
>> But I don't want to dissuade Alan. The more experiments, the merrier.
>> We might discover how to tame the damn thing.
>>
>> Paul
>
> I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
>
> I also run Windows XP under it. It is rock solid.
> I don't run more more than one VM at a time for obvious reasons.
>
> Last night I left an update 21H2 running (for the third time).
> When I checked this morning I had a BSOD.
> After rebooting Win 10 informed me that it was undoing something.
> After rebooting again I was able to get some work done.
>
> I finally decided to uninstall anything that was installed prior to the
> instability, including the latest updates.
>
> After rebooting it then reported that it was making repairs!
>
> Eventually it came up. I caried on working and then left the machine
> alone for a bit. When I got back, another BSOD.
>
> I think I made a mistake in not turning off automatic updates.
> Every time I try to uninstall an update Windows reinstalls ut.
>
> Right now it froze and I was forced to reset it.
> Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
> turn off your computer".
>
> ...and then crashed with a BSOD!
>
> So, next to start in Safe Mode. Hold down shift and click start.
> An hour later and I still have a black square!
>
> More to follow. :(
>
> Alan

In VM land, you boot the Win10 DVD image (.iso) and
use Troubleshooting instead of installing Windows. Select
the Command Prompt window option.

There isn't a particular reason this would be necessary,
but you can do this if you want.

chkdsk /f C:

If you do this, you can verify C: is the OS disk in that environment.

cd /d c: # an explicit, absolute-path-change-directory

dir # list visible files
dir /ah # list hidden files, to make sure you're on an OS partition for C:

DISM /image:c:\ /cleanup-image /revertpendingactions

That last command, says whatever update is in-flight, to reverse it.
Anything which is in the middle of installing, reverts itself.

After you exit the Command Prompt

exit

you should be back in DVD Troubleshooting options and Shut Down
should be an option.

After the VM is shut down, you can go to settings and remove the
DVD in Settings (tell it to not use the ISO).

*******

You could use InControl, to set the OS version to 21H2. That would
be, to prevent 22H2 from coming in. The InControl program can also
release the control, when you're satisfied it is safe for the VM to
proceed. The thing is, W10 21H2 won't be supported forever, and
W10 22H2 may be the last version with support right to the end of
2025.

http://al.howardknight.net/?STYPE=msgid&MSGI=%3Cu7ckf9%2411dkk%241%40dont-email.me%3E

There is also the button to punch, in Settings : Update/Security
and Windows Update settings, to delay updates for seven days.
That might stop minor updates, like a Patch Tuesday.

The program "winver.exe" , tells you what current version and
patch level you're at.

*******

Also, when you have a moment, in your host OS, give me a

inxi -F

copy and paste the output. I want to see what your host has
for hardware.

My Ubuntu has VirtualBox 6.1.38 on it, but I can run a
different version for test. This is the inxi -F on the
Test Machine.

bullwinkle@TUNAFISH:~$ inxi -F
System:
Host: TUNAFISH Kernel: 5.15.0-76-generic x86_64 bits: 64
Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
Machine:
Type: Desktop Mobo: ASUSTeK model: P9X79 v: Rev 1.xx
serial: <superuser required> BIOS: American Megatrends v: 4608
date: 12/24/2013
CPU:
Info: 6-core model: Intel Core i7-4930K bits: 64 type: MT MCP cache:
L2: 1.5 MiB
Speed (MHz): avg: 1720 min/max: 1200/3900 cores: 1: 1240 2: 1974 3: 1896
4: 1269 5: 1753 6: 1262 7: 1808 8: 1912 9: 2036 10: 2310 11: 1279 12: 1903
Graphics:
Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 515.105.01
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
gpu: nvidia resolution: 1280x1024~60Hz
OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
v: 4.6.0 NVIDIA 515.105.01
Audio:
Device-1: Intel C600/X79 series High Definition Audio driver: snd_hda_intel
Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
Device-3: Philips s SAA7164 driver: saa7164
Sound Server-1: ALSA v: k5.15.0-76-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Intel 82579V Gigabit Network driver: e1000e
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 40:16:7e:a8:94:0e
IF-ID-1: virbr0 state: down mac: 52:54:00:fa:0f:51
Drives:
Local Storage: total: 931.51 GiB used: 179.99 GiB (19.3%)
ID-1: /dev/sda vendor: Western Digital model: WD1003FZEX-00K3CA0
size: 931.51 GiB
Partition:
ID-1: / size: 314.18 GiB used: 179.99 GiB (57.3%) fs: ext4 dev: /dev/sda2
Swap:
ID-1: swap-1 type: file size: 1024 MiB used: 0 KiB (0.0%) file: /swapfile
Sensors:
System Temperatures: cpu: 25.0 C mobo: N/A gpu: nvidia temp: 34 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 37%
Info:
Processes: 335 Uptime: 2m Memory: 62.73 GiB used: 1.85 GiB (2.9%)
Shell: Bash inxi: 3.3.13
bullwinkle@TUNAFISH:~$

Paul

On Thu, 6 Jul 2023 10:02:31 -0400
Paul <nospam@needed.invalid> wrote:

> On 7/6/2023 9:01 AM, pinnerite wrote:
> > On Mon, 3 Jul 2023 18:40:32 -0400
> > Paul <nospam@needed.invalid> wrote:
> >
> > //
> >> Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
> >> stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
> >> The last copy that "just works".
> >>
> >> But I don't want to dissuade Alan. The more experiments, the merrier.
> >> We might discover how to tame the damn thing.
> >>
> >> Paul
> >
> > I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
> >
> > I also run Windows XP under it. It is rock solid.
> > I don't run more more than one VM at a time for obvious reasons.
> >
> > Last night I left an update 21H2 running (for the third time).
> > When I checked this morning I had a BSOD.
> > After rebooting Win 10 informed me that it was undoing something.
> > After rebooting again I was able to get some work done.
> >
> > I finally decided to uninstall anything that was installed prior to the
> > instability, including the latest updates.
> >
> > After rebooting it then reported that it was making repairs!
> >
> > Eventually it came up. I caried on working and then left the machine
> > alone for a bit. When I got back, another BSOD.
> >
> > I think I made a mistake in not turning off automatic updates.
> > Every time I try to uninstall an update Windows reinstalls ut.
> >
> > Right now it froze and I was forced to reset it.
> > Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
> > turn off your computer".
> >
> > ...and then crashed with a BSOD!
> >
> > So, next to start in Safe Mode. Hold down shift and click start.
> > An hour later and I still have a black square!
> >
> > More to follow. :(
> >
> > Alan
>
> In VM land, you boot the Win10 DVD image (.iso) and
> use Troubleshooting instead of installing Windows. Select
> the Command Prompt window option.
>
> There isn't a particular reason this would be necessary,
> but you can do this if you want.
>
> chkdsk /f C:
>
> If you do this, you can verify C: is the OS disk in that environment.
>
> cd /d c: # an explicit, absolute-path-change-directory
>
> dir # list visible files
> dir /ah # list hidden files, to make sure you're on an OS partition for C:
>
> DISM /image:c:\ /cleanup-image /revertpendingactions
>
> That last command, says whatever update is in-flight, to reverse it.
> Anything which is in the middle of installing, reverts itself.
>
> After you exit the Command Prompt
>
> exit
>
> you should be back in DVD Troubleshooting options and Shut Down
> should be an option.
>
> After the VM is shut down, you can go to settings and remove the
> DVD in Settings (tell it to not use the ISO).
>
> *******
>
> You could use InControl, to set the OS version to 21H2. That would
> be, to prevent 22H2 from coming in. The InControl program can also
> release the control, when you're satisfied it is safe for the VM to
> proceed. The thing is, W10 21H2 won't be supported forever, and
> W10 22H2 may be the last version with support right to the end of
> 2025.
>
> http://al.howardknight.net/?STYPE=msgid&MSGI=%3Cu7ckf9%2411dkk%241%40dont-email.me%3E
>
> There is also the button to punch, in Settings : Update/Security
> and Windows Update settings, to delay updates for seven days.
> That might stop minor updates, like a Patch Tuesday.
>
> The program "winver.exe" , tells you what current version and
> patch level you're at.
>
> *******
>
> Also, when you have a moment, in your host OS, give me a
>
> inxi -F
>
> copy and paste the output. I want to see what your host has
> for hardware.
>
> My Ubuntu has VirtualBox 6.1.38 on it, but I can run a
> different version for test. This is the inxi -F on the
> Test Machine.
>
> bullwinkle@TUNAFISH:~$ inxi -F
> System:
> Host: TUNAFISH Kernel: 5.15.0-76-generic x86_64 bits: 64
> Desktop: GNOME 42.5 Distro: Ubuntu 22.04.2 LTS (Jammy Jellyfish)
> Machine:
> Type: Desktop Mobo: ASUSTeK model: P9X79 v: Rev 1.xx
> serial: <superuser required> BIOS: American Megatrends v: 4608
> date: 12/24/2013
> CPU:
> Info: 6-core model: Intel Core i7-4930K bits: 64 type: MT MCP cache:
> L2: 1.5 MiB
> Speed (MHz): avg: 1720 min/max: 1200/3900 cores: 1: 1240 2: 1974 3: 1896
> 4: 1269 5: 1753 6: 1262 7: 1808 8: 1912 9: 2036 10: 2310 11: 1279 12: 1903
> Graphics:
> Device-1: NVIDIA GP104 [GeForce GTX 1080] driver: nvidia v: 515.105.01
> Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: nvidia
> gpu: nvidia resolution: 1280x1024~60Hz
> OpenGL: renderer: NVIDIA GeForce GTX 1080/PCIe/SSE2
> v: 4.6.0 NVIDIA 515.105.01
> Audio:
> Device-1: Intel C600/X79 series High Definition Audio driver: snd_hda_intel
> Device-2: NVIDIA GP104 High Definition Audio driver: snd_hda_intel
> Device-3: Philips s SAA7164 driver: saa7164
> Sound Server-1: ALSA v: k5.15.0-76-generic running: yes
> Sound Server-2: PulseAudio v: 15.99.1 running: yes
> Sound Server-3: PipeWire v: 0.3.48 running: yes
> Network:
> Device-1: Intel 82579V Gigabit Network driver: e1000e
> IF: eno1 state: up speed: 1000 Mbps duplex: full mac: 40:16:7e:a8:94:0e
> IF-ID-1: virbr0 state: down mac: 52:54:00:fa:0f:51
> Drives:
> Local Storage: total: 931.51 GiB used: 179.99 GiB (19.3%)
> ID-1: /dev/sda vendor: Western Digital model: WD1003FZEX-00K3CA0
> size: 931.51 GiB
> Partition:
> ID-1: / size: 314.18 GiB used: 179.99 GiB (57.3%) fs: ext4 dev: /dev/sda2
> Swap:
> ID-1: swap-1 type: file size: 1024 MiB used: 0 KiB (0.0%) file: /swapfile
> Sensors:
> System Temperatures: cpu: 25.0 C mobo: N/A gpu: nvidia temp: 34 C
> Fan Speeds (RPM): N/A gpu: nvidia fan: 37%
> Info:
> Processes: 335 Uptime: 2m Memory: 62.73 GiB used: 1.85 GiB (2.9%)
> Shell: Bash inxi: 3.3.13
> bullwinkle@TUNAFISH:~$
>
> Paul

Well, I actually managed to squuze a bit more work out and despite the
crashes, lost no data.

I am going to attempt another Safe Mode in a moment but first, as requested:

alan@albury:~/Documents/Signature_Files$ inxi -F
System:
Host: albury Kernel: 5.15.0-76-generic x86_64 bits: 64
Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera
Machine:
Type: Desktop Mobo: ASUSTeK model: M4A785TD-V EVO v: Rev X.0x
serial: <superuser required> BIOS: American Megatrends v: 2105
date: 07/23/2010
CPU:
Info: quad core model: AMD Phenom II X4 955 bits: 64 type: MCP cache:
L2: 2 MiB
Speed (MHz): avg: 1125 min/max: 800/3200 cores: 1: 800 2: 800 3: 2100
4: 800
Graphics:
Device-1: AMD RV710 [Radeon HD 4350/4550] driver: radeon v: kernel
Device-2: AMD RV710 [Radeon HD 4350/4550] driver: radeon v: kernel
Device-3: SJ-180517-N 1080P Webcam type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.21.1.4 driver: X: loaded: ati,radeon
unloaded: fbdev,modesetting,vesa gpu: radeon resolution: 1: 1920x1080~60Hz
2: 1920x1080~60Hz
OpenGL: renderer: AMD RV710 (DRM 2.50.0 / 5.15.0-76-generic LLVM 15.0.7)
v: 3.3 Mesa 22.2.5-0ubuntu0.1~22.04.3
Audio:
Device-1: AMD SBx00 Azalia driver: snd_hda_intel
Device-2: AMD RV710/730 HDMI Audio [Radeon HD 4000 series]
driver: snd_hda_intel
Device-3: AMD RV710/730 HDMI Audio [Radeon HD 4000 series]
driver: snd_hda_intel
Device-4: Philips s SAA7160 driver: SAA716x Budget
Device-5: SJ-180517-N 1080P Webcam type: USB driver: uvcvideo
Sound Server-1: ALSA v: k5.15.0-76-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
driver: r8169
IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: 90:e6:ba:b9:72:3c
IF-ID-1: vboxnet0 state: down mac: 0a:00:27:00:00:00
Drives:
Local Storage: total: 1.82 TiB used: 1.18 TiB (64.9%)
ID-1: /dev/sda vendor: Seagate model: ST2000DM006-2DM164 size: 1.82 TiB
Partition:
ID-1: / size: 27.39 GiB used: 22.41 GiB (81.8%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 1.74 TiB used: 1.16 TiB (66.5%) fs: ext4 dev: /dev/sda5
Swap:
ID-1: swap-1 type: partition size: 8 GiB used: 1.14 GiB (14.2%)
dev: /dev/sda7
Sensors:
System Temperatures: cpu: 45.0 C mobo: 39.0 C
Fan Speeds (RPM): cpu: 2272 psu: 0 case-1: 2472
GPU: device: radeon temp: 70.0 C device: radeon temp: 63.0 C
Info:
Processes: 282 Uptime: 2d 8h 14m Memory: 15.61 GiB used: 4.87 GiB (31.2%)
Shell: Bash inxi: 3.3.13

On Thu, 6 Jul 2023 09:56:54 -0400
😎 Mighty Wannabe ✅ <@.> wrote:

> On 7/6/2023 9:01 AM, pinnerite wrote:
> > On Mon, 3 Jul 2023 18:40:32 -0400
> > Paul <nospam@needed.invalid> wrote:
> >
> > //
> >> Alan could be using V7 of VirtualBox, whereas I like V5.2 or so, for
> >> stuff that "must work". My second computer, has my "real" copy of VirtualBox on it.
> >> The last copy that "just works".
> >>
> >> But I don't want to dissuade Alan. The more experiments, the merrier.
> >> We might discover how to tame the damn thing.
> >>
> >> Paul
> > I am using V7 of Virtualbox. (7.0.8) It has a one irritant.
> >
> > I also run Windows XP under it. It is rock solid.
> > I don't run more more than one VM at a time for obvious reasons.
> >
> > Last night I left an update 21H2 running (for the third time).
> > When I checked this morning I had a BSOD.
> > After rebooting Win 10 informed me that it was undoing something.
> > After rebooting again I was able to get some work done.
> >
> > I finally decided to uninstall anything that was installed prior to the
> > instability, including the latest updates.
> >
> > After rebooting it then reported that it was making repairs!
> >
> > Eventually it came up. I caried on working and then left the machine
> > alone for a bit. When I got back, another BSOD.
> >
> > I think I made a mistake in not turning off automatic updates.
> > Every time I try to uninstall an update Windows reinstalls ut.
> >
> > Right now it froze and I was forced to reset it.
> > Ot is now happ;lily telling me that it is "Getting Windows ready. Don't
> > turn off your computer".
> >
> > ...and then crashed with a BSOD!
> >
> > So, next to start in Safe Mode. Hold down shift and click start.
> > An hour later and I still have a black square!
> >
> > More to follow. :(
> >
> > Alan
> >
>
>
> You are a masochist. Why don't you just buy a new, cheap Windows box
> with the latest legal Windows OS already installed?
>

Because not everybody wants to change the practises that have survived
20 years and meet my psarticiulsar requirements.

As soon as I can ditch Microsoft, believe me I will.

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

Thanks Paul,

> >
> > chkdsk /f C:

I ran chkdsk twice early on.

> > If you do this, you can verify C: is the OS disk in that environment.
> >
> > cd /d c: # an explicit, absolute-path-change-directory
> >
> > dir # list visible files
> > dir /ah # list hidden files, to make sure you're on an OS partition for C:

The next commands seem to presume that I can access a command line while other user initiated processes are running. I cannot do that while an update is running.
By the way I have managed to stop updates until I eliminate the problem.

> > DISM /image:c:\ /cleanup-image /revertpendingactions
> >
> > That last command, says whatever update is in-flight, to reverse it.
> > Anything which is in the middle of installing, reverts itself.
> >
> > After you exit the Command Prompt
> >

Regards, Alan

--
Linux Mint 21.1 kernel version 5.15.0-75-generic Cinnamon 5.6.8

On 7/6/2023 2:03 PM, pinnerite wrote:
> Thanks Paul,
>
>>>
>>> chkdsk /f C:
>
> I ran chkdsk twice early on.
>
>
>>> If you do this, you can verify C: is the OS disk in that environment.
>>>
>>> cd /d c: # an explicit, absolute-path-change-directory
>>>
>>> dir # list visible files
>>> dir /ah # list hidden files, to make sure you're on an OS partition for C:
>
> The next commands seem to presume that I can access a command line while other user initiated processes are running. I cannot do that while an update is running.
> By the way I have managed to stop updates until I eliminate the problem.
>
>>> DISM /image:c:\ /cleanup-image /revertpendingactions
>>>
>>> That last command, says whatever update is in-flight, to reverse it.
>>> Anything which is in the middle of installing, reverts itself.
>>>
>>> After you exit the Command Prompt
>>>
>
> Regards, Alan
>

To issue this command

DISM /image:c:\ /cleanup-image /revertpendingactions

you were supposed to be booted from the Win10 DVD (by using the ISO, in VBox).

The OS is "at rest" when you issue the command. That's
why you're doing it from a DVD. To give the OS a "whack"
while it is not running or attempting to run. The format
of that command, hints it is an "offline" command. That
is what the "/image:c:\" tells you, is the OS is offline
when the command is issued.

*******

Then, the next time the OS runs, it notices the status change,
that it is supposed to roll back whatever broken thing is crashing.

That command *only* works, if an Update is "in-flight" and
the finishing step of the install (the reboot), is not finishing
the update. If an Update has finished and the machine decides to
crash a day later, that command *does nothing*. That is not
a general maintenance command. It's only to solve repetitive
crashes caused by bad digestion of Patch Tuesday.

The command is not a mentalist. It does not "guess" what is
broken and fix it. None of Microsofts stuff is that
clairvoyant. Considering the complexity, their Upgrade Rollback
logic is pretty good, considering all the challenges it faces.
But many of their other Troubleshooters are just thrown together.
They're not magical.

At one time, Win10 would keep hammering hammering hammering on
the same update. There were Visual Studio Redistributable library
files, it would try to update, the update would fail, it could
manage to do at least three more tries the same day. And it could
do that for days on end. Later, Microsoft added some nuances to
the Windows Update process, so "not every stupid thing would loop".
However, that has to be balanced by their maintenance policy stance - when
a Release is going out of support, they will also try and try to
jam in the supported version, so that the "machine" stays in support.

I wanted to keep you healthy enough, so you could start a Repair Install
once the OS could stand on its own two legs. If the machine now
runs, do a "winver.exe" and see how far it's patched. You can manually
try to update it from a 22H2 ISO (you don't boot the ISO, and while
in the running Win10, you right click the ISO file as presented to
the OS and "mount" it, then run Setup.exe) . Doing the Repair Install,
is not the same details as preparing for a "revertpendingactions".

It could be the VBox Additions are gumming up the works, but
I've never seen any evidence here, that this happens. Considering
all the things VBox adds to an environment, it's amazingly stable
as far as that stuff goes.

It's more likely that a "Hardening" step is messing with it.
And all you have in that case, is the .log files that VBox keeps
from attempted runs.

Your inxi results tell me your RS880 in the chipset is turned off,
and just your two video cards are active. You seem to have access
to most of your RAM, and either the address space on the motherboard
goes past 16GB (and that's how the video cards are not impacting
the reported free RAM), or, the two 4350 video cards have relatively
small VRAM on board. In any case, you have plenty of RAM for
a virtual machine to share.

And the processor appears to be new enough, to be instruction set
compatible. I could find at least one report of a similar processor
succeeded in running Win10 at physical level, which means
the "coreinfo" results must have been OK. The only other weirdness
in modern times, is some browsers now, may be using SSE4 or SSE4.2.
If a browser croaks, that's a potential reason. There was a time,
when SSE2 was all the browser insisted on (for memory block moves).

Paul

On Mon, 03 Jul 2023 14:04:24 -0500
Char Jackson <none@none.invalid> wrote:

> On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
>
> >On 7/3/23 12:13, this is what pinnerite wrote:
> >> You know, what really pisses me off is that Microsoft can jump to a
> >> BSOD but cannot display the reason on the screen!
> >>
> >>
> >I always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
>
> It's also captured in Event Viewer, as well as being visible in apps
> such as Nirsoft's BlueScreenView. Both of those methods are especially
> handy for people who configure their Windows systems to automatically
> reboot when they encounter a BSOD.
>

A kid two doors away told me about the Event Viewer too while his dog
was licking me to death.

Apparently the culpret is VBoxDispD3D.dll

However updates may have taken care of it.
Although my desktop icons have disappeared again (the text remains), it
seems to be stable.

Thanks, Alan

--
Linux Mint 21.2 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On Wed, 12 Jul 2023 15:25:43 +0100
pinnerite <pinnerite@gmail.com> wrote:

> On Mon, 03 Jul 2023 14:04:24 -0500
> Char Jackson <none@none.invalid> wrote:
>
> > On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
> >
> > >On 7/3/23 12:13, this is what pinnerite wrote:
> > >> You know, what really pisses me off is that Microsoft can jump to a
> > >> BSOD but cannot display the reason on the screen!
> > >>
> > >>
> > >I always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
> >
> > It's also captured in Event Viewer, as well as being visible in apps
> > such as Nirsoft's BlueScreenView. Both of those methods are especially
> > handy for people who configure their Windows systems to automatically
> > reboot when they encounter a BSOD.
> >
>
> A kid two doors away told me about the Event Viewer too while his dog
> was licking me to death.
>
> Apparently the culpret is VBoxDispD3D.dll
>
> However updates may have taken care of it.
> Although my desktop icons have disappeared again (the text remains), it
> seems to be stable.
>
> Thanks, Alan

As usual I spoke (wrote) too soon.
Despite setting up shared directories in virtualbox and in samba (belt
and braces), under Windows 10 the shared folders are inaccessible yet
the XP VM has no trouble.

(Except it cannot my cut-sheet scanner any more.

Fortunately the Linux host can.

:(

--
Linux Mint 21.1 kernel version 5.15.0-76-generic Cinnamon 5.6.8

On 7/13/2023 3:56 PM, pinnerite wrote:
> On Wed, 12 Jul 2023 15:25:43 +0100
> pinnerite <pinnerite@gmail.com> wrote:
>
>> On Mon, 03 Jul 2023 14:04:24 -0500
>> Char Jackson <none@none.invalid> wrote:
>>
>>> On Mon, 3 Jul 2023 13:04:51 -0400, Big Al <Bears@invalid.com> wrote:
>>>
>>>> On 7/3/23 12:13, this is what pinnerite wrote:
>>>>> You know, what really pisses me off is that Microsoft can jump to a
>>>>> BSOD but cannot display the reason on the screen!
>>>>>
>>>>>
>>>> I always thought the BSOD had a reason down at the bottom. A bit obtuse, maybe too techy but there.
>>>
>>> It's also captured in Event Viewer, as well as being visible in apps
>>> such as Nirsoft's BlueScreenView. Both of those methods are especially
>>> handy for people who configure their Windows systems to automatically
>>> reboot when they encounter a BSOD.
>>>
>>
>> A kid two doors away told me about the Event Viewer too while his dog
>> was licking me to death.
>>
>> Apparently the culpret is VBoxDispD3D.dll
>>
>> However updates may have taken care of it.
>> Although my desktop icons have disappeared again (the text remains), it
>> seems to be stable.
>>
>> Thanks, Alan
>
> As usual I spoke (wrote) too soon.
> Despite setting up shared directories in virtualbox and in samba (belt
> and braces), under Windows 10 the shared folders are inaccessible yet
> the XP VM has no trouble.
>
> (Except it cannot my cut-sheet scanner any more.
>
> Fortunately the Linux host can.
>
> :(
>

Is your Linux (Host) user account a member of "vboxusers" ?

The Host side of the equation, has this to install:

Oracle_VM_VirtualBox_Extension_Pack-6.1.44.vbox-extpack

While Linux has a "package" that is actually a copy of something
like wget, that accesses the Oracle site for you, I did the procedure
manually, just to make absolutely sure the License dialog appeared,
and everything was done properly. The Synaptic route of installing
vbox-extpack is a bit too "silent" for my taste - the stupid thing
erases the downloaded vbox-extpack when it is finished, which means
the user cannot look in the folder and verify later that they've done
that step.

Double clicking that file, should trigger the virtualbox executable,
to install it. On Linux, DKMS may install that, and part of
that, is installing the equivalent of a USB filter driver.
It seems to finish installation a little too quickly, to be
actual DKMS. I am suspicious of how that is being done.

Inside the Guest, are Guest Additions ISO, which the GUI
places in the virtual optical drive when you select the Guest Additions
option in the GUI of the running Guest.

Together, these enable various features. Like accessing a shared folder
uses Guest Additions, inside the Guest.

The vbox-extpack, wants to allow ordinary users to access
the USB filter driver device, and that's when it needs to
make the Linux user account "alan" a member of "vboxusers" group.
If all of that is successful, in the Guest Settings, you
should see three lines, a line for USB1.1, a line for USB2, a line for USB3.

Your cut-sheet scanner, is likely to only need "USB2" ticked,
and the Guest driver is OHCI/EHCI for the low speed stuff.
If you select USB3, that's XHCI, WindowsXP and Windows7 don't
have an inbox driver for that, W8/W10/W11 do have an inbox ("Class") driver.
Checking that all three USB lines are present in Guest Settings,
then ticking the USB2 box, it should all work, everywhere. Only
something like Win98 would wibble and be broken, with a setup
like that. WinXP+ should be fine using USB2 radio button.

Paul