Special Posted September 22, 2019 Share Posted September 22, 2019 So this is odd, I was on Paint.NET v4.2.2 and everything was working fine, then I installed v4.2.4 moments ago but my AV quarantined "msvcp140_codecvt_ids.dll" and Paint.NET won't start without it, un-quarantining this file and Paint.NET will work again, I went back to 4.2.2 to check and I don't see this file. I'm just wondering what this file is, does, and is it new to v4.2.4? Link to comment Share on other sites More sharing options...
toe_head2001 Posted September 22, 2019 Share Posted September 22, 2019 It's part of the Microsoft Visual C++ runtime. Rick explained here: https://mobile.twitter.com/rickbrewPDN/status/1174754574034333696 1 My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
Rick Brewster Posted September 22, 2019 Share Posted September 22, 2019 Also, your AV is broken and you should probably get rid of it and only use Windows Defender (I'm not picking on you -- this is pretty standard advice nowadays). The file has a valid digital signature from Microsoft. The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Special Posted September 23, 2019 Author Share Posted September 23, 2019 (edited) Hey now, if I got rid of something every time it broke I wouldn't be using Paint.NET now would I? v4.2.2, v4.2.3, v4.2.4 (and I bet v4.2.5 is right around the corner too), so Ha! And just to clarify, I use the AV that I do because it give ME the full control on MY System on what should and what does happen with its HIPS, unlike Windows Defender and pretty much any other MS product where you have no control over anything. So yeah, it wasn't due to the file being malicious (maybe I should have clarified this part better), I knew it was an MS file from the get go, it simply informed me that this .dll was trying to load and I looked at it and said, Na, block it, previous version of Paint.NET didn't use this thing so why allow some new .dll to run for v4.2.4. Maybe you like the hands off approach with Defender, but I love having a super tight Firewall and HIPS rule set that gives me the control. Also Windows Defender is IMO trash, it has some of the worst performance of all the AV's, what with it having no caching thus it will constantly scan the same files over and over every time you open a folder for example, obtuse and hidden settings that are only accessibility with PowerShell, and like I said above, gives the user almost no control over how it works, hope you like definition updated updating 5+ times a day... Oh and they currently sit on top with the most false positives, so congrats to them on that achievement! Small Edit: Oh and I also find it funny how you say, your AV's broken use WD, when recently MS broke WD. Edited September 23, 2019 by Special Link to comment Share on other sites More sharing options...
Rick Brewster Posted September 23, 2019 Share Posted September 23, 2019 Ooooooooookay well anyway you have your answer ... if you block the DLL then Paint.NET won't load The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts