Please note, I have all patches on my windows, and I do mean all, this baby is setup to automatically update and when checking windows updates, it is not missing anything…
There’s been a couple other threads on the topic. Although your system may be up to date with the publicly released updates, it apparently is missing this hotfix. Chances are pretty good that if you have 64 bit Vista or Windows 7 that you’re missing the hotfix. Do what the link says and you’ll be golden. I did it about 5 days ago and it’s helped resolve some inconsistent crashes in Unity.
indeed, the hotfix solves a problem that windows itself has (hits in on other cases) where uncatched exceptions of 32bit apps cause the instant crash of the same
Well, here is the “peachy” part of this, after installing it, my framework 4 is blown, so I am now in the process of running a repair on my framework 4.0… sigh… over 3/4 of my crap no longer works and Microsoft says on the thread that the patch is not fully tested and pretty much use at your own risk, not cool
not really a “main” thread, and nothing “official” and NO never use some “other” link like the ones in the “main” thread that goes to files “outside of” OFFICIAL MICROSOFT links, aka from Microsoft.COM not that crap that is in that thread you are calling “main”, and yes, this blows, after installing the “official” microsoft version for WIndows 7 (which by the way you can’t remove once installed), I had to uninstall everything .Net 4.0 related framework and re-install them, reboot, then I can run my crap again, nice heads up on that one
FROM MICROSOFT WHEN I GOT THE OFFICIAL FILE (again not that CRAP from the “MAIN” thread that is NOT a Microsoft Link)
IMPORTANT INFORMATION
For your convenience, we put the hotfix that you requested on an HTTP site. You can download the hotfix from this site without us filling up your e-mail inbox.
WARNING This hotfix has not undergone full testing. Therefore, it is intended only for systems or computers that are experiencing the exact problem that is described in the one or more Microsoft Knowledge Base articles that are listed in “KB Article Numbers” field in the table at the end of this e-mail message. If you are not sure whether any special compatibility or installation issues are associated with this hotfix, we encourage you to wait for the next service pack release. The service pack will include a fully tested version of this fix. We understand that it can be difficult to determine whether any compatibility or installation issues are associated with a hotfix. If you want confirmation that this hotfix addresses your specific problem, or if you want to confirm whether any special compatibility or installation issues are associated with this hotfix, support professionals in Customer Support Services can help you with that. For information about how to contact support, copy the following link and then past it into your Web browser:
For additional support options, please copy the following link and then paste it into your Web browser:
Before you install this hotfix
If you decide to install this hotfix, please note the following items:
Do not deploy a hotfix in a production environment without first testing the hotfix.
Back up the system or the computer that will receive the hotfix before you install the hotfix.
Additional hotfix information
This hotfix package uses a password. Therefore, you must enter for each package the password that we included in this e-mail message. To make sure that you enter the correct password, we recommend that you highlight, copy, and then paste the password from this e-mail message when you are prompted. If you do not enter the correct password, you cannot install the hotfix.
NOTE Passwords are set to expire every seven days. Download the package within the next seven days to make sure that you can extract the files. If there are fewer than seven days left in the password change cycle when you receive this e-mail message, you receive two passwords. If this is the case, use the first password if you download the hotfix package before the date in the “Password Changes On” field that is listed in the table at the end of this e-mail message. Use the second password if you download the hotfix package after the date in the “Password Changes On” field.
NOTE For your convenience, we send the hotfix location to you in a hyperlink. To connect to this hotfix location, you can click the hyperlink in the “Location” field that is listed in the table at the end of this e-mail message to have your Web browser open that location. However, sometimes e-mail program settings disable hyperlinks. If the hyperlink in this e-mail message is disabled, please copy the hyperlink in the “Location” field and then past it into the address box of your Web browser. Make sure that you include the exact text (without spaces) between the parentheses in the http:// address.
@zumwalt - I feel your pain my friend, I’ve had my share of issues since switching from all Mac to all Windows. Fortunately for me, 99% of my issues have been caused by either a virus scanner or whatever it was this hotfix is supposed to fix. Kinda makes me long for the days when we all “had” to use Mac OS X.
I downloaded the hotfix from Microsoft. But I can’t extract the patch. The password that was provided in the email does the same thing as not providing a password at all. It can create an empty folder at best. I’ve been having issues with stability in unity and I want this to work. Maybe it’s a better idea to use older unity version? Let me know if you know about this.
The editor 64bit request went into review, so on that front there is some hope
my 18GB RAM wouldn’t mind and I know I’m not the only one with a machine like this who would like to really use beast and umbra …