Hi All,

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB


Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

Many thanks,

-T

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T <T@invalid.invalid> wrote:

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

I'd look in Event Viewer. Then I'd start Windows in its safe mode to
eliminate all startup program to load QB in a cleaner environment.

QB will freeze after login if the company file exceeds the maximum size.
Pro & Premiere: 250 MB. Enterprise: 1.5 GB. I've also read there is a
limit on vendor, employee, and customer records of 14,500. Also if the
number of DB fragments of 15-19 as critical with 20+ as severe danger.

https://kb.coraltreetech.com/knowledge/woodard-supporting-clients-with-large-files

Besides other suggestions, it mentions how to reduce the size of the QB
file.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/9/23 22:17, VanguardLH wrote:

T <T@invalid.invalid> wrote:

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

I'd look in Event Viewer.

I did. Nothing. :'(

Then I'd start Windows in its safe mode to
eliminate all startup program to load QB in a cleaner environment.

QB won't run in safe mode. I tried.

QB will freeze after login if the company file exceeds the maximum size.
Pro & Premiere: 250 MB. Enterprise: 1.5 GB.

If you leave them alone, they will eventually load.
And it does load fine and run fine on the satellite
computer. So the file is okay.

I have seen customers with several Gig of company files
load. Oh they complained, but they did load, eventually.
The customers get into trouble when they get impatient.
(Yes, I told them to have their accountant archive/reduce
their file size.)

I've also read there is a
limit on vendor, employee, and customer records of 14,500. Also if the number of DB fragments of 15-19 as critical with 20+ as severe danger.

It would show on both computes.

https://kb.coraltreetech.com/knowledge/woodard-supporting-clients-with-large-files

Besides other suggestions, it mentions how to reduce the size of the QB
file.

All the standard stuff is not shaking anything lose.
I even checked SMART. No mal or junkware. chkdsk
came up clean. Disabled the antivirus. (Both
computers have the same anti virus version.)
All the QB updates are installed.

