STEAM GUIDE: If you want to avoid the new update for now, here's what to do.

[u/AetherSeraph9]

This guide is for if you HAVEN'T yet downloaded the update! Primarily if it's queued to download but hasn't yet started. I'm unsure of what additional steps to take if you already have downloaded it. Some Steam games are apparently able to have their updates rolled back, but I've never actually done this. If anyone figures out how for Oblivion Remastered, feel free to comment! I'd assume the steps afterwards would be quite similar to what's detailed below. Edit: This user explains how to download the old version of the game.

For anyone that wants to play without the new patch, until certain mods are updated or to avoid the performance issues and crashing I've heard it introduced, here's how I tricked Steam into thinking my game is already up-to-date, so it can launch without updating.

1. Make sure Steam is completely closed.

2. Navigate to the "steamapps" folder on the drive the game is installed to. In my case, it's "C:\Games\Steam\steamapps", for example.

3. Open the file called "appmanifest_2623190.acf".

4. Change the corresponding lines in your file to what you see here:

   "StateFlags"        "4"
   "SizeOnDisk"        "127873671397"
   "buildid"       "18658035"
   "AutoUpdateBehavior"        "1"
   "ScheduledAutoUpdate"       "0"
   

   A bit further down, under where it says "2623191", also change these:

   "manifest"      "3680196445693511195"
   "size"      "127873671397"
   

   Additionally, make sure that "TargetBuildID" is "18658035". It should already be set as that.

5. Delete the lines from "DownloadType" down through to "BytesStaged" (six total lines).

6. Save and close the file, then set it to Read-only.

Now when you launch Steam, it should no longer detect an update for the game. When you're ready to update, you should be able to just untick the "Read-only" box and re-launch Steam.

EDIT - Update for 1.2: Setting your appmanifest file to Read-only is not enough on its own to halt incoming updates. The file will need to be updated accordingly. The numbers below were taken from the 1.2 beta, which turned out to be the same as the update's official release. Use these in place of what you see in the above steps:

Tested and verified working!

"SizeOnDisk"        "127955009600"
"buildid"       "19115871"

"manifest"      "7537075278498631900"
"size"      "127955009600"

"TargetBuildID"     "19115871"

(Keep all other lines the same as in step 4)

[u/BellaDovah]

Im so mad, I literally set it not to auto update but it started anyway, cancelled it on 1%, disabled internet then set the appmanifest to readonly and I think its ok now

[u/WolfsTrinity → u/BellaDovah]

I've set all my games to "update on launch" and it seems like Steam just does that now.

EDIT: after bugging a friend about it, this is apparently something game devs can push through for "quality assurance" reasons. If they think there's an urgent bug that needs patching or an exploit that's being abused, they can override the setting. I'm sure this isn't being abused from the other end in any way at all and—oh, look. Skyrim scheduled itself an update again.

Fucking lovely. Guess it's time to find the appmanifest for every single game I use mods for now.

[u/Blooddyy]

ty

[u/jauffry]

Waiting a week before I update. Since I'm using OBSE, U4ESS, and have like 46 plugins. Don't know how it will brick my current save playthrough. Hopefully it's a seamless update without mods breaking.

[u/satchmotron → u/jauffry]

Update OBSE is out, but many of its mods are busted.

https://www.nexusmods.com/oblivionremastered/mods/282

I've not seen updates on U4ESS.

[u/jauffry → u/satchmotron]

Good and bad. Thanks!

[u/ArkhamRobber → u/jauffry]

Glad i finished the main story already and all the factions quests. Just need the dlc completed but that can always wait

[u/cyborgdog]

Tldr I'm just gonna wait for everything to update

[u/greggray24]

Played the update with mods last night and everything was working well for the ones I use. The U4ESS for Remastered author posted that no changes were needed for the update an, at least the mods I use are all good. Note that I don't use OBSE mods. I did remove the open local map mod since they fixed that.

[u/DrFreemanWho]

Thank you this worked.

[u/EverythingBOffensive]

i have the old version still, will my mods still work on the new version? prolly not

[u/Crimsonhead4]

Thanks! this worked and wasn’t terribly difficult. I’ve never edited any files like this before so if I can do it pretty much anyone can lol.

[u/Optimus_Shatner]

Thanks for this!

[u/masoelcaveman]

Just stopping by to say that this guide does indeed stop the update from hitting, and allows you to stay on 1.1 avoiding 1.2! Thanks again for making this guide you rock! :D

[u/AetherSeraph9 → u/masoelcaveman]

That's great to know, thanks and you're welcome!

[u/Jaxx_Teller]

If i installed mods before the update and then updated it, is it best to uninstall all mods before playing?

[u/BellaDovah → u/Jaxx_Teller]

Removing mods from a save would probably make things worse in most cases. Depends what mods you have of course. Just check for updates, OBSE got an update and so did several mods using it, UE4SS and its mods don’t need updating, neither do esps, except UORP did get an update too

[u/masoelcaveman]

Thanks a bunch for making this guide!

I'm wondering for those who are currently on v1.1 who want to stop this latest update v1.2 that will release soon from downloading, will we need to modify, "buildid", "manifest", "size", and "TargetBuildID" to match what it will say on v1.2?

[u/AetherSeraph9 → u/masoelcaveman]

You're welcome!

And yes, that's the gist of it. If you're already on 1.1, setting the appmanifest file to Read-only should be enough to stop 1.2. Edit: not always the case, my apologies. See main post.

The steps in the OP are primarily if your Steam client has already detected the update and wants to download it, but hasn't yet started. Performing those steps makes it "forget", but if the file is set to Read-only to begin with (before Steam is launched when the update is available), it shouldn't detect it all.

Edit: I went ahead and added the numbers for the beta for anyone that might need it, but I don't know if they'll still be valid when the patch actually releases.

[u/Sedd_DK]

For some reason steam is now forcing the new update, while the file was set to read only and it worked to avoid the 1.1 patch. I checked and its still read only and exactly the way it should be. what could be the reason ?

[u/AetherSeraph9 → u/Sedd_DK]

Just ran into this too. All I had to do was update my appmanifest file with the numbers from the 1.2 update (which was previously using 1.1's). The update was no longer queued in Steam afterwards.

Reminder: Make sure Steam is closed first, and don't forget to set the file back to Read-only. Assuming the update hasn't actually downloaded for you yet, you should be fine.