CSET Database Setup Error

[LorenWagner]

Receive the following error. Have rebooted and uninstalled CSET and reinstalled but still get the same error.

CSET Error.docx

Please advise.

Thanks

[randywoods]

Blog post about this issue: https://blog.nimblepros.com/blogs/sql-server-windows-11-fiasco/

LocalDB log files located here:
C:\Users%USER%\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\

Look for “misaligned log IOs” error message, the root cause is Windows 11 doesn’t behave the same way as Windows 10 with SQL Server LocalDB when it comes to disk sector sizes on modern SSDs.

Potential Fix:

New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"

[LorenWagner]

randywoods - thanks for the quick response. I made the change but still get the error.

CSET Error 2.docx

[randywoods]

If you care to share your logs we could take a look ...

C:\Users%user%\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\INLLocalDb2022

[LorenWagner]

Is the attached what you are looking for? Thank you, Loren Dr. Loren W. Wagner, DIA, CISSP Founder/CEO LJW Cyber Consulting A Certified Veteran Owned Small Business CMMC Registered Practitioner ***@***.*** 419.722.2990 www.ljwconsult.com

…

________________________________ From: Randy Woods ***@***.***> Sent: Thursday, June 12, 2025 12:19 PM To: cisagov/cset ***@***.***> Cc: Loren Wagner ***@***.***>; Author ***@***.***> Subject: Re: [cisagov/cset] CSET Database Setup Error (Issue #4716) [https://avatars.githubusercontent.com/u/43245635?s=20&v=4]randywoods left a comment (cisagov/cset#4716)<#4716 (comment)> If you care to share your logs we could take a look ... C:\Users%user%\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\INLLocalDb2022 — Reply to this email directly, view it on GitHub<#4716 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BTNX3Q6AD52BJ7YPLSNMYZ33DGSARAVCNFSM6AAAAAB7AC2OASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNRXGQ3DGOBRGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[randywoods]

I don't see an attachment on your post. Is there a way to attach it directly to this Github thread?

[LorenWagner]

Sorry, let's try again.

error.log

[Marcus-Goectau]

@LorenWagner Can you also send us a copy of the logs located here?

C:\Users%username%\AppData\Local\DHS\CSET

[jenna-protech]

Not original poster, but I was having this same issue

I used this command mentioned:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095"

I did change the sector size to 4096 based on another post elsewhere who had similar issues, 4095 may still work though

Rebooted my PC

And then deleted and recreated the localDB instance:

sqllocaldb delete INLLocalDB2022
sqllocaldb create INLLocalDB2022

Then tried to start from command line and it worked this time:

sqllocaldb start INLLocalDB2022

I was able to open the CSET program without errors after this

[LorenWagner]

CSET logs

CSET.log
CSET_electron.log

[LorenWagner]

@jenna-protech, thank you for the information. I entered the suggested commands which eliminated the SQL errors. However, now when I run CSET it hangs on "Initializing CSET...". Progress but... Dr. Loren W. Wagner, DIA, CISSP Founder/CEO LJW Cyber Consulting A Certified Veteran Owned Small Business CMMC Registered Practitioner ***@***.*** 419.722.2990 www.ljwconsult.com

…

________________________________ From: jenna-protech ***@***.***> Sent: Monday, June 23, 2025 2:11 PM To: cisagov/cset ***@***.***> Cc: Loren Wagner ***@***.***>; Mention ***@***.***> Subject: Re: [cisagov/cset] CSET Database Setup Error (Issue #4716) [https://avatars.githubusercontent.com/u/217644011?s=20&v=4]jenna-protech left a comment (cisagov/cset#4716)<#4716 (comment)> Not original poster, but I was having this same issue I used this command mentioned: New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\stornvme\Parameters\Device" -Name "ForcedPhysicalSectorSizeInBytes" -PropertyType MultiString -Force -Value "* 4095" I did change the sector size to 4096 based on another post elsewhere who had similar issues, 4095 may still work though Rebooted my PC And then deleted and recreated the localDB instance: sqllocaldb delete INLLocalDB2022 sqllocaldb create INLLocalDB2022 Then tried to start from command line and it worked this time: sqllocaldb start INLLocalDB2022 I was able to open the CSET program without errors after this — Reply to this email directly, view it on GitHub<#4716 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BTNX3QYS3344OGXSU2I4NAL3FA7NHAVCNFSM6AAAAAB7AC2OASVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOJXGQZDENRSGM>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Marcus-Goectau]

@LorenWagner Can you send a new copy of your logs now that the SQL errors are gone?

[LorenWagner]

@Marcus-Goectau as requested
CSET.log
CSET_electron.log

[Marcus-Goectau]

@LorenWagner It looks like the database is now being setup correctly. I do see the application is trying to launch the backend API on and undefined port. I would try reinstalling the application to see if that clears up the issue.

[LorenWagner]

@Marcus-Goectau - Ok, I uninstalled CSET, restarted the system, installed CSET, reentered the SQL commands and it still doesn't get past "Initializing CSET". Including latest logs in case something shows up. Thanks for the help.

CSET.log
CSET_electron.log