Oafed

Awesome! Sounds good to me. I'll definitely do that.

I agree that the security software blows and should be dumped - unfortunately the IT gestapo has a strangle hold on us. I do have admin on my system but they are good at making it difficult to bypass (I can't just stop the service or kill the process). I heard a rumor that someone has a registry script that disables it. I need that script. Sorry for being hasty - I'm just frustrated because I like Paint.Net quite a bit but haven't been able to install it lately.

Do to the lack of acknowledgment from the Paint.Net team I figured I'd track down the bug myself. I downloaded the source and after filling in some junk strings I built and ran everything just fine. Maybe I will just have to build it myself from now on. The installer is not included as part of the the source - so I can't track down the bug. It is annoying me to no end that every computer at the corporation I work at can not install Paint.Net because our security software is blocking a buffer overflow bug in the installer.

This releates to the error identified here http://paintdotnet.forumer.com/viewtopic.php?f=10&t=21585&p=122008 and here http://paintdotnet.forumer.com/viewtopic.php?f=10&t=22228&st=0&sk=t&sd=a. No solution has been posted on either of those topics, but I've done some more debugging to identify the cause. The security program that I have installed (Proventia) is blocking the install due to a "Buffer Overflow Exploit Attempt" by SetupNgen.exe. Here is the exact security log which is blocking SetupNgen.exe from completing (which results in the 1603 / 1733 error people are seeing). Foxyshadis seems to have pulled out a debug version of Paint.Net and posted the stack trace of the exception: System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at PaintDotNet.SetupNgen.SHGetFolderPathW(IntPtr hwndOwner, Int32 nFolder, IntPtr hToken, UInt32 dwFlags, IntPtr pszPath) at PaintDotNet.SetupNgen.SHGetFolderPath(Int32 nFolder) at PaintDotNet.SetupNgen.MainImpl(String[] args) at PaintDotNet.SetupNgen.Main(String[] args) The MSI log reports The consensis is that this problem was introduced after v3.10. v3.10 does not throw this exception when installing but all subsequent versions do.

I've tried all previous suggestions, including looking through those old topics and trying what they suggested. I've done the windows installer cleanup, repared .net framework, verified the services were running correctly that were mentioned, etc... 3.30 does not install. 3.10 does. I can uninstall and install 3.10 as much as I want, 3.30 never works. I guess I'll just try each new release and see if it works - and if not I'll just keep going back to 3.10

No it isnt. The error I quoted was the error popped up by windows installer. The paint.net installer reported the failure as 1603. No I shouldn't, this topic is the same problem I am having. No working solution is here yet. Nothing at that page addresses this particular issue. omg dude... If you didn't notice I DID SAY 3.30 has the same problem. My only reason for mentioning 3.22 was to inform you as to WHEN the problem was first introduced. Geez... Don't get all butt hurt. 3.30 just came out yesterday. That isn't what is causing my problem. There is obviously something in the MSI that is failing on some systems which causes the fatal drop out of the installer. Repairing the .Net framework didn't help me. Restarting Remote Procedure Call services (RPC) didn't help me. There are not really any other solutions around for me to try.

This is rather annoying. Luckily I do have a 3.10 install sitting around which is the last version that DOES install. 3.22 did NOT install and 3.30 does NOT install. Both start installing and then pop up the error: "There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." Interestingly enough 3.30 RC1 did install. Too bad I didn't keep that version around =/ So back to 3.10 until you guys fix this.