Jump to content

Microsoft VC++ redist is broken on XP. How to start a ticket in MS Support?


Dibya

Recommended Posts

It seems Microsoft did their job again i.e breaking stuff.

https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

Latest VC++ 2015 2017 and 2019 Re-dist is broken on XP: https://aka.ms/vs/16/release/vc_redist.x86.exe

It now calls some API which are replaced with Stubs in Windows 10 ( Don't believe , Hit those api on respective DLL with Dis Assembler)

We need to start a ticket to let them fix the runtime as soon as possible as People still code for XP and we need newer C++ Standard.

Edit: Please someone start the Support ticket and We all will go and support. Microsoft accounts knows i am 18yrs old they will not take me seriously.

Edited by Dibya
Link to comment
Share on other sites


15 hours ago, Dibya said:

We need to start a ticket to let them fix the runtime as soon as possible as People still code for XP and we need newer C++ Standard.

Edit: Please someone start the Support ticket and We all will go and support. Microsoft accounts knows i am 18yrs old they will not take me seriously.

:blink:   Are you serious? Really? No offense meant, but what world do you live in? XP SP3 went EoS on April 8 2014 (and POSReady 2009, on Apr 9 2019). Now, we're on Apr 26 2021, just over two years after that, what on Earth justifies believing MS did that by mistake, while striving to keep backward compatibility with an OS they'd rather had disappeared already? They wouldn't be able to care less even if they bothered to try it! Come on, wake up to reality, it's time already! And make no mistake, I do love XP SP3 and actually use it as my main OS to this day.  :whistle: 

Link to comment
Share on other sites

10 hours ago, luweitest said:

Thanks @Dibya for the warning. I installed that redist just the other day, yet no abnormality observed yet. I don't know what specific app will call that redist. Is there an old version of 2015~2019 redist not affected?

These are the last versions that work

http://i430vx.net/files/XP/EOL/VC1719_redist.XPx64.exe

http://i430vx.net/files/XP/EOL/VC1719_redist.XPx86.exe

Link to comment
Share on other sites

Microsoft does not fix bugs unless it is forcasted to have an impact to their bottom line. It doesn't matter if it is related to a currently supported product or not. I have submitted bug reports including PoC for current MS Office and with the ADK and they do nothing about it, not even acknowledge it. The typical reaction goes something like this:

:unsure: If I do a specific thing, I get an error. How should I fix it?
:angel Let me ask you a bunch of irrelevant questions
... (a lot of back and forth)
:unsure: I found what makes the error. Here are the commands I run, what happens, the logs and traces, and how to fix it
:angel = :zzz:

Sometimes it comes down to who you talk to. If the person you are interacting with is a support person and not a tech or engineer, then they may see a "resolution" of using a workaround and never pass it up. Once they think they have "solved" the issue, it is over. Nothing is ever done, not even make a KB or a post about it.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...