Hi, I’ve tried everything from complete reinstall of all components of onyx to cdm commands to manual install of sql 2012… I’ve got no more idea. anyone know how to fix this??
ONYX Install version: 4.8.1239 (Tried 1238 also)
Fresh Windows 11 - All updates till 30.November 2022.
AMD 4800HS
Nvidia 2060 Max Q
16 GB DDR4 3200MHz
Samsung 980 1TB
Onyx worked on this machine before fresh windows install.
Many thanks 
Please go to the file location here:
Download the .vbs file and run it from the command prompt in your windows OS after a reboot of the PC.
Once you run that script, try the uninstall again.
Reinstall ONYX after another reboot.
I’ve tried several time but unsucesfull, same error pops again.
Got any other idea?
Sorry no other idea besides a clean OS install. Some OEM PCs have Windows images that are corrupt (seen it with HP and Lenovo)
Reinstall PC with download from server, which brings in a clean Windows 11 image from Microsoft, not the customized image from the PC manufacturer.
I’ve found error that does this just gotta fix it somehow
2022-12-02 01:15:14.64 Server Microsoft SQL Server 2012 (SP4) (KB4018073) - 11.0.7001.0 (X64)
Aug 15 2017 10:23:29
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.3 (Build 22621: ) (Hypervisor)
2022-12-02 01:15:14.64 Server (c) Microsoft Corporation.
2022-12-02 01:15:14.64 Server All rights reserved.
2022-12-02 01:15:14.64 Server Server process ID is 14304.
2022-12-02 01:15:14.64 Server System Manufacturer: ‘ASUSTeK COMPUTER INC.’, System Model: ‘ROG Zephyrus G14 GA401IV_GA401IV’.
2022-12-02 01:15:14.64 Server Authentication mode is MIXED.
2022-12-02 01:15:14.64 Server Logging SQL Server messages in file ‘C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\error.log’.
2022-12-02 01:15:14.64 Server The service account is ‘D3NDO\denio’. This is an informational message; no user action is required.
2022-12-02 01:15:14.64 Server Command Line Startup Parameters:
-c
-S “MSSQL11E.LOCALDB”
-s “LOCALDB#EA5605C3”
-d “C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\master.mdf”
-l “C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\mastlog.ldf”
-e “C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\error.log”
2022-12-02 01:15:14.72 Server SQL Server detected 1 sockets with 8 cores per socket and 16 logical processors per socket, 16 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-12-02 01:15:14.72 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-12-02 01:15:14.72 Server Detected 15789 MB of RAM. This is an informational message; no user action is required.
2022-12-02 01:15:14.72 Server Using conventional memory in the memory manager.
2022-12-02 01:15:14.87 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-12-02 01:15:14.87 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2022-12-02 01:15:14.87 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2022-12-02 01:15:14.87 Server Database Instant File Initialization: disabled. For security and performance considerations see the topic ‘Database Instant File Initialization’ in SQL Server Books Online. This is an informational message only. No user action is required.
2022-12-02 01:15:14.89 Server Software Usage Metrics is disabled.
2022-12-02 01:15:14.89 spid5s Starting up database ‘master’.
2022-12-02 01:15:14.90 spid5s Error: 5178, Severity: 16, State: 1.
2022-12-02 01:15:14.90 spid5s Cannot use file ‘C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\master.mdf’ because it was originally formatted with sector size 4096 and is now on a volume with sector size 16384. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2022-12-02 01:15:14.90 spid5s Error: 5178, Severity: 16, State: 1.
2022-12-02 01:15:14.90 spid5s Cannot use file ‘C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\master.mdf’ because it was originally formatted with sector size 4096 and is now on a volume with sector size 16384. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2022-12-02 01:15:14.90 spid5s Error: 5178, Severity: 16, State: 1.
2022-12-02 01:15:14.90 spid5s Cannot use file ‘C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\mastlog.ldf’ because it was originally formatted with sector size 4096 and is now on a volume with sector size 16384. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2022-12-02 01:15:14.90 spid5s Error: 5178, Severity: 16, State: 1.
2022-12-02 01:15:14.90 spid5s Cannot use file ‘C:\Users\denio\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ObsidianCS_Onyx\mastlog.ldf’ because it was originally formatted with sector size 4096 and is now on a volume with sector size 16384. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2022-12-02 01:15:14.90 spid5s SQL Server shutdown has been initiated
A setup script did not execute, could you send the install log (most recent MSI*.log file containing the text ONYX.MSI in your %TEMP% folder)?
You can force it yourself by adding HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL11E.LOCALDB\MSSQLServer\Parameters\SQLArg0 (type REG_SZ - String value) with value -T1800 to the registry. After adding, you should uninstall and re-install Onyx (you can leave the SQL server installation as is).
Sorry can’t upload here for some reason so here is in the link: WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
I think I know what issue is but it can’t be fixed due to SQL LocalDB
SQL for some reson on instalation gets info from windows that phisical sector of my ssd is 4096 but after when it tries to run a server then wants to be sector size 512. I’ve reinstalled windows for like 10th time with manual cmd formatting for sector sizes and everything
That’s correct, and the value reported appears ok (which is why the script doesn’t execute its action), but looking at your SQL errors, another parameter appears to have come into play. So, could you add the registry entry I suggested and confirm it fixes the problem? Then I could incorporate an additional condition for my script in the next build…