Something is clobbering QB on the main computer.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T24gOC8xMC8yMyAwMToxNCwgVCB3cm90ZToNCj4gT24gOC85LzIzIDIyOjE3LCBWYW5ndWFy ZExIIHdyb3RlOg0KPj4gVCA8VEBpbnZhbGlkLmludmFsaWQ+IHdyb3RlOg0KPj4NCj4+PiBJ IGFtIGdldHRpbmcgbm93aGVyZSB3aXRoIFF1aWNrQm9va3MgKFFCKQ0KPj4+IHRlY2ggc3Vw cG9ydCwgc28gSSB0aG91Z2h0IEknZCBydW4gaXQgYnkNCj4+PiB5b3UgZ3V5cy7CoCBUaGVp ciAiZG9jdG9yIiBwcm9ncmFtIGlzIHVzZWxlc3MuDQo+Pj4gVGhhdCBpcyBhbGwgdGhleSBj b3VsZCBjb21lIHVwIHdpdGguDQo+Pj4NCj4+PiBXaW5kb3dzIDEwIHBybyAyMkgyDQo+Pj4g UUIgZGVza3RvcCBpcyAyMDIzLVI1UCA2NCBiaXQNCj4+PiBDb21wYW55IGZpbGUgaXMgNjAw TUINCj4+Pg0KPj4+IEN1c3RvbWVyIGhhcyB0d28gbGljZW5zZXMuwqAgVGhlIHNhdGVsbGl0 ZSBjb21wdXRlciwNCj4+PiB3aGljaCBpcyBpZGVudGljYWwgdG8gdGhlIFF1aWNrQm9va3Mg KFFCKXNlcnZlciwNCj4+PiBoYXMgbm8gaXNzdWVzLsKgIFNvIG5vdGhpbmcgd3Jvbmcgd2l0 aCB0aGUgY29tcGFueQ0KPj4+IGZpbGUgb3IgdGhlIG5ldHdvcmtpbmcuDQo+Pj4NCj4+PiBP biB0aGUgc2VydmVyIGNvbXB1dGVyLCBRdWlja2Jvb2tzIHdpbGwgZnJlZXplDQo+Pj4gcmFu ZG9tbHkgaW4gYW55IHdpbmRvdy7CoCBUaGUgY3VzdG9tZXIgdXNlcyB0aGUNCj4+PiBUYXNr IE1hbmFnZXIgdG8ga2lsbCBRdWlja2Jvb2tzIGFuZCBzdGFydHMNCj4+PiBvdmVyLsKgIFRo ZXJlIGFyZSBubyBlcnJvciBtZXNzYWdlcy4NCj4+Pg0KPj4+IFRoZSB0aW1lIGlzIGhhcHBl bmVkIHRvIG1lLCB0aGUgUUIgc3BsYXNoIHNjcmVlbg0KPj4+IHRvb2sgZm9yZXZlciB0byBs b2FkIHVwIHRvIHRoZSBsb2dpbiBwYWdlLsKgIFRoZW4NCj4+PiBhZnRlciBsb2cgaW4sIFFC IGZyb3plLsKgwqAgTm90aGluZyBlbHNlIHdhcyBmcm96ZW4NCj4+PiBhbmQgdGhlIGNvbXB1 dGVyIHdhcyBhY3Rpbmcgbm9ybWFsbHksIGV4Y2VwdCBmb3INCj4+PiBRQi7CoCBUaGUgVGFz ayBtYW5hZ2VyIHNob3dlZCBDUFUsIERyaXZlLCBNZW1vcnksDQo+Pj4gYWxsIHZlcnkgbGl0 dGxlIHVzZWQuwqAgRXZlbiB0cmllZCBpdCB3aXRoIHRoZQ0KPj4+IEFudGkgVmlydXMgZGlz YWJsZWQuDQo+Pj4NCj4+PiBJIGhhdmUgZm91bmQgbm90aGluZyB3cm9uZyB3aXRoIHRoZSBv cGVyYXRpbmcNCj4+PiBzeXN0ZW0uwqDCoCBFdmVuIHBhc3NlZCBgc2ZjIC9zY2Fubm93YC4N Cj4+Pg0KPj4+IEVyYXNpbmcgUUIgYW5kIHJlaW5zdGFsbGluZyBkaWQgbm90IGhlbHAuDQo+ Pj4gQW5kIFFCIGlzIG9uIHRoZSBsYXRlc3Qgc2VydmljZSBwYWNrLg0KPj4+DQo+Pj4gSG93 IHdvdWxkIHlvdSBndXlzIHByb2NlZWQgdHJvdWJsZXNob290aW5nIHRoaXM/DQo+Pg0KPj4g SSdkIGxvb2sgaW4gRXZlbnQgVmlld2VyLiANCj4gDQo+IEkgZGlkLsKgIE5vdGhpbmcuIDon KA0KPiANCj4+IFRoZW4gSSdkIHN0YXJ0IFdpbmRvd3MgaW4gaXRzIHNhZmUgbW9kZSB0bw0K Pj4gZWxpbWluYXRlIGFsbCBzdGFydHVwIHByb2dyYW0gdG8gbG9hZCBRQiBpbiBhIGNsZWFu ZXIgZW52aXJvbm1lbnQuDQo+IA0KPiBRQiB3b24ndCBydW4gaW4gc2FmZSBtb2RlLsKgIEkg dHJpZWQuDQo+IA0KPiANCj4+IFFCIHdpbGwgZnJlZXplIGFmdGVyIGxvZ2luIGlmIHRoZSBj b21wYW55IGZpbGUgZXhjZWVkcyB0aGUgbWF4aW11bSBzaXplLg0KPj4gUHJvICYgUHJlbWll cmU6IDI1MCBNQi7CoCBFbnRlcnByaXNlOiAxLjUgR0IuIA0KPiANCj4gSWYgeW91IGxlYXZl IHRoZW0gYWxvbmUsIHRoZXkgd2lsbCBldmVudHVhbGx5IGxvYWQuDQo+IEFuZCBpdCBkb2Vz IGxvYWQgZmluZSBhbmQgcnVuIGZpbmUgb24gdGhlIHNhdGVsbGl0ZQ0KPiBjb21wdXRlci7C oCBTbyB0aGUgZmlsZSBpcyBva2F5Lg0KPiANCj4gSSBoYXZlIHNlZW4gY3VzdG9tZXJzIHdp dGggc2V2ZXJhbCBHaWcgb2YgY29tcGFueSBmaWxlcw0KPiBsb2FkLsKgIE9oIHRoZXkgY29t cGxhaW5lZCwgYnV0IHRoZXkgZGlkIGxvYWQsIGV2ZW50dWFsbHkuDQo+IFRoZSBjdXN0b21l cnMgZ2V0IGludG8gdHJvdWJsZSB3aGVuIHRoZXkgZ2V0IGltcGF0aWVudC4NCj4gKFllcywg SSB0b2xkIHRoZW0gdG8gaGF2ZSB0aGVpciBhY2NvdW50YW50IGFyY2hpdmUvcmVkdWNlDQo+ IHRoZWlyIGZpbGUgc2l6ZS4pDQo+IA0KPiANCj4+IEkndmUgYWxzbyByZWFkIHRoZXJlIGlz IGENCj4+IGxpbWl0IG9uIHZlbmRvciwgZW1wbG95ZWUsIGFuZCBjdXN0b21lciByZWNvcmRz IG9mIDE0LDUwMC7CoCBBbHNvIGlmIHRoZQ0KPj4gbnVtYmVyIG9mIERCIGZyYWdtZW50cyBv ZiAxNS0xOSBhcyBjcml0aWNhbCB3aXRoIDIwKyBhcyBzZXZlcmUgZGFuZ2VyLg0KPiANCj4g SXQgd291bGQgc2hvdyBvbiBib3RoIGNvbXB1dGVzLg0KPiANCj4+IGh0dHBzOi8va2IuY29y YWx0cmVldGVjaC5jb20va25vd2xlZGdlL3dvb2RhcmQtc3VwcG9ydGluZy1jbGllbnRzLXdp dGgtbGFyZ2UtZmlsZXMNCj4+DQo+PiBCZXNpZGVzIG90aGVyIHN1Z2dlc3Rpb25zLCBpdCBt ZW50aW9ucyBob3cgdG8gcmVkdWNlIHRoZSBzaXplIG9mIHRoZSBRQg0KPj4gZmlsZS4NCj4g DQo+IA0KPiBBbGwgdGhlIHN0YW5kYXJkIHN0dWZmIGlzIG5vdCBzaGFraW5nIGFueXRoaW5n IGxvc2UuDQo+IEkgZXZlbiBjaGVja2VkIFNNQVJULsKgIE5vIG1hbCBvciBqdW5rd2FyZS7C oCBjaGtkc2sNCj4gY2FtZSB1cCBjbGVhbi7CoCBEaXNhYmxlZCB0aGUgYW50aXZpcnVzLsKg IChCb3RoDQo+IGNvbXB1dGVycyBoYXZlIHRoZSBzYW1lIGFudGkgdmlydXMgdmVyc2lvbi4p DQo+IEFsbCB0aGUgUUIgdXBkYXRlcyBhcmUgaW5zdGFsbGVkLg0KPiANCj4gU29tZXRoaW5n IGlzIGNsb2JiZXJpbmcgUUIgb24gdGhlIG1haW4gY29tcHV0ZXIuDQoNCg0KSXQgb2NjdXJz IHRvIG1lIHRoYXQgSSBzaG91bGQgZG8gYSBgcHNgIG9uIGJvdGgNCmNvbXB1dGVycyBhbmQg Y29tcGFyaW5nIHdoYXQgaXMgbm90IHJ1bm5pbmcNCm9uIHRoZSBzbGF2ZSB0aGF0IGlzIHJ1 bm5pbmcgb24gdGhlIG1hc3Rlci4NCg0KSXQgY291bGQgYmUgc29tZXRoaW5nIGFzIHN0dXBp ZCBhcyBwcmludCBkcml2ZXJzDQpqYW1taW5nIFFCIHdoZW4gUUIgc3RhcnRzIHVwIGFuZCBp cyByZWFkaW5nIHRoZQ0KcHJpbnQgZHJpdmVycyBmb3IgaW5zdGFsbGVkIHByaW50ZXJzDQoN Cg0KDQo=

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T <T@invalid.invalid> wrote:

