It broke full RAM-usage so if you tweaked your game LAA-wise to get better performance, this is probably the cause for it running slower now.

Wait, so, you are pissed becouse the game is running slow becouse you tweeked it?

I don't understand... If you tweeked it for better perfomance, that's cool well done, awsome. But then, if they patch something for or using the 'origonal' data etc then isn't it your fault? Are you annoyed they did not cater for your needs or are you annoyed you tweeked it?

Despite what it looks like, I really am trying not to have a go, I am just really confused as to the issues. And, by tweeks I dont mean Mods, I mean other tweeks you have done to better your performance.

No, what I′m talking about is having the LAA-flag enabled on the TESV.exe
It′s not really a tweak, it′s more a fix for the fact that we have no 64bit installation for the game.
LAA is a common way to make applications use your whole memory and it′s done everywhere to increase performance. Skyrim is a new game with highest graphics standards AND it′s meant to be modded. There is no way this could work out well with only 2GB of RAM supported. The new update encrypts the .exe so it would ONLY work with steam. This is to prevent people from pirating, but pointless, as the patch was applied on steam, and the pirated versions don′t use steam anyway. The downside for us, who purchased the game is that now the game will only use 2GB of our 8+ GB of RAM and therefore will crash repeatedly for those who boosted up the graphics, because this demands more memory than the game can use, even if there′s more RAM available.
They didn′t put a 64bit .exe installer on the disc/for download in the first place, why would they make the tweak harder as well for us?
This is why I′m complaining, now we have to use an old .exe to run our games on a quality that our PC′s support!

What an utter nonsense !

I'm run it through Steam anyway so this didn't affect me, but I do want to address this. EULAs do not trump the law. That's why companies will rarely try to defend a EULA in court. They know there's a strong chance they might lose, and they don't want to set that precedent.

Actually you ARE affected exactly because you are running it on steam.
I recommend you not to install any memory-consuming mods until the next patch, or use the old .exe if you want to... test it, if you have stuff running in the background that uses RAM, you might experience crashes... watch your memory!

No, it would only affect the mod people. I'm not using mods yet.

Background programs have no effect on it though. 32 bit memory limits affect ONLY that program, and not the system memory. The OS handles that, in this case Windows 7 64 bit version.

Honestly it's not that great of an idea to mod the game before the creation kit comes out. Even after that it's probably better to wait for a patch or so. That gives mods time to mature and it gives Bethesda time to tweak.

If you choose to mod now (or have to use a mod for whatever reason) you should probably resign yourself to having issues when patches come out.

If you're not modding and you have a problem, a lot of the time the check file integrity thing does the job.

Right or wrong, that's just how it is - and how it's been in the past.

I had to roll back to my pre-LAA executable because my frames suffered so horribly. I hope this is fixed, then again, I don't think X3TC was ever LAA patch-able after its last steam patch.

Please use http://www.gamesas.com/index.php?/topic/1284688-request-that-recent-patch-be-fixed-to-allow-laa-to-prevent-ctds/ for discussing the LAA issue.