Recent content by Labonte18

On this particular one, I could probably do that.. But.. It's not going to fly for the future. I actually installed SQL 2022 and with a few tweaks, was able to get it working... If that can get through some testing.. I suppose that's the way we'll go in the future.

So.. Microsoft removed powershell 2.0.. Which is a prerequisite for installing SQL 2012. You basically wind up with an error saying that it can't enable Powershell 2.0 and go to windows features to enable it.. Which you can't do, because it's been removed. I'm going to try to remove the...

Did all in the video.. All of that, other than being on private vs public had already been done. No difference.

Ugh.. I hate to pile on here, but I'm having a very similar issue. I have a POS system, DOS based, that runs SMB1.0.. At some point recently.. No more access to it via Win11. Win10 still works great. I've tried, I think all of the suggestions here.. No love. I have wiresharked it.. I can share...

Might be on to something here.. So.. Had to do some registry changes and now, I can see LogicalBytesPerSector : 512 PhysicalBytesPerSectorForAtomicity : 4096 PhysicalBytesPerSectorForPerformance : 4096 FileSystemEffectivePhysicalBytesPerSectorForAtomicity : 4096 Device Alignment...

Pretty much every one is coming back with some flavor of this error during install when it attempts to start the SQL Server Cannot use file 'C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is...