On 4/19/2024 1:36 AM, Char Jackson wrote:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

Googling "cbfs6.sys" doesn't raise any alarms, unless I missed it. That driver
seems to be pretty common.

I've confirmed that launching Outlook 2019 triggers the BSOD within about 0-5 seconds. Starting Outlook 2019 in safe mode *does not* trigger the BSOD. Likewise, starting Windows in safe mode and launching OL 2019 *does not* trigger
the BSOD, so that's a big clue, but I'm not seeing much info online about this
particular Stop Code. Microsoft says "This bug check appears very infrequently.", to which I think I agree. <https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x22--file-system>

This guy has the same BSOD, same Stop Code 0x22 FILE_SYSTEM, but a different 'what failed' driver. No problem resolution. <https://answers.microsoft.com/en-us/windows/forum/all/stop-code-file-system/e70ac4f2-1a08-4085-bc09-62c3a25c7d0e>

Poking around the web, I don't see any easy/quick solutions, but I have Macrium
images available, so I rolled back a week. No help. Next, I rolled back to March
1. No Help. I rolled back to February 1. No help. I rolled back to October 13,
2023. No help. Since that's my oldest image and it still has the issue, I brought the system forward and have been running it (without OL 2019) since the
end of March to verify its stability. There have been no further BSOD events since I stopped trying to launch OL 2019.

I guess all of that means that the issue, whatever it is, has been present since
last year, just waiting for me to reboot the system.

Has anyone else seen this issue? Specifically, has anyone else seen Stop Code 0x22 FILE_SYSTEM?

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and knows how to fix it.

Err_6.4.5-Dec2023.exe 0x22
# for hex 0x22 / decimal 34
BTH_ERROR_LMP_RESPONSE_TIMEOUT bthdef.h
FILE_SYSTEM bugcodes.h <===
CR_NEED_RESTART cfgmgr32.h
POLICY_ERRV_GLOBAL_GRP_SUM_FLOW_RATE lpmapi.h
NRC_TOOMANY nb30.h
# /* too many commands outstanding, retry later */
NMERR_PROTOCOL_NOT_ENABLED netmon.h
OLE_ERROR_NOT_OPEN ole.h
# Object is not open for editing */
ERROR_WRONG_DISK winerror.h
# The wrong diskette is in the drive.
# Insert %2 (Volume Serial Number: %3) into drive %1.
LDAP_INVALID_DN_SYNTAX winldap.h
# as an HRESULT: Severity: SUCCESS (0), FACILITY_NULL (0x0), Code 0x22
# for hex 0x22 / decimal 34
ERROR_WRONG_DISK winerror.h
# The wrong diskette is in the drive.
# Insert %2 (Volume Serial Number: %3) into drive %1.
# 10 matches found for "0x22"

The header file is no help whatsoever.

//
// MessageId: FILE_SYSTEM
//
// MessageText:
//
// FILE_SYSTEM
//
#define FILE_SYSTEM ((ULONG)0x00000022L)

//
// MessageId: FAT_FILE_SYSTEM
//
// MessageText:
//
// FAT_FILE_SYSTEM
//
#define FAT_FILE_SYSTEM ((ULONG)0x00000023L)

//
// MessageId: NTFS_FILE_SYSTEM
//
// MessageText:
//
// NTFS_FILE_SYSTEM
//
#define NTFS_FILE_SYSTEM ((ULONG)0x00000024L)

//
// MessageId: NPFS_FILE_SYSTEM
//
// MessageText:
//
// NPFS_FILE_SYSTEM
//
#define NPFS_FILE_SYSTEM ((ULONG)0x00000025L)

//
// MessageId: CDFS_FILE_SYSTEM
//
// MessageText:
//
// CDFS_FILE_SYSTEM
//
#define CDFS_FILE_SYSTEM ((ULONG)0x00000026L)

//
// MessageId: RDR_FILE_SYSTEM
//
// MessageText:
//
// RDR_FILE_SYSTEM
//
#define RDR_FILE_SYSTEM ((ULONG)0x00000027L)

//
// MessageId: CORRUPT_ACCESS_TOKEN
//
// MessageText:
//
// CORRUPT_ACCESS_TOKEN
//
#define CORRUPT_ACCESS_TOKEN ((ULONG)0x00000028L)

*******

Then, the next ones hint that the level this is coming from,
is quite low.

//
// MessageId: DATA_BUS_ERROR
//
// MessageText:
//
// DATA_BUS_ERROR
//
#define DATA_BUS_ERROR ((ULONG)0x0000002EL)

//
// MessageId: INSTRUCTION_BUS_ERROR
//
// MessageText:
//
// INSTRUCTION_BUS_ERROR
//
#define INSTRUCTION_BUS_ERROR ((ULONG)0x0000002FL)

At some point, you can't use printf, sprintf, fprintf. It's not
allowed at driver level. Fitting a large integer into a register
should work.

OK, this article says there would be four large integers besides
the tiny BSOD value. I've actually written code at work, to show
the developers an error code is bubbling up, and printing
the equivalent string from user space would be "really helpful".
You know what kind of look I got. I'm not sure that these parameters
are worth a whole lot. Rubbish.

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x26--cdfs-file-system

When an error is two levels deep, a typical developer prints the top one,
and does not bother with the rest. The BSOD does present them, but
it's "good luck" decoding them. What I tried to show our developers,
is you could actually put a text string next to the number, to save
people having to traverse a file system full of source to find it.

At least, with the "Err_6.4.5.exe" utility, they did try to help us.
I got further than I should have.

This article is devoid of detail, implying there isn't a driver
involved (yet). We're at file system level and "something bad happened".
For example, SCSI drivers are used for "foreign devices" for which
there is no in-box driver. Perhaps a CDB (Control Data Block)
approached the pseudo-SCSI level and it was the wrong size. CDBs
come in sizes up to around 12 bytes or so. After the SCSI layer,
a physical device might be the next layer down.

When you use Imgburn, you are given "sense codes" when the optical drive
has an issue. This involves CDBs and so on.

*******

OK, your incident example picture is helpful.

https://filestore.community.support.microsoft.com/api/images/920aca81-1eaa-44a5-a6a9-52e8074d8f46?upload=true

The helper in that thread, tells us it could be some gaming protection
stuff, a shim of some sort. And a shim, may not "follow the rules" about putting standard values as return codes. that's why we only get
a name. It's a file system. It's a file system of some sort.
It could be custom crypto (TrueCrypt). Something weird like that maybe.
It could be a driver protecting an asset (dongleware).