On 8/9/23 22:17, VanguardLH wrote:

T <T@invalid.invalid> wrote:

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

I'd look in Event Viewer.

I did. Nothing. :'(

Then I'd start Windows in its safe mode to eliminate all startup
program to load QB in a cleaner environment.

QB won't run in safe mode. I tried.

Did you include networking when choosing safe mode? I would think the
QB client would load even if the network were absent, but there would be
an error in not finding the company file across the network. Presumably
QB automatically reopens the last opened company file.

A trick to open QB without loading the company file is to press and hold
down the Ctrl key when loading QB. Keep the Ctrl key pressed until the
"No Company Open" prompt appears. Then use File -> Open to load the
company file. That way, you can determine if it is QB that is slow to
load, or it's the company file that is slow to open.

Did you log into a Windows account with admin privs when booting into
safe mode?

QB will freeze after login if the company file exceeds the maximum
size. Pro & Premiere: 250 MB. Enterprise: 1.5 GB.

If you leave them alone, they will eventually load.
And it does load fine and run fine on the satellite
computer. So the file is okay.

As noted in the articles that I read about QB taking a long time to log
in, and QB behaving very slowly, has to do with the size of the company
file, not that it won't load.

I have seen customers with several Gig of company files
load. Oh they complained, but they did load, eventually.
The customers get into trouble when they get impatient.
(Yes, I told them to have their accountant archive/reduce
their file size.)

What's the size of the problematic company file?
Is the customer running the Pro or Enterprise edition of QB?

What's the effective (measured) bandwidth between the QB server to
wherever the QB client is running?

I've also read there is a limit on vendor, employee, and customer
records of 14,500. Also if the number of DB fragments of 15-19 as
critical with 20+ as severe danger.

It would show on both computes.

Identical hardware, OS version, and startup programs on both?

Do both hosts have the minimum hardware and software requirements as
noted for whatever version/edition you are running of QB?

Something is clobbering QB on the main computer.

Hence why I mentioned safe mode. Articles I find say QB does run in
safe mode. That only loads essential drivers. Does QB have its own
drivers? If so, you may have to disable all startup programs, reboot
normally to allow all drivers to load, including any for QB, but none of
the startup programs run. Those are just the programs in the Startup
folder, not those under Logon Events. To see all locations where
programs may load on Windows startup, or on Windows login, use
SysInternals AutoRuns.

If QB has drivers to load on Windows startup or login, did you check
Device Mgr (devmgmt.msc) for any errors, like yellow exclamation marks
next to devices?

Is the "doctor" program you mentioned the "QuickBooks Install Diagnostic
Tool"? Did you try their Quickbooks Tool Hub?

https://quickbooks.intuit.com/learn-support/en-us/help-article/login-password/fix-common-problems-errors-quickbooks-desktop-tool/L3Yab5gNN_US_en_US

Have you tried repairing the installation using the installer? Control
Panel (control.exe) -> Programs and Features -> select QuickBooks ->
repair option.

You said QB has the latest updates? When did it get the latest? If
that's when QB started failing to load, restore the QB files (or the
entire computer if nothing else would be lost that is critical in its
present state) back to the prior backup.

