VC++ Runtime ENV pre-flight checks. . .how. .

Kedar Agarkar 1

Hello All,

DEV-ENV: Visual Studio 2017 Community (Visual C++ / MFC application development)
Target-ENV: Windows 7, 8 to Windows 10

Is there any way to find exact issues w.r.to VC++ runtime ENV on target machine, even as they are seen sometimes remaining on system, after running of Re-distribution package.

I attempted to uninstall previous VC++ runtime packages and install 2017 VC++ redistribute, but some unexpected crash on specific machine sometimes re-occur. Hence.

Thanks a lot for your time.

Jeanine Zhang-MSFT 9,671 Reputation points Microsoft Vendor

2020-09-07T07:42:18.013+00:00

Hi,

Could you please provide us with more information?For example:

1,What does "find exact issues w.r.to VC++ runtime ENV on target machine" mean?
2,When the unexpected crash occurs, is there any error message? If so, please provide it.
3,when did the issue come up, before install or after?

I'm appreciate that if you could share more details with us, we will provide you with better help.

Best Regards,

Jeanine
Kedar Agarkar 1 Reputation point

2020-09-10T05:14:46.093+00:00

Hello Jeanine,

VC++ redistribute VS2017 gives error at installing. Log not intuitive. Uninstalling older VC runtime & repeat does not fix.

Created mini-dump & also logging. Log shows exit is random and happens to various different points. There is no error message. App exits(and is re-launched). Crash is happening only on one user machine. Disabled Optimizations and did simplification of pointers, math code but no use. Makes me feel - something not perfect on his VC++ runtime ENV.

After the install. While running the App.

Jeanie, I feel instead of finding root cause (which may be in his ENV), my code needs to be adjusting to fact that some PC configurations may be sensitive to math, graphics processing algo that I have and either I have to "make is simple" - all of pointer, data manipulations or tinker further with Compiler settings somewhere or both.

Thanks very much for your timely reply. Sorry, I got delayed, while fixing that crash.

KA
Anna Xiu-MSFT 28,761 Reputation points Microsoft Vendor

2020-09-10T09:32:06.247+00:00

Hi KedarAgarkar, in order to investigate this further, could you share us more installation logs? You could download and run this collect.exe tool, go to %temp% folder and find the vslogs.zip file, upload it to https://onedrive.live.com/ and share the link here. Thanks for your understanding.
Kedar Agarkar 1 Reputation point

2020-09-10T14:27:18.393+00:00

Hi Anna,

Its https://1drv.ms/u/s!Ap7_FnWIl93uhUs1N6v-IiXUpGC6?e=oZPwVz

But is at my VS machine end log. Crash is happening at user end (only). Do I repeat run at his end too?

TX a lot.

Kedar
Anna Xiu-MSFT 28,761 Reputation points Microsoft Vendor

2020-09-11T08:12:09.177+00:00

Hi KedarAgarkar, as you said, the crash only happens at the user end. It would be better to provide us with relevant logs.
Kedar Agarkar 1 Reputation point

2020-09-11T14:57:12.967+00:00

OK, Thanks Anna for your time. I will schedule a run at user end, and will certainly provide one. Give me some time. I will revert. Thanks again.

Kedar
Kedar Agarkar 1 Reputation point

2020-09-19T07:16:26.023+00:00

Hi Anna,

I have shared below, the Collect.exe logs from user machine, where my App is crashing.

https://1drv.ms/u/s!Ap7_FnWIl93uhVqYaFe44bZO5T4H?e=bShbF5

To recap. . .

MFC dynamically linked x86 build is crashing only on one Windows 10 machine, that has VS 2017 VC-redistribute well set, has sufficient RAM.

Crash happens as sharp exits from random runtime points

Looking forward to help.

Thanks

Kedar
Kedar Agarkar 1 Reputation point

2020-09-21T05:14:35.54+00:00

To add to above, the machine where it is crashing is i5, whereas all rest test machines were i3 Windows 10 / Windows 8.x.

Thanks

Kedar

2 answers

Kedar Agarkar 1 Reputation point

2020-09-19T07:15:26.643+00:00

Hi Anna,

I have shared below, the Collect.exe logs from user machine, where my App is crashing.

https://1drv.ms/u/s!Ap7_FnWIl93uhVqYaFe44bZO5T4H?e=bShbF5

To recap. . .

> MFC dynamically linked x86 build is crashing only on one Windows 10 machine, that has VS 2017 VC-redistribute well set, has sufficient RAM.

> Crash happens as sharp exits from random runtime points

Looking forward to help.

Thanks

Kedar
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Artemiy Moroz 271 Reputation points

2020-09-21T09:50:29.963+00:00

Hi!
I would suggest liking MFC and VC++ Runtimes statically. This will eliminate the need to install them each time and make your app more compatible.
Please sign in to rate this answer.
Kedar Agarkar 1 Reputation point

2020-09-24T06:14:48.95+00:00

OK, great Artem, I will try this out surely. Will post it here the results.

Will revert for sure.

Thanks a lot for your time, and answer.

Regards

Kedar
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

VC++ Runtime ENV pre-flight checks. . .how. .

2 answers

Your answer