It may not be reported, if the OS dies before the file systems are
shut down cleanly. It could be an unclean shutdown, plus any details
are lost. That's even if the stack had some provision to load
the thing into Eventvwr.msc.

Paul

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

On Fri, 19 Apr 2024 02:22:46 -0400, Paul <nospam@needed.invalid> wrote:

On 4/19/2024 1:36 AM, Char Jackson wrote:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

Googling "cbfs6.sys" doesn't raise any alarms, unless I missed it. That driver
seems to be pretty common.

I've confirmed that launching Outlook 2019 triggers the BSOD within about 0-5
seconds. Starting Outlook 2019 in safe mode *does not* trigger the BSOD.
Likewise, starting Windows in safe mode and launching OL 2019 *does not* trigger
the BSOD, so that's a big clue, but I'm not seeing much info online about this
particular Stop Code. Microsoft says "This bug check appears very
infrequently.", to which I think I agree.
<https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x22--file-system>

This guy has the same BSOD, same Stop Code 0x22 FILE_SYSTEM, but a different >> 'what failed' driver. No problem resolution.
<https://answers.microsoft.com/en-us/windows/forum/all/stop-code-file-system/e70ac4f2-1a08-4085-bc09-62c3a25c7d0e>

Poking around the web, I don't see any easy/quick solutions, but I have Macrium
images available, so I rolled back a week. No help. Next, I rolled back to March
1. No Help. I rolled back to February 1. No help. I rolled back to October 13,
2023. No help. Since that's my oldest image and it still has the issue, I
brought the system forward and have been running it (without OL 2019) since the
end of March to verify its stability. There have been no further BSOD events >> since I stopped trying to launch OL 2019.

I guess all of that means that the issue, whatever it is, has been present since
last year, just waiting for me to reboot the system.

Has anyone else seen this issue? Specifically, has anyone else seen Stop Code
0x22 FILE_SYSTEM?

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and >> knows how to fix it.

<snipped header file>

The header file is no help whatsoever.

I feel the same way.

<more snip>

Then, the next ones hint that the level this is coming from,
is quite low.

//
// MessageId: DATA_BUS_ERROR
//
// MessageText:
//
// DATA_BUS_ERROR
//
#define DATA_BUS_ERROR ((ULONG)0x0000002EL)

//
// MessageId: INSTRUCTION_BUS_ERROR
//
// MessageText:
//
// INSTRUCTION_BUS_ERROR
//
#define INSTRUCTION_BUS_ERROR ((ULONG)0x0000002FL)

At some point, you can't use printf, sprintf, fprintf. It's not
allowed at driver level. Fitting a large integer into a register
should work.

OK, this article says there would be four large integers besides
the tiny BSOD value. I've actually written code at work, to show
the developers an error code is bubbling up, and printing
the equivalent string from user space would be "really helpful".
You know what kind of look I got. I'm not sure that these parameters
are worth a whole lot. Rubbish.

https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x26--cdfs-file-system

When an error is two levels deep, a typical developer prints the top one,
and does not bother with the rest. The BSOD does present them, but
it's "good luck" decoding them. What I tried to show our developers,
is you could actually put a text string next to the number, to save
people having to traverse a file system full of source to find it.

At least, with the "Err_6.4.5.exe" utility, they did try to help us.
I got further than I should have.

This article is devoid of detail, implying there isn't a driver
involved (yet). We're at file system level and "something bad happened".
For example, SCSI drivers are used for "foreign devices" for which
there is no in-box driver. Perhaps a CDB (Control Data Block)
approached the pseudo-SCSI level and it was the wrong size. CDBs
come in sizes up to around 12 bytes or so. After the SCSI layer,
a physical device might be the next layer down.

When you use Imgburn, you are given "sense codes" when the optical drive
has an issue. This involves CDBs and so on.

*******

OK, your incident example picture is helpful.

https://filestore.community.support.microsoft.com/api/images/920aca81-1eaa-44a5-a6a9-52e8074d8f46?upload=true

The helper in that thread, tells us it could be some gaming protection
stuff, a shim of some sort. And a shim, may not "follow the rules" about >putting standard values as return codes. that's why we only get
a name. It's a file system. It's a file system of some sort.
It could be custom crypto (TrueCrypt). Something weird like that maybe.
It could be a driver protecting an asset (dongleware).

It may not be reported, if the OS dies before the file systems are
shut down cleanly. It could be an unclean shutdown, plus any details
are lost. That's even if the stack had some provision to load
the thing into Eventvwr.msc.

Thanks for the analysis. I didn't take detailed notes on what EventViewer had to
say, but as I recall it only had a note about restarting after an unexpected shutdown. I'd have to load a different Macrium image, or just trigger another BSOD, to force a new event entry.

I'm not sure I see a clear path forward at this point, but I feel like there are
clues available. If it's a filesystem driver or shim, I'm not seeing the relationship to Outlook, specifically. So far, I've found no other program that triggers the BSOD. I also have multiple minidumps that I could dig out of Macrium images, but I've never bothered to learn how to examine those things.


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Newshosting.com - Highest quality at a great p (3:633/280.2@fidonet)

On 4/19/2024 4:15 AM, Char Jackson wrote:

Thanks for the analysis. I didn't take detailed notes on what EventViewer had to
say, but as I recall it only had a note about restarting after an unexpected shutdown. I'd have to load a different Macrium image, or just trigger another BSOD, to force a new event entry.

I'm not sure I see a clear path forward at this point, but I feel like there are
clues available. If it's a filesystem driver or shim, I'm not seeing the relationship to Outlook, specifically. So far, I've found no other program that
triggers the BSOD. I also have multiple minidumps that I could dig out of Macrium images, but I've never bothered to learn how to examine those things.

Microsoft says it's uncommon. Which means they really
do not want to document it. Like give a list of
known culprits.

Was there a driver name on the screen ?

There is supposed to be a driver name in that
tiny print section.

Paul

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Char Jackson wrote on 4/18/24 10:36 PM:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and knows how to fix it.

1. Did you relocate your Outlook profile, *.pst file to another disk,
folder, or partition different than the two possible default locations?
Userprofile\Documents\Outlook Files
or
Userprofile\AppData\Local\Microsoft\Outlook

2. Was Outlook's profile stored on a mounted disk or partition?

Is cbfs6.sys found in \System32\drivers?


Outlook 2019 was bundled with a Office 2019 Home and Business,
Professional, Professional Pro, Professional Pro Plus, etc.

Based on your info(error, *.sys file) it leans to an issue that is not
related to Windows or Office.

