What " " video dlls " " do you have in mind?
Care to provide any more apt description than "it's broken"?

It just black screens when trying to load the 2nd studio's splash screen and the game locks up. The game worked last year, it's a new conflict.

Originally posted by Dihy:

It just black screens when trying to load the 2nd studio's splash screen and the game locks up. The game worked last year, it's a new conflict.

Well then it's pretty clear it's M$ that broke something in their system's compatibility with existing software.
There hasn't been a single update to this game for the last 3.5 years (source: https://steamdb.info/app/522880/depots/ ).
This game is no longer getting updates of ANY kind at this point.
During said 3.5 years there's been multiple builds of Win 10 released and long used in the wild while afaik there's not been a single complaint about Win 10 issues on this forum - even tho it does not prove the problems did not exist - it still highly suggests that if problems DID exists then they weren't common.
Let me tell you something, since an average person has no clue about game design:
when you develop a game, especially a port, you work with whatever dll versions are currently being used in the wild and available for use, they may be older ones, but whatever is "supported" by the then-"supported" systems goes.
Then you set yourself a period of time in which you are willing to support your product and you apply any patches only in that period of time.
Any problems detected post or not fixed in that period of time are not guaranteed to get a fix.
There's plenty of things that generally don't work on Win 10 (such as SecuROM) and it's entirely on Microsoft that such predicament exists.
THEY chose to screw with widely used for YEARS existing dlls, in turn breaking compatibility for any legacy long-unsupported software.
THEY chose to also drop several widely used dlls (for example ones required for SecuROM) which broke compatibility with vast selection of existing software that would otherwise work just fine on that system.
When something like that happens you cannot possibly expect some thousands of private projects and at the very least hundreds of corp-originated (be it games, or perhaps custom made software for some company's internal use, say medical sector, or financial sector) projects to dig out their codebase out of the grave and suddenly start reevauluating their software.
Standards exist for a reason.
It's called a standard because the behaviour is standarized and is supposed to be consistent and unchanged over the years.
When you want to screw with a dll you just bump it's version or fork it into a new one, giving it a name of the likes of "xinput1.1" instead of blatantly breaking a standarized original "xinput1.0" in result screwing other EVERYBODY who ever used it in their software.
Microsoft by changing their own existing dlls instead of forking them is screwing over the entire industry.
YOU just cannot expect EVERYBODY to fix their stuff FOREVER, say, if M$ decides to break a dll that was standarized, constant (unchanged) for 10 years, and suddenly M$ in their ultimate "wisdom" is changing it instead of forking the changes to a new one.
When you create a game, you cannot possibly support it FOREVER. Let's be real. It's IMPOSSIBLE.
And besides, devs use M$ existing dlls as they are SUPPOSED TO be static and not-changing. It's the ONLY reason to use M$ dlls over your own originated from your studio.
It's the M$ that broke something, not the game.
Please understand and stop shifting the blame to the wrong people.

Also, some devs don't trust M$ and they SOMETIMES (only sometimes) ship their "then current" dlls in game folders. Such as for example dx 43 dll or xinput dll. Still, there is no real reason to HAVE TO do that as it's kind of awkward to expect everybody to expect M$ to break things that M$ promised to keep static - it's a needless work, and the M$ provided dlls are SUPPOSED TO be static - if they are suddenly changed then it's 100% M$ fault that they changed 1.0 instead of creating separate 1.1 with changes.
Hope you understand.

Also, you provided ZERO details (no logs, no error messages, no os/software details, NOTHING) to help you, instead just started telling people to "give up on the product" instead of even ASKING for people to help you fix this. You just blatantly assumed it is broken PERIOD.

Originally posted by Dihy:

...

Let me say this more stright:

M$ suddenly changing code of a static dll instead of forking it into a new version is as if your IT corp's building, in which you worked for last decade, would change their entire security system overnight without prior notice or any announcement of any kind nor even a previous evaluation of existing usage of existing system nor ensuring grace period for the said existing system and when you arrive for work in the morning you cannot enter the building as your smartcard isn't working anymore, in fact you can't even find a reader for it.
It's bizzare. It's BS.
As a software company, one that is international and has gov customers, AND makes everybody pay for their crappily designed products, M$ cannot just suddenly "break sh*t" "because they are keen to do so".
Static dll is supposed to be forever static for the specified version - does M$ want to make changes? What would every SANE corp or software developer do? - implement changes in new version of the same dll.
Code commit to the same version is utter INSANITY - that way you have some software that works, some that doesn't, some people that use old version, some people that use new version, and nobody knows why sh*t suddenly doesn't work as the version didn't change and the code change was covert.
No sane software dev would do that.
But then again, M$ is a greedy corp that designs their os to intentionally break, so I wouldn't be suprised if they would commit changes without bumping a version.

Did M$ change some dll without bumping it's version and it broke this game and some other software?
There is a non zero possibility for that. But I don't work for M$ and I don't read their code so I cannot possibly answer this question with full certainty.

But there is also a possibility that problem lies somewhere else. Unfortunatelly you did not provide even rudamentary details for problem debugging so you kind of not exactly making it easy for people to even attempt TRYING to help you.
Perhaps your issue could be fixed, but you provided no meaningful details so as things stand nobody will really know.

I care about this a lot less than you do.

All of the information you provided is irrelevant to someone who is going to buy and play the game in 2021. You provided a wiki's worth of contextual information on software development, but none of it tells a person if they should buy or not buy the game.

---

Let me put it simply for you:

Steam = Ice Cream Shop

Me = Customer 1 --> "This ice cream has gone bad, the shopowner left but they're still vending the same ice cream."

You = Customer 2 --> "WELL THE RETROFIT WAS NOT DONE UP TO CODE SO THE LEASE WAS CHANGED, THE LANDLORD SHOULD'VE REFERRED TO STANDARDS."

Which statement is more relevant for the next customer trying to buy ice cream? The fact that the ice cream is bad, or that the lease was changed?

Originally posted by Dihy:

I care about this a lot less than you do.

Apparently you don't care in POSITIVE sense so much that you just blatantly give up on issue and instead of asking for help you then:
Care so much in NEGATIVE sense as to go into game's forum and actively anti-shill to people to "NOT BUY IT 'because it's not working for ME'".

Originally posted by Dihy:

All of the information you provided is irrelevant to someone who is going to buy and play the game in 2021.

Why, YES, because apparently all software devs EVER should pay attention if the *static library* they used in their creation was not perhaps covertly changed by an imcomptetent software dev that provided it and they should pay that attention TO THE DAY THEY DIE! /s
Dude, you have NO idea about software development, PERIOD.

Originally posted by Dihy:

You provided a wiki's worth of contextual information on software development, but none of it tells a person if they should buy or not buy the game.

Does your issue " " "report" " " tell people it's a worthless product that nobody "in 2021" should buy?
It does, but it's unjustified call. It doesn't work for YOU. It doesn't mean it will work for NOBODY, and all that while you fail to acknowledge that your issue could perhaps be fixed.

Originally posted by Dihy:

Which statement is more relevant for the next customer trying to buy ice cream? The fact that the ice cream is bad, or that the lease was changed?

You tell me.
Do you frequent shabby shops, deliberately buying vegetables that look spoiled, only to then to blame the shop owner?
Did shop owner force you to buy the spoiled vegetables when you SAW their state?

Originally posted by Dihy:

Let me put it simply for you:

Steam = Ice Cream Shop

Me = Customer 1 --> "This ice cream has gone bad, the shopowner left but they're still vending the same ice cream."

You = Customer 2 --> "WELL THE RETROFIT WAS NOT DONE UP TO CODE SO THE LEASE WAS CHANGED, THE LANDLORD SHOULD'VE REFERRED TO STANDARDS."

Actually your comparison is worthless.
The appropriate one would be if the company making edible toppings (for the ice cream) would change something in their recipe so that it (the toppings) now can screw with allergic people or perhaps the company had a manufacturing accident and something poisonous got into the prefabricates used.
Then they silently shove this info under a carpet, informing NOBODY, they are not changing the label info (cough *dll version and changes info* cough) making no public PSAs so the ice cream shop CANNOT POSSIBLY know.
And then somebody gets to the ice cream shop, they get allergy/poisoned and they BLAME THE ICE CREAM SHOP and not the company that is ACTUALLY to blame.
Are they making uninformed judgment calls? Yes, and so are you.

This is in parallel to M$ being suspected of changing their supposted-to-be static dlls' code without bumping their versions.
This is in NO WAY fault or a problem of the developer.
To make more crude and rudamentary example:
if M$ would suddenly change for example DirectX 43 dll without bumping it's internal version it would screw like 90+% of software on the market (out of that that uses directx and was made post the dll's original creation timestamp)!
You're not supposed to do that as a soft dev! And the people who used the dll for their end products are NOT AT FAULT!

But then again, for the THIRD time now, you have provided NO details, you have not even TRIED to seek help, and all you do is yell "it doesn't work for me (while I don't care to specify ANY technical details helping isolate the issue to a subset of user software configurations), DON'T BUY IT!".
Like, seriously...
Dude...
You need to understand that I am pretty darn patient here, but the kind of behaviour you exhibit in the OP post would REALLY piss a lot of people off.
You are making too broad of a judgment, and with NO evidence provided from you!
Would *I* buy a game knowing it MIGHT not work for me? YES.
Because when a problem arises I troubleshoot, and if I am not skilled enough to fix the problem myself I ask online WHILE PROVIDING APT INFO that is sufficient for debugging. I don't go all "it doesn't work for ME, it's 'DEFINITELY' developer's fault, DON'T BUY IT!".
When YOU don't even seek help, you just give up and yell "DON'T BUY IT" you have only yourself to blame.

O boy

Originally posted by Dihy:

O boy

"The covert change in code passed OUR testing procedures so it surely will work for everyone no problem" - some incompetent M$ employee when changing a software library (dll) code without bumping it to a new version

"It doesn't work for me so nobody should ever buy it and I am 100% certain the dev who used prefab static dlls made by SOMEONE ELSE is the one and only one to blame" - some software end user

Are you here for HELP?
Or are you here to grace the world with your exquisite statement of a " " " "fact" " " "?
I asked you REPEATEDLY to provide meaningful details so that I, and others, can at least TRY to help you.
You FAILED to do so and instead you are just blaming the dev blindly.
So I am done here.
There's helping people, and then there's wasting your limited life's time for people who fail to cooperate.
Have fun with Steam support.
I am sure they will be more than happy to tell you the same things I did just in a little bit different words.
Have a happy life.
Peace.
Bye.

what a ♥♥♥♥♥♥♥ psycho

Lol, side note I'm on Windows 11 on a new PC now and the game loads in fine.