Did you check the Windows Firewall (or whatever one you're using) is not blocking network traffic on QB?

Is the QBWUSER.ini file a text file? If so, with QB not running, rename
it. On startup, my guess is you'll have to reconfigure user parameters
in the program. If the .ini file is text, you can get info from the old
file as the new one is created and updated.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 10/08/2023 05:47, T wrote:

How would you guys proceed troubleshooting this?

Have you disabled fast startup? It works and it can fix all your
problems. Try it and let us know. You have been telling us this for over
5 years.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/10/23 07:46, VanguardLH wrote:

T <T@invalid.invalid> wrote:

On 8/9/23 22:17, VanguardLH wrote:

T <T@invalid.invalid> wrote:

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

I'd look in Event Viewer.

I did. Nothing. :'(

Then I'd start Windows in its safe mode to eliminate all startup
program to load QB in a cleaner environment.

QB won't run in safe mode. I tried.

Did you include networking when choosing safe mode? I would think the
QB client would load even if the network were absent, but there would be
an error in not finding the company file across the network. Presumably
QB automatically reopens the last opened company file.

A trick to open QB without loading the company file is to press and hold
down the Ctrl key when loading QB. Keep the Ctrl key pressed until the
"No Company Open" prompt appears. Then use File -> Open to load the
company file. That way, you can determine if it is QB that is slow to
load, or it's the company file that is slow to open.

Did you log into a Windows account with admin privs when booting into
safe mode?

QB will freeze after login if the company file exceeds the maximum
size. Pro & Premiere: 250 MB. Enterprise: 1.5 GB.

If you leave them alone, they will eventually load.
And it does load fine and run fine on the satellite
computer. So the file is okay.

As noted in the articles that I read about QB taking a long time to log
in, and QB behaving very slowly, has to do with the size of the company
file, not that it won't load.

I have seen customers with several Gig of company files
load. Oh they complained, but they did load, eventually.
The customers get into trouble when they get impatient.
(Yes, I told them to have their accountant archive/reduce
their file size.)

What's the size of the problematic company file?
Is the customer running the Pro or Enterprise edition of QB?

What's the effective (measured) bandwidth between the QB server to
wherever the QB client is running?

I've also read there is a limit on vendor, employee, and customer
records of 14,500. Also if the number of DB fragments of 15-19 as
critical with 20+ as severe danger.

It would show on both computes.

Identical hardware, OS version, and startup programs on both?

Do both hosts have the minimum hardware and software requirements as
noted for whatever version/edition you are running of QB?

Something is clobbering QB on the main computer.

Hence why I mentioned safe mode. Articles I find say QB does run in
safe mode. That only loads essential drivers. Does QB have its own
drivers? If so, you may have to disable all startup programs, reboot normally to allow all drivers to load, including any for QB, but none of
the startup programs run. Those are just the programs in the Startup
folder, not those under Logon Events.

I just get a nasty note note being able to run in safe mode.

To see all locations where
programs may load on Windows startup, or on Windows login, use
SysInternals AutoRuns.

LOVE AutoRuns. Use it all the time!

If QB has drivers to load on Windows startup or login, did you check
Device Mgr (devmgmt.msc) for any errors, like yellow exclamation marks
next to devices?

Is the "doctor" program you mentioned the "QuickBooks Install Diagnostic Tool"? Did you try their Quickbooks Tool Hub?

Ya, that is the one. In 28 years of doing this, I have
NEVER had the tool hub EVER fix anything. But,
I did jump through those hoops anyway, even though I
had little faith in it.

https://quickbooks.intuit.com/learn-support/en-us/help-article/login-password/fix-common-problems-errors-quickbooks-desktop-tool/L3Yab5gNN_US_en_US

Have you tried repairing the installation using the installer? Control
Panel (control.exe) -> Programs and Features -> select QuickBooks ->
repair option.

yes.

I also removed QB from appwiz, from the hard drive,
and every instance in the registry

You said QB has the latest updates? When did it get the latest?

I got it from the update utility inside QB.

Also, when I reinstalled , I downloaded the installer with the latest
service already installed. (Get you around having to install bazillions
of service packs one after another and
having the stinker corrupts half way through the updates.)

If
that's when QB started failing to load, restore the QB files (or the
entire computer if nothing else would be lost that is critical in its
present state) back to the prior backup.