But if not tried or considering.
O2K19
a. Has a repair function.
b. Is MSA linked - Install option(For clean or reinstall) available in
your online MSA under Services and Subscriptions\<Products you've purchased>
- the online option(after clicking 'Install) provides additional options
One of those additional options is - Choose a version\Offline installer.
https://account.microsoft.com/services
c. If the answer to question 1 or 2 was 'Yes'
- you might consider placing a copy of the pst file to the default location(recommmend ...\Documents\Outlook Files) and use the Control
Panel item "Mail (Microsoft Outlook) to change the Data File(and
accordingly the Profile) to that same expected default location, then
opening Outlook 2019


--
....w¡ñ§±¤ñ

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: windowsunplugged.com (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Char Jackson <none@none.invalid> wrote:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system
restart, and after the system restarted, I launched Outlook 2019
(among other things) and was promptly greeted by a BSOD, Stop Code
0x22 FILE_SYSTEM. It goes on to say "what failed: cbfs6.sys".

Googling "cbfs6.sys" doesn't raise any alarms, unless I missed it.
That driver seems to be pretty common.

I've confirmed that launching Outlook 2019 triggers the BSOD within
about 0-5 seconds. Starting Outlook 2019 in safe mode *does not*
trigger the BSOD. Likewise, starting Windows in safe mode and
launching OL 2019 *does not* trigger the BSOD, so that's a big clue,
but I'm not seeing much info online about this particular Stop Code. Microsoft says "This bug check appears very infrequently.", to which
I think I agree. <https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x22--file-system>

This guy has the same BSOD, same Stop Code 0x22 FILE_SYSTEM, but a
different 'what failed' driver. No problem resolution. <https://answers.microsoft.com/en-us/windows/forum/all/stop-code-file-system/e70ac4f2-1a08-4085-bc09-62c3a25c7d0e>

Poking around the web, I don't see any easy/quick solutions, but I
have Macrium images available, so I rolled back a week. No help.
Next, I rolled back to March 1. No Help. I rolled back to February 1.
No help. I rolled back to October 13, 2023. No help. Since that's my
oldest image and it still has the issue, I brought the system forward
and have been running it (without OL 2019) since the end of March to
verify its stability. There have been no further BSOD events since I
stopped trying to launch OL 2019.

I guess all of that means that the issue, whatever it is, has been
present since last year, just waiting for me to reboot the system.

Has anyone else seen this issue? Specifically, has anyone else seen
Stop Code 0x22 FILE_SYSTEM?

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and knows how to fix it.

https://www.file.net/process/cbfs6.sys.html https://www.callback.com/cbfsstorage
https://www.callback.com/cbfsconnect/

A search on my host does not find the file. Only the Recycle Bin is
excluded in my voidtools [Search] Everything. I have Outlook 2021 (with
the MS Office 2021 Plus suite), OneDrive, GoogleDrive, and a slew of
other software, but none of it needs that file since it is absent on my
setup.

CBFS (Callback File System) is *not* part of Windows. Doesn't see to be
part of any Microsoft software I've installed nor for other software
I've installed. I'm on Windows 10 Home x64 22H2. I don't have a
Windows 11 setup to search there.

Where you add/remove Windows Features, I didn't see anything like CBFS.
I see forum posts of users complaining about cbfs6.sys when using
Bdrive's Netdrive or Cloudsync. Those are consolidators for cloud
storage where it is made to appear as a local drive. Use anything like
that (by brand or functionality)? Users of RaiDrive that makes the
Google Drive online storage appear in the WSL2 (Windows Subsystem for
Linux) tree say the tree is inaccessible in File Explorer. Got any NAS
storage on your network? I've seen complaints of CBFS with Synology's
NAS devices.

When look in Event Viewer, while cbfs6.sys may be listed as the culprit, something called it, so knowing what calls it would lead to what you
installed that uses it.

Provided you configured Windows to save a dump on a BSOD (provided
enough of Windows is left running, and not hung, to write the dump
file), you can use Nirsoft's BlueScreenView. You only need to configure Windows to save a minidump. Anything bigger is only needed and
understood by driver and OS programmers.

I don't see CBFS is any part of Windows. It is use by 3rd party
software to utilitize custom or virtualized file systems.

Is CBFS listed somewhere under the following registry key?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

On 4/19/2024 9:11 AM, ...w¡ñ§±¤ñ wrote:

Char Jackson wrote on 4/18/24 10:36 PM:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and >> knows how to fix it.

1. Did you relocate your Outlook profile, *.pst file to another disk, folder, or partition different than the two possible default locations?
ÿUserprofile\Documents\Outlook Files
or
ÿUserprofile\AppData\Local\Microsoft\Outlook

2. Was Outlook's profile stored on a mounted disk or partition?

Is cbfs6.sys found in \System32\drivers?

Outlook 2019 was bundled with a Office 2019 Home and Business, Professional, Professional Pro, Professional Pro Plus, etc.

Based on your info(error, *.sys file) it leans to an issue that is not related to Windows or Office.

But if not tried or considering.
O2K19
a. Has a repair function.
b. Is MSA linked - Install option(For clean or reinstall) available in your online MSA under Services and Subscriptions\<Products you've purchased>
ÿ- the online option(after clicking 'Install) provides additional options
One of those additional options is - Choose a version\Offline installer.
ÿhttps://account.microsoft.com/services
c. If the answer to question 1 or 2 was 'Yes'
ÿ- you might consider placing a copy of the pst file to the default location(recommmend ...\Documents\Outlook Files) and use the Control Panel item "Mail (Microsoft Outlook) to change the Data File(and accordingly the Profile) to that same expected default location, then opening Outlook 2019

There is an example of an incident here with the driver.
The idea is it has something to do with virtual file systems,
cloud or gaming.

https://answers.microsoft.com/en-us/windows/forum/all/cbfs6sys-and-ntoskrnlexe-bsod/490cc9b0-81e0-4cb6-be4c-a6586daaa836

There is an evaluation package here, but I couldn't get a
sniff as to what it's packed with. I don't install
stuff like this on a whim. It is a relatively large package
for testing a relatively small driver.

https://callback-file-system.software.informer.com/download/

Paul

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: A noiseless patient Spider (3:633/280.2@fidonet)

Paul wrote on 4/19/24 12:40 PM:

On 4/19/2024 9:11 AM, ...w¡ñ§±¤ñ wrote:

Char Jackson wrote on 4/18/24 10:36 PM:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and
knows how to fix it.

1. Did you relocate your Outlook profile, *.pst file to another disk, folder, or partition different than the two possible default locations?
ÿUserprofile\Documents\Outlook Files
or
ÿUserprofile\AppData\Local\Microsoft\Outlook

2. Was Outlook's profile stored on a mounted disk or partition?

Is cbfs6.sys found in \System32\drivers?


Outlook 2019 was bundled with a Office 2019 Home and Business, Professional, Professional Pro, Professional Pro Plus, etc.

Based on your info(error, *.sys file) it leans to an issue that is not related to Windows or Office.

But if not tried or considering.
O2K19
a. Has a repair function.
b. Is MSA linked - Install option(For clean or reinstall) available in your online MSA under Services and Subscriptions\<Products you've purchased>
ÿ- the online option(after clicking 'Install) provides additional options >> One of those additional options is - Choose a version\Offline installer.
ÿhttps://account.microsoft.com/services
c. If the answer to question 1 or 2 was 'Yes'
ÿ- you might consider placing a copy of the pst file to the default location(recommmend ...\Documents\Outlook Files) and use the Control Panel item "Mail (Microsoft Outlook) to change the Data File(and accordingly the Profile) to that same expected default location, then opening Outlook 2019

There is an example of an incident here with the driver.
The idea is it has something to do with virtual file systems,
cloud or gaming.

https://answers.microsoft.com/en-us/windows/forum/all/cbfs6sys-and-ntoskrnlexe-bsod/490cc9b0-81e0-4cb6-be4c-a6586daaa836

There is an evaluation package here, but I couldn't get a
sniff as to what it's packed with. I don't install
stuff like this on a whim. It is a relatively large package
for testing a relatively small driver.

https://callback-file-system.software.informer.com/download/

Paul

Hi,Paul.
Thanks for the info.
My thinking was specific to the occurrence when launching Outlook 2019.
i.e. if the Profile and its PST file was moved from one of those possible default locations(mounted drive, cloud) the file system jumps through different hoops as well as Outlook 2019 to open the profile/pst file.

--
....w¡ñ§±¤ñ

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: windowsunplugged.com (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

"...w¡ñ§±¤ñ " <winstonmvp@gmail.com> wrote:

Paul wrote on 4/19/24 12:40 PM:

On 4/19/2024 9:11 AM, ...w¡ñ§±¤ñ wrote:

Char Jackson wrote on 4/18/24 10:36 PM:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and
knows how to fix it.

1. Did you relocate your Outlook profile, *.pst file to another disk, folder, or partition different than the two possible default locations?
ÿUserprofile\Documents\Outlook Files
or
ÿUserprofile\AppData\Local\Microsoft\Outlook

2. Was Outlook's profile stored on a mounted disk or partition?

Is cbfs6.sys found in \System32\drivers?


Outlook 2019 was bundled with a Office 2019 Home and Business, Professional, Professional Pro, Professional Pro Plus, etc.

Based on your info(error, *.sys file) it leans to an issue that is not related to Windows or Office.

But if not tried or considering.
O2K19
a. Has a repair function.
b. Is MSA linked - Install option(For clean or reinstall) available in your online MSA under Services and Subscriptions\<Products you've purchased>
ÿ- the online option(after clicking 'Install) provides additional options >>> One of those additional options is - Choose a version\Offline installer. >>> ÿhttps://account.microsoft.com/services
c. If the answer to question 1 or 2 was 'Yes'
ÿ- you might consider placing a copy of the pst file to the default location(recommmend ...\Documents\Outlook Files) and use the Control Panel item "Mail (Microsoft Outlook) to change the Data File(and accordingly the Profile) to that same expected default location, then opening Outlook 2019

There is an example of an incident here with the driver.
The idea is it has something to do with virtual file systems,
cloud or gaming.

https://answers.microsoft.com/en-us/windows/forum/all/cbfs6sys-and-ntoskrnlexe-bsod/490cc9b0-81e0-4cb6-be4c-a6586daaa836

There is an evaluation package here, but I couldn't get a
sniff as to what it's packed with. I don't install
stuff like this on a whim. It is a relatively large package
for testing a relatively small driver.

https://callback-file-system.software.informer.com/download/

Paul

Hi,Paul.
Thanks for the info.
My thinking was specific to the occurrence when launching Outlook 2019. i.e. if the Profile and its PST file was moved from one of those possible default locations(mounted drive, cloud) the file system jumps through different hoops as well as Outlook 2019 to open the profile/pst file.

A warning by Microsoft is to *not* have the message store for Outlook
(any client version) on a networked drive. Outlook was not designed for networked access to its message store (.pst, .msg, .ost, etc) files.
For one problem, those files don't get properly closed when the network connection is closed (crash on either endpoint host, network disconnect
without first closing Outlook, etc).

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Char Jackson <none@none.invalid> wrote:

I don't know where I picked it up, (I mean I don't know which program I installed that brought the driver along), but I tried renaming it so that it wouldn't be found during boot - and the boot failed. Something really wants it
to be there. VanguardLH pointed out that it's not a core Windows file.

Did you try booting into Windows' safe mode? That won't load
non-essential drivers (which usually means those needed to boot Windows
that Microsoft provides).

Some things I point at were cloud storage, virtual drives or file
systems, sync storage. Using anything like that other than MS OneDrive,
Google Drive, and Dropbox (I have those, and with no cbfs6.sys file) and
some NAS storage (I don't use that, either).

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Char Jackson <none@none.invalid> wrote:

On Fri, 19 Apr 2024 14:27:44 -0500, VanguardLH <V@nguard.LH> wrote:

Char Jackson <none@none.invalid> wrote:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system
restart, and after the system restarted, I launched Outlook 2019
(among other things) and was promptly greeted by a BSOD, Stop Code
0x22 FILE_SYSTEM. It goes on to say "what failed: cbfs6.sys".

Googling "cbfs6.sys" doesn't raise any alarms, unless I missed it.
That driver seems to be pretty common.

I've confirmed that launching Outlook 2019 triggers the BSOD within
about 0-5 seconds. Starting Outlook 2019 in safe mode *does not*
trigger the BSOD. Likewise, starting Windows in safe mode and
launching OL 2019 *does not* trigger the BSOD, so that's a big clue,
but I'm not seeing much info online about this particular Stop Code.
Microsoft says "This bug check appears very infrequently.", to which
I think I agree. <https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x22--file-system>

This guy has the same BSOD, same Stop Code 0x22 FILE_SYSTEM, but a
different 'what failed' driver. No problem resolution.
<https://answers.microsoft.com/en-us/windows/forum/all/stop-code-file-system/e70ac4f2-1a08-4085-bc09-62c3a25c7d0e>

Poking around the web, I don't see any easy/quick solutions, but I
have Macrium images available, so I rolled back a week. No help.
Next, I rolled back to March 1. No Help. I rolled back to February 1.
No help. I rolled back to October 13, 2023. No help. Since that's my
oldest image and it still has the issue, I brought the system forward
and have been running it (without OL 2019) since the end of March to
verify its stability. There have been no further BSOD events since I
stopped trying to launch OL 2019.

I guess all of that means that the issue, whatever it is, has been
present since last year, just waiting for me to reboot the system.

Has anyone else seen this issue? Specifically, has anyone else seen
Stop Code 0x22 FILE_SYSTEM?

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and
knows how to fix it.

https://www.file.net/process/cbfs6.sys.html >>https://www.callback.com/cbfsstorage
https://www.callback.com/cbfsconnect/

A search on my host does not find the file. Only the Recycle Bin is >>excluded in my voidtools [Search] Everything. I have Outlook 2021 (with >>the MS Office 2021 Plus suite), OneDrive, GoogleDrive, and a slew of
other software, but none of it needs that file since it is absent on my >>setup.

CBFS (Callback File System) is *not* part of Windows. Doesn't see to be >>part of any Microsoft software I've installed nor for other software
I've installed. I'm on Windows 10 Home x64 22H2. I don't have a
Windows 11 setup to search there.

Now that you mention it, I agree that cbfs6.sys isn't a core Windows file. I just checked a couple of clean Win 10 VMs and they weren't present.

Where you add/remove Windows Features, I didn't see anything like CBFS.
I see forum posts of users complaining about cbfs6.sys when using
Bdrive's Netdrive or Cloudsync. Those are consolidators for cloud
storage where it is made to appear as a local drive. Use anything like >>that (by brand or functionality)? Users of RaiDrive that makes the
Google Drive online storage appear in the WSL2 (Windows Subsystem for >>Linux) tree say the tree is inaccessible in File Explorer. Got any NAS >>storage on your network? I've seen complaints of CBFS with Synology's
NAS devices.

DropBox and OneDrive. I don't use either of those, but they're present.

When look in Event Viewer, while cbfs6.sys may be listed as the culprit, >>something called it, so knowing what calls it would lead to what you >>installed that uses it.

Provided you configured Windows to save a dump on a BSOD (provided
enough of Windows is left running, and not hung, to write the dump
file), you can use Nirsoft's BlueScreenView. You only need to configure >>Windows to save a minidump. Anything bigger is only needed and
understood by driver and OS programmers.

I have a minidump and I can access at least a dozen more if I dig through Macrium images, and I have BlueScreenView. BSV lists cbfs6.sys as a culprit, but
does it tell me what called that driver?

I don't see CBFS is any part of Windows. It is use by 3rd party
software to utilitize custom or virtualized file systems.

Is CBFS listed somewhere under the following registry key?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider

Yes. I have "cbfs6,RDPNP,LanmanWorkstation,webclient" under HwOrder and Order subkeys.

I assume RDPNP is related to the fact that I access that PC via RDP 99.9999% of
the time.

Ever have the Box Sync client installed, or similar? That client
supports mirror sync of local data to cloud storage, and uses CBFS.

https://support.box.com/hc/en-us/community/posts/19018028785427-BOX-Drive-installs-cbfsconnect2017-sys-which-disables-support-for-Microsoft-s-Bypass-IO-directstorage

Their driver has a slightly different name. However, I suspect a lot of
these sync clients are using a virtual file system, and all are using Callback's CBFS virtual/network drives.

Boxcryptor (cloud storage encryption, https://www.boxcryptor.com/) is
another tool that installs CBFS.

https://www.callback.com/case-study/boxcryptor

What I've found, so far, is CBFS is mostly used by local clients
accessing cloud storage, and implementing some virtual file system
between the OS and the cloud server. Also looks to be used by some
virtual drive products. Callback.com has their CBFS library to use when programming software that uses virtual drives. That is noted in the 3rd
URL I gave at the callback.com web site.

Ever look in Device Manager (devmgmt.msc) to see if there some CBFS or
virtual file/drive device listed there? You may have to elect to "Show
Hidden Devices". If listed, right-click on it to select Uninstall. You
may have to reboot after the uninstall of the device although a hardware
rescan (right-click on computer name, and select "Scan for hardware
changes") may be sufficient.

Is CBFS listed as a service (services.msc)? Although it is a driver,
they could implement a service to facilitate using the driver. If you
ever discover which installed product is using CBFS, likely you'll have
to get a new cbfs*.sys driver to replace a possibly corrupted or
out-of-date one you have. Callback.com mentions CBFS is used for a
virtual file system with their NFS (Network File System) server.
Besides any cloud storage services, do you use any file servers in your
own intranet?

Other than the safe mode Windows startup that I mentioned (did that fail
to boot?), you could try renaming cbfs6.sys to cbfs6.OLD_sys, or move it
out of the C:\Windows\System32\drivers folder (I'm guessing that's where
you'll find it) to elsewhere, and reboot. Then the driver file can't be
found to load it.

Just because it has the name of a well-known driver doesn't mean that
driver came from the well-known source. Could be malware. Malware
often hides behind the name for something known and desirable. Have you
tried running cbfs*.sys through VirusTotal.com? I know you can submit
..exe files to them, but not sure about *.sys driver files.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

On Sat, 20 Apr 2024 00:08:12 -0500, VanguardLH <V@nguard.LH> wrote:

Char Jackson <none@none.invalid> wrote:

I don't know where I picked it up, (I mean I don't know which program I
installed that brought the driver along), but I tried renaming it so that it >> wouldn't be found during boot - and the boot failed. Something really wants it
to be there. VanguardLH pointed out that it's not a core Windows file.

Did you try booting into Windows' safe mode?

I'm fairly sure I tried starting Windows in safe mode, in which case launching Outlook didn't trigger a BSOD.

I'm also fairly sure, with Windows normally booted, that Outlook in safe mode didn't trigger a BSOD.

It's been just over a month now since I did any initial troubleshooting and I really should go back and cover that ground again. Maybe even take written notes
instead of just trying to remember everything. I'm thinking, though, that having
..pst files loaded (when OL is running), where the .pst files are just wherever they happen to be, including mostly on networked drives because they were previously used on another PC, could be contributing, even though it hasn't been
a problem all these years.

That won't load
non-essential drivers (which usually means those needed to boot Windows
that Microsoft provides).

Some things I point at were cloud storage, virtual drives or file
systems, sync storage. Using anything like that other than MS OneDrive, >Google Drive, and Dropbox (I have those, and with no cbfs6.sys file) and
some NAS storage (I don't use that, either).

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Newshosting.com - Highest quality at a great p (3:633/280.2@fidonet)

On Sat, 20 Apr 2024 01:40:05 -0500, VanguardLH <V@nguard.LH> wrote:

Char Jackson <none@none.invalid> wrote:

On Fri, 19 Apr 2024 14:27:44 -0500, VanguardLH <V@nguard.LH> wrote:

Char Jackson <none@none.invalid> wrote:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system
restart, and after the system restarted, I launched Outlook 2019
(among other things) and was promptly greeted by a BSOD, Stop Code
0x22 FILE_SYSTEM. It goes on to say "what failed: cbfs6.sys".

Googling "cbfs6.sys" doesn't raise any alarms, unless I missed it.
That driver seems to be pretty common.

I've confirmed that launching Outlook 2019 triggers the BSOD within
about 0-5 seconds. Starting Outlook 2019 in safe mode *does not*
trigger the BSOD. Likewise, starting Windows in safe mode and
launching OL 2019 *does not* trigger the BSOD, so that's a big clue,
but I'm not seeing much info online about this particular Stop Code.
Microsoft says "This bug check appears very infrequently.", to which
I think I agree. <https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0x22--file-system>

This guy has the same BSOD, same Stop Code 0x22 FILE_SYSTEM, but a
different 'what failed' driver. No problem resolution.
<https://answers.microsoft.com/en-us/windows/forum/all/stop-code-file-system/e70ac4f2-1a08-4085-bc09-62c3a25c7d0e>

Poking around the web, I don't see any easy/quick solutions, but I
have Macrium images available, so I rolled back a week. No help.
Next, I rolled back to March 1. No Help. I rolled back to February 1.
No help. I rolled back to October 13, 2023. No help. Since that's my
oldest image and it still has the issue, I brought the system forward
and have been running it (without OL 2019) since the end of March to
verify its stability. There have been no further BSOD events since I
stopped trying to launch OL 2019.

I guess all of that means that the issue, whatever it is, has been
present since last year, just waiting for me to reboot the system.

Has anyone else seen this issue? Specifically, has anyone else seen
Stop Code 0x22 FILE_SYSTEM?

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and
knows how to fix it.

https://www.file.net/process/cbfs6.sys.html >>>https://www.callback.com/cbfsstorage >>>https://www.callback.com/cbfsconnect/

A search on my host does not find the file. Only the Recycle Bin is >>>excluded in my voidtools [Search] Everything. I have Outlook 2021 (with >>>the MS Office 2021 Plus suite), OneDrive, GoogleDrive, and a slew of >>>other software, but none of it needs that file since it is absent on my >>>setup.

CBFS (Callback File System) is *not* part of Windows. Doesn't see to be >>>part of any Microsoft software I've installed nor for other software
I've installed. I'm on Windows 10 Home x64 22H2. I don't have a
Windows 11 setup to search there.

Now that you mention it, I agree that cbfs6.sys isn't a core Windows file. I >> just checked a couple of clean Win 10 VMs and they weren't present.

Where you add/remove Windows Features, I didn't see anything like CBFS.
I see forum posts of users complaining about cbfs6.sys when using >>>Bdrive's Netdrive or Cloudsync. Those are consolidators for cloud >>>storage where it is made to appear as a local drive. Use anything like >>>that (by brand or functionality)? Users of RaiDrive that makes the >>>Google Drive online storage appear in the WSL2 (Windows Subsystem for >>>Linux) tree say the tree is inaccessible in File Explorer. Got any NAS >>>storage on your network? I've seen complaints of CBFS with Synology's >>>NAS devices.

DropBox and OneDrive. I don't use either of those, but they're present.

When look in Event Viewer, while cbfs6.sys may be listed as the culprit, >>>something called it, so knowing what calls it would lead to what you >>>installed that uses it.

Provided you configured Windows to save a dump on a BSOD (provided
enough of Windows is left running, and not hung, to write the dump
file), you can use Nirsoft's BlueScreenView. You only need to configure >>>Windows to save a minidump. Anything bigger is only needed and >>>understood by driver and OS programmers.

I have a minidump and I can access at least a dozen more if I dig through
Macrium images, and I have BlueScreenView. BSV lists cbfs6.sys as a culprit, but
does it tell me what called that driver?

I don't see CBFS is any part of Windows. It is use by 3rd party
software to utilitize custom or virtualized file systems.

Is CBFS listed somewhere under the following registry key?

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider

Yes. I have "cbfs6,RDPNP,LanmanWorkstation,webclient" under HwOrder and Order
subkeys.

I assume RDPNP is related to the fact that I access that PC via RDP 99.9999% of
the time.

Ever have the Box Sync client installed, or similar? That client
supports mirror sync of local data to cloud storage, and uses CBFS.

I don't think anything like that is installed.

https://support.box.com/hc/en-us/community/posts/19018028785427-BOX-Drive-installs-cbfsconnect2017-sys-which-disables-support-for-Microsoft-s-Bypass-IO-directstorage

Their driver has a slightly different name. However, I suspect a lot of >these sync clients are using a virtual file system, and all are using >Callback's CBFS virtual/network drives.

Boxcryptor (cloud storage encryption, https://www.boxcryptor.com/) is
another tool that installs CBFS.

https://www.callback.com/case-study/boxcryptor

What I've found, so far, is CBFS is mostly used by local clients
accessing cloud storage, and implementing some virtual file system
between the OS and the cloud server. Also looks to be used by some
virtual drive products. Callback.com has their CBFS library to use when >programming software that uses virtual drives. That is noted in the 3rd
URL I gave at the callback.com web site.

Ever look in Device Manager (devmgmt.msc) to see if there some CBFS or >virtual file/drive device listed there? You may have to elect to "Show >Hidden Devices". If listed, right-click on it to select Uninstall. You
may have to reboot after the uninstall of the device although a hardware >rescan (right-click on computer name, and select "Scan for hardware
changes") may be sufficient.

I don't see anything obvious in Device Manager.

Is CBFS listed as a service (services.msc)?

No, I don't see anything like that.

Although it is a driver,
they could implement a service to facilitate using the driver. If you
ever discover which installed product is using CBFS, likely you'll have
to get a new cbfs*.sys driver to replace a possibly corrupted or
out-of-date one you have. Callback.com mentions CBFS is used for a
virtual file system with their NFS (Network File System) server.
Besides any cloud storage services, do you use any file servers in your
own intranet?

That PC hosts the Plex server software, so it has access to my video library so that it can serve up video upon request from other hosts on the LAN. So far, I don't think Plex is involved.

Other than the safe mode Windows startup that I mentioned (did that fail
to boot?)

From memory, I believe Windows safe mode booted fine and Outlook was able to launch without triggering a BSOD. I can see that I'll have to go back and try all of the basic things again, this time taking notes.

you could try renaming cbfs6.sys to cbfs6.OLD_sys, or move it
out of the C:\Windows\System32\drivers folder (I'm guessing that's where >you'll find it) to elsewhere, and reboot. Then the driver file can't be >found to load it.

That was perhaps the very first thing I did. I think I mentioned it. Renaming it
caused Windows startup to hang. That, too, is something I should go back and verify.

Just because it has the name of a well-known driver doesn't mean that
driver came from the well-known source. Could be malware. Malware
often hides behind the name for something known and desirable. Have you >tried running cbfs*.sys through VirusTotal.com? I know you can submit
.exe files to them, but not sure about *.sys driver files.

I submitted cbfs6.sys just now and 0 of 63 security vendors flagged it.


--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Newshosting.com - Highest quality at a great p (3:633/280.2@fidonet)

Char Jackson wrote on 4/19/24 10:13 PM:

On Fri, 19 Apr 2024 06:11:51 -0700, ...w¡ñ§±¤ñ <winstonmvp@gmail.com> wrote:

Char Jackson wrote on 4/18/24 10:36 PM:

Windows 10 22H2 - OS Build 19045.4291

In mid-March, I did my twice-yearly Windows 10 updates and system restart, and
after the system restarted, I launched Outlook 2019 (among other things) and was
promptly greeted by a BSOD, Stop Code 0x22 FILE_SYSTEM. It goes on to say "what
failed: cbfs6.sys".

I've switched over to using Outlook 2016 on my laptop, so it's not vital that I
fix this anytime soon, but I decided to post in case someone has seen it and
knows how to fix it.

1. Did you relocate your Outlook profile, *.pst file to another disk,
folder, or partition different than the two possible default locations?

I've been using various versions of Outlook for what seems like more than 20 years, so I have .pst files in lots of locations, most of which are on networked
drives. That has been fine for many years, but VanguardLH, and now possibly you
as well, are pointing out that .pst files should probably not be on networked drives.

Having said that, I think my main profile .pst is located at C:\Users\<user>\Documents\Outlook Files

The filename there is "Outlook Main.pst", which sounds like an example of my personal naming convention rather than a default name that the program itself provided. The size is 11.25 gigabytes. I vaguely remember that older versions of
Outlook didn't like working with such large files.

I have 2 other .pst files called Outlook.pst and Outlook_2.pst, both of which are on a networked drive. Are those the profile .pst files? Both of those are much smaller, 5GB and 1GB, respectively.

Userprofile\Documents\Outlook Files

Yes, that one. I think. Unless the profile .pst is one of the files on the networked drive.

or
Userprofile\AppData\Local\Microsoft\Outlook

The only .pst in that location is "Internet Calendar Subscriptions.pst"

2. Was Outlook's profile stored on a mounted disk or partition?

As far as I know. Everything worked fine for many years.

Is cbfs6.sys found in \System32\drivers?

Yes, it's there. It's version 6.1.184.118, 451KB, dated 9/21/2016.

Outlook 2019 was bundled with a Office 2019 Home and Business,
Professional, Professional Pro, Professional Pro Plus, etc.

This is a Pro Plus Retail edition. The other major apps in the suite haven't shown any issues, but of course they don't have the equivalent of .pst files scattered everywhere.

Based on your info(error, *.sys file) it leans to an issue that is not
related to Windows or Office.

But if not tried or considering.
O2K19
a. Has a repair function.
b. Is MSA linked - Install option(For clean or reinstall) available in
your online MSA under Services and Subscriptions\<Products you've purchased> >> - the online option(after clicking 'Install) provides additional options >> One of those additional options is - Choose a version\Offline installer.
https://account.microsoft.com/services
c. If the answer to question 1 or 2 was 'Yes'
- you might consider placing a copy of the pst file to the default
location(recommmend ...\Documents\Outlook Files) and use the Control
Panel item "Mail (Microsoft Outlook) to change the Data File(and
accordingly the Profile) to that same expected default location, then
opening Outlook 2019

I have 22 .pst files scattered about, but I assume the profile .pst is one of the three files I mentioned above. I'll try to spend some time on this in the coming day(s). Thanks.

If you open Control Panel and click on the Outlook created cpl item 'Mail (Microsoft Outlook)' a dialog box opens with multiple setup type items:
Setup email accounts and directories
Data files
Profiles

Data Files:
When opened shows the default pst file that outlook opens(it has a
check beside it) and other pst files loaded at when Outlook opens.
The usual default data file(.pst) created is Outlook.pst
- there may be more than one Data *.pst file
=> it could be a renamed previous Outlook.pst file
=> it could, depending how email accounts are setup, a *.pst where the
* is an email username or username.com.
Here's a not so brief overview of what
Outlook does on first use:
#1 - The first POP account configured will have it's PST file
automatically set as the "default data file" and will any include contact/calendar folders
- if an earlier Outlook.pst file is already present(copied from an
earlier system or earlier version of Outlook) in the default
location(e.g. ..Documents\Outlook Files) the first POP3 account will have
the choice of using the Outlook.pst file or create the first pst with the email name.

#2 - For any subsequent POP accounts configured, you will have the option
to use an existing PST file or have Outlook create a new one. Any new PST files will not contain contact/calendar folders.

#3 - Be default, contacts will be created in the default contact folder
(same for calendar)

#4 - Any PST file that has standard Outlook contact/calendar folders in
the folder tree was at one time set as the "default data file" - not necessarily in the current version of Outlook being used but at any point
in its past in any version of Outlook.

#5 - Anytime you set a different PST file as the default data file,
Outlook will automatically add contact/calendar folders to it if those
folders don't exist already.

#6 - Changing which PST file is the "default data file" has no negative connotations - just need to be aware of what that means (see point #3).
You can do that all day long without hurting anything

#7 - The name of the PST file has no impact on the name of the email
account. Outlook just uses the email address as the PST file name when it first creates the file. Can change the name of the file if you wanted to without losing any data. If you did that, Outlook would whine about not
being able to find the old file name and ask to pick the one you want to
use. That's it.

#8 - The "default data file" is separate and distinct from the "default
email account". One doesn't impact the other. What you can't do is remove
an email account from the Outlook profile if it's associated data file
(for any account type) is set as the "default data file".

#9 - Removing a POP account from the profile does not remove it's PST
file. In other words, it continues to show in the Outlook Nav Pane until
you explicitly remove the file from the profile which in turn, does not
delete the file from the system.

10. When setting up an IMAP account, current versions(including 2019,
2016) setup with an *.ost file. But earlier Outlook versions(2013 or
earlier or 2010 and earlier) created or could be configured to use their
own *.pst or the default *.pst file.

Show Profiles
- That is name within the default pst file. It is not the name of the
Data file. When an account is setup, the profile is given the name Outlook.
- One can have multiple profiles, but caution, if you previously
renamed an Outlook.pst file and adds that to the Data file option, when
that pst is opened in Outlook(since it was previously and usually the
earlier default data pst file, it also would have a profile name Outlook.
- if one uses the Show Profiles option 'Add' to create a new profile,
the ability to give it a different name than Outlook is available.


Thus if if you've multiple pst spread out across different locations(main drive, mounted, networked) only one can be the default. If more than
exist, then more than one may have the same profile name(Outlook).

One of the tricks,I learned a long time ago...since I've been using
Outlook since Outlook 97...is when moving/upgrading to a later
Office?Outlook version, always create the Outlook Files folder(in userprofile\Documents\) and place the earlier Outlook.pst file in that
folder ***and always before first use of the newer Outlook version..that
way my main Outlook.pst file contains all the prior contacts and calendar content and subsequently adding any new POP3 account to always choose
that same Outlook.pst file to avoid having multiple emailname.pst files(because email addresses come and go be they isp provided or
free(like GMail) or free or add free or Microsoft 365 subscription(using
an Outlook, MSN, Live, Hotmail)MSA account for the purchase/activation
etc - this way no matter what changes 'Outlook.pst' as the Data file
remains the same and the default. I keep the size of it controlled by Archiving content to a unique name pst file that can be opened if
necessary and cleaning out the trash(no longer needed emails, contacts, calendar content) once or twice a year. My current Outlook.pst data file
in used for all these years is still only 2.5 GB(I've seen some Outlook
pst files on other devices inthe 50-60 GB range and users having no clue
what they don't need - emails, contacts, etc).


I still don't think and agree that Outlook failing to open is directly responsible, but it does mean if those pst files need to be accessed
across multiple locations...that Outlook and the presence of the
cbfs6.sys file may be stepping on each others' toes)

--
....w¡ñ§±¤ñ

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: windowsunplugged.com (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Char Jackson <none@none.invalid> wrote:

That PC hosts the Plex server software, so it has access to my video library so
that it can serve up video upon request from other hosts on the LAN. So far, I
don't think Plex is involved.

Plex. Is that the Plex media server from plex.tv? (https://www.plex.tv/media-server-downloads/)

Some ISPs are throttling connections to Plex considering it to be
distributing pirating software. You should be okay if you're just using
it within your intranet.

Plex is cracking down on pirated content using their service, but it can
take a while to mend a damaged reputation.

https://cordcuttersnews.com/plex-is-cracking-down-on-pirated-content/

I submitted cbfs6.sys just now and 0 of 63 security vendors flagged it.

Unsure from where you could obtain a trustworthy download of just the
CBFS driver if you don't find what installed it in the first place.
Once the culprit software is determined, you'll probably have to
uninstal it, do remnant file and registry cleanup, and a new install to
get the new driver (unless the program offers an auto-update feature,
and offers a new version of the driver file).

Possibly you could use SysInternals ProcMon to monitor who is issuing
calls to the cbfs6.sys driver file, but I'm not sure that would work.
The driver gets loaded into memory. Guess I'd look in the registry to
see what all entries and data items define that driver interface.

Did you did into the file, like using the HxD Editor, or use
SysInternal's strings tool (which you'll probably want to redirect its
stdout to a file to view inside, say, Notepad), to look for strings
inside the file that might lead to which product it is associated?

Aside: I've seen some users report moving from CBSF to WinFSP which is
similar to FUSE (libfuse) from Linux.

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

I've never used the MS Driver verifier (verifier.exe) on drivers. From
what I've read, the legit cbfs6.sys driver is supposed to be signed.
Maybe the verifier will check that. Or maybe you need to use sigverif (https://www.majorgeeks.com/content/page/how_to_verify_if_system_files_and_drivers_are_digitally_signed_in_windows.html)
to check cbfs6.sys is signed.

https://www.hybrid-analysis.com/sample/fd508ac5bf65f632554e7051e6ea8efa16898e630c5c101acdf32af1d8fc1972/5d86ae370288383b35b18bed#mitre-matrix-modal

The sample (cbfs6.sys) was submitted back in 2019. Besides VirusTotal,
try submitting the file to https://www.hybrid-analysis.com/. As to how
much of its report you understand, well, it quickly went over my head.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

Keywords: VanguardLH,VLH

Char Jackson <none@none.invalid> wrote:

I'm fairly sure I tried starting Windows in safe mode, in which case launching Outlook didn't trigger a BSOD.

I'm also fairly sure, with Windows normally booted, that Outlook in
safe mode didn't trigger a BSOD.

Any add-ons installed in Outlook?

Perhaps time to move all those .pst files back to local internal
storage, and retest. Not across a network, and not on removable media.

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: Usenet Elder (3:633/280.2@fidonet)

VanguardLH wrote on 4/20/24 8:06 PM:

Char Jackson <none@none.invalid> wrote:

I'm fairly sure I tried starting Windows in safe mode, in which case
launching Outlook didn't trigger a BSOD.

I'm also fairly sure, with Windows normally booted, that Outlook in
safe mode didn't trigger a BSOD.

Any add-ons installed in Outlook?

Perhaps time to move all those .pst files back to local internal
storage, and retest. Not across a network, and not on removable media.

That could be one route, other possible routes.

If Outlook in normal mode is configured to open multiple pst files, those
same pst should appear in safe mode. The code for opening those
additional pst files exists in the default Outlook profile.
i.e. those additional pst files load on both normal and safe mode.
- Since those pst files are present in safe mode, they can be closed,
the profile updated to exclude those from opening. Once done and safe
mode session closed(exit Outlook), the next instance of Outlook in normal
mode will open with the default profile and the default data file.
=> Note: The default Data file(should be configured to be on the local disk/drive)


--
....w¡ñ§±¤ñ

--- MBSE BBS v1.0.8.4 (Linux-x86_64)
* Origin: windowsunplugged.com (3:633/280.2@fidonet)