sql server 2022 error filename, folder or syntax error occurred

Question

sql server 2022 error filename, folder or syntax error occurred

John Blasko 0

error during installation of sql 2022 or 19 or 17

error occurred filename, folder or syntax error occurred -

set and verified registry for 4k blocks

verified new download

uninstalled including registry

error comes back no matter what i do.

Viorel 127K Reputation points

2025-01-28T17:44:36.51+00:00

Did it show an error message in English? Show the details in case of 2022.
Erland Sommarskog 134.7K Reputation points MVP Volunteer Moderator

2025-01-28T22:05:29.5933333+00:00

In the folder C:\Program Files\Microsoft SQL Server\nnn\Setup Boostrap\Log you find one folder per installation attempt. nnn is 160 for SQL 2022, 150 for SQL 2019 and 140 for SQL 2017.

The files of most interest are summary.txt and detail.txt. Attach them here, and we can take a look.
John Blasko 0 Reputation points

2025-01-28T22:13:42.1133333+00:00

yes it was in english. I did the fixes for the 4k nvme under windows 11 and clean uninstalls - fresh downloads. This is the only system i haven't been able to fix.

Troubleshooting operating system disk sector size greater than 4 KB - SQL Server | Microsoft Learn

Steps Performed - How to Uninstall SQL Server: A Step-by-Step Guide - SQL Knowledge Center

Clean uninstall using above article.

Added registry fix for solid state drives

Restarting System

Downloading clean copy of SQL

Running Setup

Changing compatibility settings

Ends in Syntax, folder or filename error.

Did all those steps under your original image and a fresh clean install to see if the issue was in the image.

Tried those steps with all versions of SQL still supported

Checked folder permissions

Made sure Windows Installer was running elevated

Along with other things like SFC and MOF commands to check OS integrity.

I fix this 10 times a day, but this station has me stumped.
John Blasko 0 Reputation points

2025-01-28T22:15:13.42+00:00

we ended up loading windows 10 and installing (worked fine) then upgraded the os to windows 11 pro. Doesn't make sense but i was hoping there was something i missed. i wiped out the log files putting windows 10 on the machine.