Did you check the Windows Firewall (or whatever one you're using) is not blocking network traffic on QB?

The offending computer is the server, so it "shouldn't" affect it. But
I disabled the firewall anyway and also used
ESET's firewall "learning mode", which is a really, really slick
utility. QB is so poorly written that they could be
using a network drive on the local computer. I have seen that before.

Is the QBWUSER.ini file a text file?

Yup, did that. Deleted it several times when QB was
both removed and/or not running.

If so, with QB not running, rename
it. On startup, my guess is you'll have to reconfigure user parameters
in the program. If the .ini file is text, you can get info from the old
file as the new one is created and updated.

The tip off when this is randomly doing to happen
is when the green qb splash screen comes up and takes
forever to go away. Killing QB and restarting and everything goes well.


I have yet to do that PS and compare between the
two computers. Had not had enough time with having
to talk people through their strobe light flashing
screens. I posted a fix over on the W11 group.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

What about the trick mentioned where you load QB *without* reloading the company file that was opened the last time. See if QB will load by
itself. If that works, then have QB load the company file.

The idea is to check if it is a problem with QB loading, or when QB
tries to open the company file.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 8/11/23 19:30, VanguardLH wrote:

What about the trick mentioned where you load QB *without* reloading the company file that was opened the last time. See if QB will load by
itself. If that works, then have QB load the company file.

I use that all the time to determine if the
company file is responsible. I did try it here,
several times.

But the issue is that this is random. It
may work fine five times and poop out on
the fifth.

And I can not find anything wrong with the OS. I am hoping
that the PS comparison solves the issue.

The idea is to check if it is a problem with QB loading, or when QB
tries to open the company file.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T24gOC85LzIzIDIxOjQ3LCBUIHdyb3RlOg0KPiBIaSBBbGwsDQo+IA0KPiBJIGFtIGdldHRp bmcgbm93aGVyZSB3aXRoIFF1aWNrQm9va3MgKFFCKQ0KPiB0ZWNoIHN1cHBvcnQsIHNvIEkg dGhvdWdodCBJJ2QgcnVuIGl0IGJ5DQo+IHlvdSBndXlzLsKgIFRoZWlyICJkb2N0b3IiIHBy b2dyYW0gaXMgdXNlbGVzcy4NCj4gVGhhdCBpcyBhbGwgdGhleSBjb3VsZCBjb21lIHVwIHdp dGguDQo+IA0KPiBXaW5kb3dzIDEwIHBybyAyMkgyDQo+IFFCIGRlc2t0b3AgaXMgMjAyMy1S NVAgNjQgYml0DQo+IENvbXBhbnkgZmlsZSBpcyA2MDBNQg0KPiANCj4gDQo+IEN1c3RvbWVy IGhhcyB0d28gbGljZW5zZXMuwqAgVGhlIHNhdGVsbGl0ZSBjb21wdXRlciwNCj4gd2hpY2gg aXMgaWRlbnRpY2FsIHRvIHRoZSBRdWlja0Jvb2tzIChRQilzZXJ2ZXIsDQo+IGhhcyBubyBp c3N1ZXMuwqAgU28gbm90aGluZyB3cm9uZyB3aXRoIHRoZSBjb21wYW55DQo+IGZpbGUgb3Ig dGhlIG5ldHdvcmtpbmcuDQo+IA0KPiBPbiB0aGUgc2VydmVyIGNvbXB1dGVyLCBRdWlja2Jv b2tzIHdpbGwgZnJlZXplDQo+IHJhbmRvbWx5IGluIGFueSB3aW5kb3cuwqAgVGhlIGN1c3Rv bWVyIHVzZXMgdGhlDQo+IFRhc2sgTWFuYWdlciB0byBraWxsIFF1aWNrYm9va3MgYW5kIHN0 YXJ0cw0KPiBvdmVyLsKgIFRoZXJlIGFyZSBubyBlcnJvciBtZXNzYWdlcy4NCj4gDQo+IFRo ZSB0aW1lIGlzIGhhcHBlbmVkIHRvIG1lLCB0aGUgUUIgc3BsYXNoIHNjcmVlbg0KPiB0b29r IGZvcmV2ZXIgdG8gbG9hZCB1cCB0byB0aGUgbG9naW4gcGFnZS7CoCBUaGVuDQo+IGFmdGVy IGxvZyBpbiwgUUIgZnJvemUuwqDCoCBOb3RoaW5nIGVsc2Ugd2FzIGZyb3plbg0KPiBhbmQg dGhlIGNvbXB1dGVyIHdhcyBhY3Rpbmcgbm9ybWFsbHksIGV4Y2VwdCBmb3INCj4gUUIuwqAg VGhlIFRhc2sgbWFuYWdlciBzaG93ZWQgQ1BVLCBEcml2ZSwgTWVtb3J5LA0KPiBhbGwgdmVy eSBsaXR0bGUgdXNlZC7CoCBFdmVuIHRyaWVkIGl0IHdpdGggdGhlDQo+IEFudGkgVmlydXMg ZGlzYWJsZWQuDQo+IA0KPiBJIGhhdmUgZm91bmQgbm90aGluZyB3cm9uZyB3aXRoIHRoZSBv cGVyYXRpbmcNCj4gc3lzdGVtLsKgwqAgRXZlbiBwYXNzZWQgYHNmYyAvc2Nhbm5vd2AuDQo+ IA0KPiBFcmFzaW5nIFFCIGFuZCByZWluc3RhbGxpbmcgZGlkIG5vdCBoZWxwLg0KPiBBbmQg UUIgaXMgb24gdGhlIGxhdGVzdCBzZXJ2aWNlIHBhY2suDQo+IA0KPiBIb3cgd291bGQgeW91 IGd1eXMgcHJvY2VlZCB0cm91Ymxlc2hvb3RpbmcgdGhpcz8NCj4gDQo+IE1hbnkgdGhhbmtz LA0KPiANCj4gLVQNCg0KRm9sbG93IHVwLg0KDQoNCg0KSGkgR3V5cywNCg0KSXQgYWJvdXQg a2lsbGVkIG1lLCBidXQgSSBmaW5hbGx5IGZpeGVkIGl0Lg0KDQpJIGNvbXBhcmVkIGFsbCB0 aGUgcnVubmluZyBwcm9jZXNzZXMgb24gdGhlDQpzZXJ2ZXIgYWdhaW5zdCB0aGUgc2F0ZWxs aXRlLiBJIGZvdW5kIGFib3V0DQpzZXZlbiB0aGF0IHNob3VsZCBub3QgYmUgcnVubmluZyBv biB0aGUgc2VydmVyDQphbmQgcmVtb3ZlZCB0aGVtLiBUaGVuIEkgcmFuIEludGVs4oCZcyBk cml2ZXINCnVwZGF0ZSB1dGlsaXR5IGFuZCBpdCB1cGRhdGVkIHRoZSB2aWRlbw0KZHJpdmVy LiBUaGVuIEkgcmFuIFNVTW8gYW5kIHVwZGF0ZWQgZXZlcnkNCmxhc3QgcHJvZ3JhbS4NCg0K Q3VzdG9tZXIgd3JvdGUgbWUgdmVyeSBwbGVhc2VkLg0KDQpTbyBiYXNpY2FsbHksIHNvbWV0 aGluZyBvciBzb21ldGhpbmdzIGludGVyYWN0ZWQNCndpdGggUXVpY2tCb29rcyBhbmQgY2F1 c2UgUUIgdG8gZnJlZXplLiBJdCBpcw0KcHJvYmFibHkgYSBidWcgaW4gUUIgYXMgbm8gb3Ro ZXIgcHJvZ3JhbQ0KZXhwZXJpZW5jZWQgYW4gaXNzdWUuIEJ1dCBsb2NhdGluZyB0aGUgYnVn IGlzDQphbG1vc3QgaW1wb3NzaWJsZSB0byBkby4gU28gSSBhbSBqdXN0IGdsYWQgUUINCmlz IG5vdyBydW5uaW5nIGFuZCBub3QgY3Jhc2hpbmcuDQoNClRoYW5rIHlvdSBmb3IgYWxsIHRo ZSBoZWxwLA0KLVQNCg0KDQo=

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T <T@invalid.invalid> wrote:

On 8/9/23 21:47, T wrote:

Hi All,

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys.  Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses.  The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues.  So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window.  The customer uses the
Task Manager to kill Quickbooks and starts
over.  There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page.  Then
after log in, QB froze.   Nothing else was frozen
and the computer was acting normally, except for
QB.  The Task manager showed CPU, Drive, Memory,
all very little used.  Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system.   Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

Many thanks,

-T

Follow up.

Hi Guys,

It about killed me, but I finally fixed it.

I compared all the running processes on the
server against the satellite. I found about
seven that should not be running on the server
and removed them. Then I ran Intel¢s driver
update utility and it updated the video
driver. Then I ran SUMo and updated every
last program.

Customer wrote me very pleased.

So basically, something or somethings interacted
with QuickBooks and cause QB to freeze. It is
probably a bug in QB as no other program
experienced an issue. But locating the bug is
almost impossible to do. So I am just glad QB
is now running and not crashing.

Thank you for all the help,
-T

Safe mode, as suggested, didn't [temporarily] get rid of the superfluous processes?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T24gOC8yNS8yMyAxMDo1NSwgVmFuZ3VhcmRMSCB3cm90ZToNCj4gVCA8VEBpbnZhbGlkLmlu dmFsaWQ+IHdyb3RlOg0KPiANCj4+IE9uIDgvOS8yMyAyMTo0NywgVCB3cm90ZToNCj4+PiBI aSBBbGwsDQo+Pj4NCj4+PiBJIGFtIGdldHRpbmcgbm93aGVyZSB3aXRoIFF1aWNrQm9va3Mg KFFCKQ0KPj4+IHRlY2ggc3VwcG9ydCwgc28gSSB0aG91Z2h0IEknZCBydW4gaXQgYnkNCj4+ PiB5b3UgZ3V5cy7CoCBUaGVpciAiZG9jdG9yIiBwcm9ncmFtIGlzIHVzZWxlc3MuDQo+Pj4g VGhhdCBpcyBhbGwgdGhleSBjb3VsZCBjb21lIHVwIHdpdGguDQo+Pj4NCj4+PiBXaW5kb3dz IDEwIHBybyAyMkgyDQo+Pj4gUUIgZGVza3RvcCBpcyAyMDIzLVI1UCA2NCBiaXQNCj4+PiBD b21wYW55IGZpbGUgaXMgNjAwTUINCj4+Pg0KPj4+IEN1c3RvbWVyIGhhcyB0d28gbGljZW5z ZXMuwqAgVGhlIHNhdGVsbGl0ZSBjb21wdXRlciwNCj4+PiB3aGljaCBpcyBpZGVudGljYWwg dG8gdGhlIFF1aWNrQm9va3MgKFFCKXNlcnZlciwNCj4+PiBoYXMgbm8gaXNzdWVzLsKgIFNv IG5vdGhpbmcgd3Jvbmcgd2l0aCB0aGUgY29tcGFueQ0KPj4+IGZpbGUgb3IgdGhlIG5ldHdv cmtpbmcuDQo+Pj4NCj4+PiBPbiB0aGUgc2VydmVyIGNvbXB1dGVyLCBRdWlja2Jvb2tzIHdp bGwgZnJlZXplDQo+Pj4gcmFuZG9tbHkgaW4gYW55IHdpbmRvdy7CoCBUaGUgY3VzdG9tZXIg dXNlcyB0aGUNCj4+PiBUYXNrIE1hbmFnZXIgdG8ga2lsbCBRdWlja2Jvb2tzIGFuZCBzdGFy dHMNCj4+PiBvdmVyLsKgIFRoZXJlIGFyZSBubyBlcnJvciBtZXNzYWdlcy4NCj4+Pg0KPj4+ IFRoZSB0aW1lIGlzIGhhcHBlbmVkIHRvIG1lLCB0aGUgUUIgc3BsYXNoIHNjcmVlbg0KPj4+ IHRvb2sgZm9yZXZlciB0byBsb2FkIHVwIHRvIHRoZSBsb2dpbiBwYWdlLsKgIFRoZW4NCj4+ PiBhZnRlciBsb2cgaW4sIFFCIGZyb3plLsKgwqAgTm90aGluZyBlbHNlIHdhcyBmcm96ZW4N Cj4+PiBhbmQgdGhlIGNvbXB1dGVyIHdhcyBhY3Rpbmcgbm9ybWFsbHksIGV4Y2VwdCBmb3IN Cj4+PiBRQi7CoCBUaGUgVGFzayBtYW5hZ2VyIHNob3dlZCBDUFUsIERyaXZlLCBNZW1vcnks DQo+Pj4gYWxsIHZlcnkgbGl0dGxlIHVzZWQuwqAgRXZlbiB0cmllZCBpdCB3aXRoIHRoZQ0K Pj4+IEFudGkgVmlydXMgZGlzYWJsZWQuDQo+Pj4NCj4+PiBJIGhhdmUgZm91bmQgbm90aGlu ZyB3cm9uZyB3aXRoIHRoZSBvcGVyYXRpbmcNCj4+PiBzeXN0ZW0uwqDCoCBFdmVuIHBhc3Nl ZCBgc2ZjIC9zY2Fubm93YC4NCj4+Pg0KPj4+IEVyYXNpbmcgUUIgYW5kIHJlaW5zdGFsbGlu ZyBkaWQgbm90IGhlbHAuDQo+Pj4gQW5kIFFCIGlzIG9uIHRoZSBsYXRlc3Qgc2VydmljZSBw YWNrLg0KPj4+DQo+Pj4gSG93IHdvdWxkIHlvdSBndXlzIHByb2NlZWQgdHJvdWJsZXNob290 aW5nIHRoaXM/DQo+Pj4NCj4+PiBNYW55IHRoYW5rcywNCj4+Pg0KPj4+IC1UDQo+Pg0KPj4g Rm9sbG93IHVwLg0KPj4NCj4+IEhpIEd1eXMsDQo+Pg0KPj4gSXQgYWJvdXQga2lsbGVkIG1l LCBidXQgSSBmaW5hbGx5IGZpeGVkIGl0Lg0KPj4NCj4+IEkgY29tcGFyZWQgYWxsIHRoZSBy dW5uaW5nIHByb2Nlc3NlcyBvbiB0aGUNCj4+IHNlcnZlciBhZ2FpbnN0IHRoZSBzYXRlbGxp dGUuIEkgZm91bmQgYWJvdXQNCj4+IHNldmVuIHRoYXQgc2hvdWxkIG5vdCBiZSBydW5uaW5n IG9uIHRoZSBzZXJ2ZXINCj4+IGFuZCByZW1vdmVkIHRoZW0uIFRoZW4gSSByYW4gSW50ZWzi gJlzIGRyaXZlcg0KPj4gdXBkYXRlIHV0aWxpdHkgYW5kIGl0IHVwZGF0ZWQgdGhlIHZpZGVv DQo+PiBkcml2ZXIuIFRoZW4gSSByYW4gU1VNbyBhbmQgdXBkYXRlZCBldmVyeQ0KPj4gbGFz dCBwcm9ncmFtLg0KPj4NCj4+IEN1c3RvbWVyIHdyb3RlIG1lIHZlcnkgcGxlYXNlZC4NCj4+ DQo+PiBTbyBiYXNpY2FsbHksIHNvbWV0aGluZyBvciBzb21ldGhpbmdzIGludGVyYWN0ZWQN Cj4+IHdpdGggUXVpY2tCb29rcyBhbmQgY2F1c2UgUUIgdG8gZnJlZXplLiBJdCBpcw0KPj4g cHJvYmFibHkgYSBidWcgaW4gUUIgYXMgbm8gb3RoZXIgcHJvZ3JhbQ0KPj4gZXhwZXJpZW5j ZWQgYW4gaXNzdWUuIEJ1dCBsb2NhdGluZyB0aGUgYnVnIGlzDQo+PiBhbG1vc3QgaW1wb3Nz aWJsZSB0byBkby4gU28gSSBhbSBqdXN0IGdsYWQgUUINCj4+IGlzIG5vdyBydW5uaW5nIGFu ZCBub3QgY3Jhc2hpbmcuDQo+Pg0KPj4gVGhhbmsgeW91IGZvciBhbGwgdGhlIGhlbHAsDQo+ PiAtVA0KPiANCj4gU2FmZSBtb2RlLCBhcyBzdWdnZXN0ZWQsIGRpZG4ndCBbdGVtcG9yYXJp bHldIGdldCByaWQgb2YgdGhlIHN1cGVyZmx1b3VzDQo+IHByb2Nlc3Nlcz8NCg0KUUIsIGRl c3BpdGUgd2hhdCBJIHdhcyB0b2xkIGFib3V0IHNhZmUgbW9kZSwgd291bGQNCm5vdCBydW4g aW4gc2FmZSBtb2RlLg0KDQpJbnRlcmVzdGluZywgb25lIG9mIHRoZSBwcm9jZXNzZXMgd2Fz IGEgcHJvZ3JhbQ0KZnJvbSBTYW1zdW5nJ3MgbWlncmF0aW9uIHV0aWxpdHkuICBJJ2QgYXBw YXJlbnRseQ0KdXNlZCBpdCB5ZWFycyBhZ28gdG8gdXBncmFkZSBhIGRyaXZlLiAgSXQgd2Fz DQpzdGlsbCBydW5uaW5nLiAgQnV0IGl0IHdhcyBub3QgaW4gQXV0b1J1bnMgb3INClByb2dy YW1zIGFuZCBGZWF0dXJlcy4gIEFwcGFyZW50bHksIEkgaGFkIHRob3VnaHQNCkknZCByZW1v dmVkIGl0IGluIHRoZSBwYXN0LiAgV2hlbiBJIHdlbnQgdG8gdGhlDQpmaWxlIG9uIHRoZSBk cml2ZSwgYm90aCB3aXRoIHRoZSBGaWxlIE1hbmFnZXIgYW5kDQp0aGUgQWRtaW4gY29tbWFu ZCBsaW5lLCBpdCB3b3VsZCBub3QgbGV0IG1lIHJlbW92ZQ0KaXQgZHVlIHRvIGEgZmlsZSBs b2NrIHNvbWV3aGVyZSBpdCBkaWQgbm90IHN0YXRlLg0KU28gSSB1c2VkIFRhc2sgTWFuYWdl ciB0byBraWxsIHRoZSBwcm9jZXNzIGFuZA0KIm1hZ2ljYWxseSIgYm90aCB0aGUgZmlsZSBh bmQgdGhlIGRpcmVjdG9yeSBpdA0KcmVzaWRlZCBpbiBkaXNhcHBlYXJlZC4gIFRoYXQgd2Fz IGEgbmV3IG9uZQ0Kb24gbWUhDQo=

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Bill Bradshaw wrote:

T wrote:

On 8/25/23 10:55, VanguardLH wrote:

T <T@invalid.invalid> wrote:

On 8/9/23 21:47, T wrote:

Hi All,

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

I came across this in some of todays computer news:

For three days, system administrators have been troubleshooting
errors that have prevented Windows users from running applications
such as QuickBooks and Avatax. We now know the cause: an unannounced
move or glitch by Microsoft that removed a once-widely used digital certificate in Windows. The removed credential is known as a root certificate, meaning it anchors the trust of hundreds or thousands of intermediate and individual certificates downstream. The root certificate-with the serial number 18dad19e267de8bb4a2158cdcc6b3b4a
and the SHA1 fingerprint 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5-was
no longer trusted in Windows. Because that root was tied to
certificates that certify their authenticity and trust, people trying
to use or install the app received the error.
Just minutes before this post was scheduled to go live, researchers
learned that the certificate had been restored in Windows. It's
unclear how or why that occurred. The certificate immediately below
this paragraph shows the certificate's status on Thursday. The one
below that shows the status as of Friday.

There is more to the article. I have no URL for it. Maybe you can
find it.

Try this:

https://arstechnica.com/?p=1963549#rssowlmlink

<Bill>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Bill Bradshaw wrote:

T wrote:

On 8/25/23 10:55, VanguardLH wrote:

T <T@invalid.invalid> wrote:

On 8/9/23 21:47, T wrote:

Hi All,

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

I came across this in some of todays computer news:

For three days, system administrators have been troubleshooting
errors that have prevented Windows users from running applications
such as QuickBooks and Avatax. We now know the cause: an unannounced
move or glitch by Microsoft that removed a once-widely used digital certificate in Windows. The removed credential is known as a root certificate, meaning it anchors the trust of hundreds or thousands of intermediate and individual certificates downstream. The root certificate-with the serial number 18dad19e267de8bb4a2158cdcc6b3b4a
and the SHA1 fingerprint 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5-was
no longer trusted in Windows. Because that root was tied to
certificates that certify their authenticity and trust, people trying
to use or install the app received the error.
Just minutes before this post was scheduled to go live, researchers
learned that the certificate had been restored in Windows. It's
unclear how or why that occurred. The certificate immediately below
this paragraph shows the certificate's status on Thursday. The one
below that shows the status as of Friday.

There is more to the article. I have no URL for it. Maybe you can
find it.

Try this:

https://arstechnica.com/?p=1963549#rssowlmlink

<Bill>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

T wrote:

On 8/25/23 10:55, VanguardLH wrote:

T <T@invalid.invalid> wrote:

On 8/9/23 21:47, T wrote:

Hi All,

I am getting nowhere with QuickBooks (QB)
tech support, so I thought I'd run it by
you guys. Their "doctor" program is useless.
That is all they could come up with.

Windows 10 pro 22H2
QB desktop is 2023-R5P 64 bit
Company file is 600MB

Customer has two licenses. The satellite computer,
which is identical to the QuickBooks (QB)server,
has no issues. So nothing wrong with the company
file or the networking.

On the server computer, Quickbooks will freeze
randomly in any window. The customer uses the
Task Manager to kill Quickbooks and starts
over. There are no error messages.

The time is happened to me, the QB splash screen
took forever to load up to the login page. Then
after log in, QB froze. Nothing else was frozen
and the computer was acting normally, except for
QB. The Task manager showed CPU, Drive, Memory,
all very little used. Even tried it with the
Anti Virus disabled.

I have found nothing wrong with the operating
system. Even passed `sfc /scannow`.

Erasing QB and reinstalling did not help.
And QB is on the latest service pack.

How would you guys proceed troubleshooting this?

Many thanks,

-T

Follow up.

Hi Guys,

It about killed me, but I finally fixed it.

I compared all the running processes on the
server against the satellite. I found about
seven that should not be running on the server
and removed them. Then I ran Intel's driver
update utility and it updated the video
driver. Then I ran SUMo and updated every
last program.

Customer wrote me very pleased.

So basically, something or somethings interacted
with QuickBooks and cause QB to freeze. It is
probably a bug in QB as no other program
experienced an issue. But locating the bug is
almost impossible to do. So I am just glad QB
is now running and not crashing.

Thank you for all the help,
-T

Safe mode, as suggested, didn't [temporarily] get rid of the
superfluous processes?

QB, despite what I was told about safe mode, would
not run in safe mode.

Interesting, one of the processes was a program
from Samsung's migration utility. I'd apparently
used it years ago to upgrade a drive. It was
still running. But it was not in AutoRuns or
Programs and Features. Apparently, I had thought
I'd removed it in the past. When I went to the
file on the drive, both with the File Manager and
the Admin command line, it would not let me remove
it due to a file lock somewhere it did not state.
So I used Task Manager to kill the process and
"magically" both the file and the directory it
resided in disappeared. That was a new one
on me!

I came across this in some of todays computer news:

For three days, system administrators have been troubleshooting errors that have prevented Windows users from running applications such as QuickBooks
and Avatax. We now know the cause: an unannounced move or glitch by
Microsoft that removed a once-widely used digital certificate in Windows.
The removed credential is known as a root certificate, meaning it anchors
the trust of hundreds or thousands of intermediate and individual
certificates downstream. The root certificate-with the serial number 18dad19e267de8bb4a2158cdcc6b3b4a and the SHA1 fingerprint 4EB6D578499B1CCF5F581EAD56BE3D9B6744A5E5-was no longer trusted in Windows. Because that root was tied to certificates that certify their authenticity
and trust, people trying to use or install the app received the error.

Just minutes before this post was scheduled to go live, researchers learned that the certificate had been restored in Windows. It's unclear how or why
that occurred. The certificate immediately below this paragraph shows the certificate's status on Thursday. The one below that shows the status as of Friday.

There is more to the article. I have no URL for it. Maybe you can find it.

--
<Bill>

Brought to you from Anchorage, Alaska

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)