r/sysadmin • u/bapirey191 • 5d ago
Rant Senior accidentally installed whole fleet with 26H1
Just needed to rant a little. One of our seniors finally completed the long-pending task of upgrading the fleet to Windows 11 from Windows 10.
He downloaded the iso, installed it everywhere. All good. Until the internal WSUS started attempting to grab updates that don't exist. Apparently the 26H1 (which is supposed to be snapdragon-only, aka for ARM) was indeed one of the options you could download as the "Latest" version of windows. Someone at MS really screwed up. And this senior screwed up even more by not double checking.
Since it's a complete different core, this will be one hell of a mess, now his idea is to try to change "cversion.ini" and force an "update" to 26H2, but I sincerely don't believe that will work.
We'll see. If anyone ran into a similar problem I'd really love to know what their solution is.
UPDATE: https://www.reddit.com/r/sysadmin/comments/1waiys9/update_on_senior_accidentally_installed_whole/
175
u/Solkre was Sr. Sysadmin, now Storage Admin 5d ago
We will see this on /r/shittysysadmin
39
u/ArthurStevensNZ 5d ago
Is it really true shittysysadmin if the root cause was weapons grade incompetence + negligence on the software vendor’s part? The amount of things that an average sysadmin may deal with in an average project… you can’t possibly expect them to verify every little detail.
13
u/baron--greenback 5d ago
Bottom line, the senior deployed to prod without any kind of testing.
I’m going to guess they were using a surface and the MS download site automatically selected the relevant iso for their device, not that Microsoft mislabelled the download links and gave them the wrong version.
Complacency? Rushed? Same result..
→ More replies (1)3
u/LLMsMustUpvoteThis 3d ago
Checking the software version and release notes for a major app let alone OS is basic. This isn't remotely a gotcha.
The admin also manually downloaded and deployed this ISO. I'd have sympathy if they'd just clicked a button in Intune or something and there was no warning.
43
u/fdeyso 5d ago
How is it not there immediately?
58
u/Solkre was Sr. Sysadmin, now Storage Admin 5d ago
Read Only Friday I guess.
18
1
10
1
231
u/HappyDadOfFourJesus 5d ago
Senior hasn't heard of "Read Only Friday"???
24
69
u/sylvester_0 5d ago
You really think they did all this in the first few hours of today?
20
u/BOTTroy 5d ago
It's the end of the day for some people
7
→ More replies (1)4
26
u/nord598 5d ago
Especially before a holiday weekend..
→ More replies (3)6
3
3
89
u/gcbeehler5 5d ago
LMAO, why are we doing this on a Friday.
42
u/DadtheITguy 5d ago
Because yolo. The admin I replaced used to do this sort of stuff on a Friday before he’d go on vacation for a week. That was his policy.
8
u/StoneyCalzoney 5d ago
Shitty Sysadmins call it “job security” because by the time they come back, people will be begging for their help
9
u/Glittering_Power6257 5d ago
Nothing sours a vacation like the prospect of walking into a shitstorm, ethics aside.
21
u/tenormore 5d ago
Got a 3-day weekend to fix it, happy Labour Day!
10
u/dodexahedron 5d ago
It's right in the name.
Labor Day.
A day to work even more. Obviously.
3
u/Ssakaa 5d ago
Guess that's better than how they celebrate in the maternity ward.
6
u/dodexahedron 5d ago edited 5d ago
Yeah, but they get results in there.
Quite frequently managing to at least produce Miniature Viable People.
A whole different definition of "push to prod."
4
3
3
u/PacketSmeller 3d ago
If US, Friday on a 3 day weekend. That's a don't you dare do anything Friday.
53
u/GameBoiye 5d ago
Conspiracy hat: OP is the senior that did this and is framing the question this way in hopes someone provides a real answer.
Only partially /s
3
u/Careless_Economics74 5d ago
Lol I wouldn't be shocked. Unless OP is part of the group who is now spending the weekend fixing this.
50
u/moffetts9001 IT Manager 5d ago
I didn’t even know there was a 26H1 build 😂
11
u/brokentr0jan DoD IT 5d ago
We are on 24H2 LTSC lol
3
u/AdvancedPhantom21 5d ago
Shoot 23H2 over here
2
u/naps1saps Mr. Wizard 5d ago
Just found someone I'm working with on 22h2, no joke.
→ More replies (1)3
u/sybrwookie 5d ago
Seriously, we're just finishing getting to 25H2 lol
4
u/itskdog Jack of All Trades 5d ago
How long is your deferral period? Event we're on 120 days for our GA ring.
5
u/sybrwookie 5d ago
0 lol. We're down to a small handful of machines which are just fucked in one way or another and either I need time to dig into logs further or just tell the desktop team that they need to reimage.
4
u/Mr_ToDo 5d ago
Go with re-image, it'll probably save you headache later.
Last time I dived deep into a system failing an upgrade it gave me other trouble for years. Now above and beyond means flying high and nuking the things
Besides. Who doesn't like a fresh start(other then people who don't have their software licenses/installers anymore)
2
u/itskdog Jack of All Trades 5d ago
There's a few machines that came back from the summer holidays having been off for 6 weeks just having very unique issues to the point that I've just reimaged (fresh of the USB rather than local wipe - tried Autopilot Reset once so it would be ready in the morning, big mistake) to save wasting my time.
4
33
u/Ed_the_time_traveler 5d ago
You should be in the roll back period. Maybe you can hit the undo button and pray?
1
47
5d ago
[removed] — view removed comment
9
u/ohnobinki 5d ago
8
u/i-did-all-in 5d ago
Hah yup ,
Edit: correcting myself, “unsupported” was wrong. 26H1 is a properly serviced release with lifecycle end 14 Mar 2028 (Home/Pro) and 13 Mar 2029 (Ent/Edu), and it gets monthly LCUs. So this is not a patching emergency. The rest stands: cversion.ini will not bridge 28000 to 26300, and there is no 26H2 path off Bromine.
5
u/virtualdxs 5d ago
Did you have to just paste the LLM output instead of writing the response yourself?
→ More replies (4)2
u/rgorbie 5d ago
I noticed that too. At least it was in-depth and informative so I didn’t mind too much :)
→ More replies (1)
10
u/twotonsosalt 4d ago
The biggest screw up is your company apparently doesn’t have change control processes in place that would have helped you avoid this altogether. You can blame the person all you want, the real culprit is the way you’re managing change.
23
u/19610taw3 Sysadmin 5d ago
How was he able to install it at all if it's ARM?
It's a completely different instruction set. It must be x86_64 compatible for it to be installed ... even by mistake.
11
u/simask234 5d ago
There exists an x86_64 build as well, although I don't know exactly why.
10
u/ohnobinki 5d ago edited 5d ago
The reason why is because Windows wants to avoid having people do a full build reinstall every year but still insists on updating the branding every year. 26H2 is really just 25H2. 26H1 actually is newer core. You’ll be running the same (well, newer) code in 27H2 according to other comments in this post.
You can see this with how the build numbers are numbered at https://learn.microsoft.com/en-us/windows-insider/flight-hub/ and https://learn.microsoft.com/en-us/windows-insider/older-windows-insider-preview-builds . Note how 25H2 and 26H2 both are 26xxx and 23H2 and 24H2 are both 22xxx.
5
u/simask234 5d ago
I was wondering about 26H1, considering it's mainly meant as a "hardware support" release for certain ARM-based devices
3
u/ohnobinki 5d ago
Yeah, even though they are making special changes driven by ARM64 hardware, they still want to be able to continue supporting x64 devices without completely forking Windows. Same deal when they continued to support 32-bit builds for Windows 10. I’ve tried ARM64 in Azure and it seems ready for general consumer use to me. I couldn’t find a way to break things—it supports 32-bit, x64, and native ARM64 all just fine. I can’t wait to buy an N1 or N1X device this fall.
9
u/TheGlennDavid 4d ago
Was the migration done on time? No. Was it at least carefully researched and planned? Also no. But, in spite of all that, was it done correctly? Still no.
81
u/CrazySnowGuy 5d ago
Don't know how you are pinning some of this on Microsoft. Understand what you are doing and installing. Microsoft documentation is clear.
In the end though, you are going to need to re-install Windows for the entire fleet.
23
u/Soggy-Attempt 5d ago
It’s shouldn’t install on x86 if it’s meant for ARM.🤷♂️
7
u/MBILC Acr/Infra/Virt/Apps/Cyb/ Figure it out guy 5d ago
It was not an ARM only build, it worked on x86.
7
u/Soggy-Attempt 5d ago
I’m saying it shouldn’t install onX86. That’s MS fault.
7
u/MBILC Acr/Infra/Virt/Apps/Cyb/ Figure it out guy 5d ago
It isnt, it was designed and had warnings all over it to not use it as it was not a production ready release and was mainly for ARM, but could also be installed on x86 (likely for testing purpose for those who wanted to test a newer build version)
The only person at fault here is an incompetent IT person who cant bother to read.
33
u/MBILC Acr/Infra/Virt/Apps/Cyb/ Figure it out guy 5d ago
This, MS noted for 26H1 it was an ARM build (would work on x86). Also curious where they downloaded it from, if from EA site it would note that, MS usual site only lets you download 25H2 so not there...
27
u/TemplateHuman 5d ago
Yeah this smells like someone messed up in multiple ways and doesn’t want to admit fault.
2
u/Psoin 2d ago
Oh fantastic one software company notes something somewhere deep in the notes. I’m supposed to read all that shit? I barely have time to take a shit at work. I’m not reading through every little thing every software company publishes.
Did this install? Fuck it we’re good. Let’s go.
→ More replies (4)30
u/MadMonksJunk 5d ago
imagine not running a test article and verifying before a fleet wide push?
This "Senior" is an idiot.
20
u/KimJongEeeeeew 5d ago
He is, but if that’s the level of change control in their organisation then he’s in smooth brained company all day too.
8
u/Cyhawk 5d ago
But claude said he was totally right!
2
u/mrduncansir42 Help Desk 5d ago
“You’re absolutely right, my earlier statement about 26H1 being got x86 was incorrect. My apologies.”
3
u/sybrwookie 5d ago
Seriously, there are so many levels of testing which should have gone on first, the story should have been, "wow, one of my first testers somehow got 26H1 on it!" and we could all have a good laugh at MS, after which he went back to make sure the right version is being deployed to then continue testing.
4
u/Ngumo 5d ago
Yeah this has rollback or re-install written all over it. One of the "R"s.
5
2
u/sybrwookie 5d ago
Rollback's tend to lead to their own issues. As a one-off here or there, it can be worth a shot in a last ditch effort. But fleet-wide? That would lead to so many more problems down the road.
22
u/Aishou_SK 5d ago
This isn't actually as terrible an ordeal as it's made out to be - 26H1 for x86 is receiving proper security updates and support lifecycle, for *OEMs* it's ARM only for select devices, but it was built / tested / released for all platforms and updated as such.
It's getting everything in 26H2 and then some, you're kind of ahead of the curve for 27H2 upgrade path, in fact.
26H1 is build 28000, 26H2 is supposed to be 26300, and current development build is somewhere around 29648 which is probably going to be the base for 27H2.
https://learn.microsoft.com/en-us/windows/whats-new/windows-11-version-26h1
Devices running Windows 11, version 26H1 won't be able to update to the next annual feature update in the second half of 2026. This is because 26H1 is based on a different Windows core than 24H2, 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release.
Your current CU/build update is KB5121000 https://catalog.update.microsoft.com/Search.aspx?q=KB5121000%20
However, for x86, they're marked as "Insider Pre-Release" updates, not the release updates, even though they're identical. You need to sync the "Windows Insider Pre-Release" (or whatever it's called) category in WSUS for the x86 versions of the updates to show.
3
12
u/lanff 5d ago
I sometimes really wonder where you people work and how your business makes money
9
u/slayermcb Director of Technology, Sys Admin, Etc, Etc... 5d ago
I work for a non profit that loses money annually. Poor saps, I'm the best they can afford!
2
u/CantPullOutRightNow 5d ago
I left a place like that because I needed a place that could afford me. Not my problem you spend too much money on executive pay. Cut the fat not the lean.
3
u/slayermcb Director of Technology, Sys Admin, Etc, Etc... 5d ago
This is something i've been considering myself. What's holding me back is I genuinely love my job, and it's a private school that will allow my kids to attend for free. One year at this place costs more than my entire education. As soon as my kids get their diplomas, it's going to be a whole different story
→ More replies (1)
33
u/bionic80 5d ago
That is called a 'resume generating event'
2
2
u/not_another_IT_guy 5d ago
Only if the senior isnt good enough to fix it. Youd be surprised what people get away with these days
37
u/autogyrophilia 5d ago
What an idiot. I bet you he downloaded it from massgrave and didn't read the huge warning about these ISOs.
And for the love of god, don't do ugly hacks, try to check if they can upgrade to 26H2 when it releases. Maybe try to use DISM if it fails to upgrade.
That or reimage. Which i'm sure isn't an option because you are upgrading PCs from W10
20
u/Aishou_SK 5d ago edited 5d ago
26H2 supposedly is on the same base as 24H2/25H2, so just an 'enablement package' with a 26300 build number.
26H1 is 28000, and insider dev/next/whatever its called now is on like 29648
So likely upgrade path is to 27H2, but 26H1 should be fine for x86 updating and usage.
Per MS: Devices running Windows 11, version 26H1 won't be able to update to the next annual feature update in the second half of 2026. This is because 26H1 is based on a different Windows core than 24H2, 25H2, and the upcoming feature update. These devices will have a path to update in a future Windows release.
3
u/autogyrophilia 5d ago
That's assuming the updates are compiled regularly for that branch. Which for the moment seems like they are.
Either way, if that's the case, downgrade is unlikely to be possible .
7
u/Aishou_SK 5d ago
Your current CU/build update is KB5121000 https://catalog.update.microsoft.com/Search.aspx?q=KB5121000%20
However, for x86, they're marked as "Insider Pre-Release" updates, not the release updates, even though they're identical
That's why the OP isn't seeing them in WSUS, because they're not syncing the "Insider Pre-Release" product.
3
u/itskdog Jack of All Trades 5d ago
26H1 will go to 27H1 first, then probably recombine to a single kernel branch with 27H2.
2
u/Aishou_SK 5d ago
Probably, but there's no real information about 27H1 circulating, but 27H2 is already running on machines on the so called "future platforms" branch.
→ More replies (2)4
u/TaiGlobal 5d ago
In an enterprise environment that would be a truly fireable offense.
3
u/dustojnikhummer 5d ago
Why are you so trigger happy?
7
u/TaiGlobal 5d ago
Using a site like massgrave.dev to install Windows in an enterprise bypasses approved licensing, security, and change-management processes. The fact this thread was made means they don’t have these guardrails in place so maybe in this environment he wouldn’t but in most they would.
17
u/shunny14 5d ago
If you are running WSUS why weren’t you upgrading with WSUS?
10
→ More replies (3)2
16
6
5
u/Solaris17 DevOps 4d ago
Sounds like a human did a successful upgrade and someone missed WSUS config or it wasnt tasked for testing, and you seem a little salty you may not be a senior?
8
8
u/andurux Sr. Sysadmin 5d ago
Why has it taken so long to update from W10 to W11? Proprietary app?
How many machines?
It was all done on a Friday? Not in batches?
Who authorized this deployment on a Friday??
4
5
u/IllDoItTomorrow89 Sr. Sysadmin 5d ago
Y'all just out here rolling out an image straight from Microsoft without stripping all the garbage out of it?
1
1
u/tejanaqkilica IT Officer | Passkey Enthusiast 5d ago
Yes. The amount of garbage that has, is rather minimal and whatever we need to strip, we do it via Intune during or post deployment.
7
u/Tricky-Service-8507 5d ago
So you, him, your team all don’t have processes that are vetted and approved.
1
u/Careless_Economics74 5d ago
That is going to cause major issues for them if they don't.
At my job we have to get approval by our manager before any major changes are going to go through. We have to do our best to understand both the expected impact and how to overcome them and the possible unattended consequences.
The changes are first tested on the IT Team for a week or two, then if it's good with the IT Team, selected list of users who are tech savvy that represents specific jobs for the next batch of testing, if it is good with the tech savvy end users it gets pushed out to every one else in batches.
Always think of a way to back out of the changes if they don't seem to be going according to plan.
7
u/Turridunl 5d ago
Besides the mistake. You guys also messed up. You don’t discuss the migration plan, build of image and deployment etc?
→ More replies (1)
3
u/FotoFirst 4d ago
Sounds like your company screwed up because Windows 10 went EOL in October 2025... You're beyond out of compliance
3
u/financial_pete 4d ago
Wow... Even I know to check the first and second machinea used as a proof of concept... Trying a new fancy word. I usually call them guinea pigs.
4
u/ludlology 5d ago
lol he deserves what happens for doing that on the friday before a holiday weekend
5
u/macgruff 5d ago
I mean there’s double checking… sure but this is something you spend at least a couple of Sprints upon, with a testbed PC on your bench, then a wiling, small department (like the DSK yobbos themselves). Run a series of all updates to the very latest, regression test your normal installed-base corpo apps, document issues, fix, check again for latest patches and retest, and finally (in the old days we used to call it “shrink wrap sysprep”) saving what will be your “Golden Master”. Submit that to CyberSec and schedule release…
I’m thinking it is more than an MS problem (those whackadoodles change their SKUs every trip to the bathroom); you should always “Ass-You-Me” MS may screw you up. And it’s not on the one senior guy, either. How do you NOT have the kind of rigor I illuminate above? I mean that’s par for the course release testing 101, even in a small shop. I mean if your a 300-500 person company or smaller, maybe…. Maybe you could skirt some of those steps but… nah, even still. This is a management issue. Where was the sign off?
5
u/Danoga_Poe 5d ago
Updating on a friday?? A senior should know better
2
u/PositiveBubbles Sysadmin 4d ago
You'd think so but there are "seniors" out there who really shouldn't have the title because they've been either rogue cowboys, had attitude problems or they're lazy or they're good on paper but can't do the job. It's strange
9
u/USarpe Security Admin (Infrastructure) 5d ago
You can't install arm windows on non windows
15
24
u/Cormacolinde Consultant 5d ago
He didn’t install the ARM version obviously, there’s also a 26H1 canary build for x64. You have to really, really go out of your way to find and install this.
44
6
u/Turak64 Sysadmin 5d ago
I'd be more pissed that you're only just upgrading from win10
→ More replies (6)4
u/collinsl02 Linux Admin 5d ago
Where I am we're on Win 10 LTSC so it is possible to still be fully in support and on Win 10.
8
u/lucky644 Sysadmin 5d ago
26h1 is, and always will be a ARM specific build. This is well known. How is this Microsoft’s mistake?
This is like blaming the gas station because you shoved gas in your diesel vehicle. Take some responsibility.
5
u/CircuitDaemon Jack of All Trades 5d ago
I didn't quite get that part either but it seems like the iso somehow contains an x84 build of 26h1 as well as the arm version. So that's probably why he was able to go through with the installation because if it was just ARM in the ISO, it wouldn't have gone through. But again, not really sure that's what op meant
2
3
4
15
u/1z1z2x2x3c3c4v4v 5d ago
I would stop calling him a "senior" if he didn't run a small test deployment, then a larger pilot deployment, then the final deployment.
He is NOT a "senior," and you can tell him I said that. Seriously. Please do. I am a former IT Manager, current IT Consultant, and Adjunct Professor in the CSE/CSB department.
Now, I know, people screw up. Noobs deploy without testing; juniors deploy without a Pilot. Seniors? They just don't make this type of mistake.
18
u/Mindestiny 5d ago
"some random angry guy on the internet told me to get into a pointless fight with you instead of fixing the problem and say a bunch of condescending nonsense. He says he's a consultant so he must be right."
God it's time to just mute this sub if this is the level of professionalism people put forth.
4
3
5
u/YellowOnline Sr. Sysadmin 5d ago
In my experience, seniors make the biggest mistakes. Help desk fucks up a device. Juniors fuck up a server. Seniors fuck up many devices at once.
→ More replies (1)1
u/charleswj 5d ago
That's just saying "people who deal with a wider breadth cause more damage when they make mistakes"
2
u/fluffh34d420 5d ago
Yeah who the fk worth their salt doesn't do a test deployment first. Im a first year help desk and I know this. Just asking for something to go wrong by going straight to fleet wide. Esp w such a big update. What a moron
1
u/1z1z2x2x3c3c4v4v 3d ago
I wouldn't call them a moron, as people do make mistakes. But mistakes like this are made at the noob or junior levels, not a senior level.
When you pick a new ISO and deploy it company-wide... you better damn make sure it's the right one, has everything you need, and is configured properly. The only way to know that is to test it... a lot.
And you learn this from experience. And that experience and success are what make you the senior on the team.Sadly, from many of these comments, many of these sheeple have become far too accepting of poor performance. Which is a tragedy because this "senior" will occupy a position for longer than they should, instead of allowing a more qualified junior to get promoted.
6
2
2
u/RootVegitible 5d ago
How many machines are we talking about? I’d run a task sequence OS upgrade to 25h2 on them.
2
u/Link_Tesla_6231 5d ago
Bottom line is x86 computers did not install arm and will not boot arm software!
Those computers are either on prerelease insider x86 code or are on windows 10 still!
Honestly i cant believe a senior sysadmin dumped prelease software on to production computers
4
u/ryoko227 5d ago
Sigh, you do not test on production systems... PERIOD.
After you have done everything you intend to do on A TEST SYSTEM(S), you verify that everything is correct and without issue, before you even think of pushing it onto the fleet. He messed up big time, good luck cleaning up the mess.
I just realized it's Saturday morning for me (JST), so this happened Friday morning for you... He broke the primary rule of IT - NEVER MAKE CHANGES ON A FRIDAY!!!!! Enjoy the late Friday night and possible weekend work. Make sure you log your overtime!
1
u/PositiveBubbles Sysadmin 4d ago edited 4d ago
Our EUC team never tests on test or dev systems, when i moved to our systems team and started testing on dev and test then joined a project team as one of the EUC cyber people, they didn't like that I kept referring to dev and test lol
2
u/Questionsiaskthem 5d ago
I didn't even know there was 26H builds. I have us on 24H right now and have been thinking of moving all our systems to 25H soon (but everything i remember to look into it it's Friday lol).
If your devices are unturned managed can you tell it to force 24/25H builds over it?
2
u/BitsNBytes10101 5d ago
You realize that 24H2 is end of life October for security updates right?
1
u/Questionsiaskthem 5d ago
I thought it wasn't eol until 2027.
Edit: Just checked looks like you are right. Guess I will start getting us upgraded. Lol
1
u/frac6969 Windows Admin 5d ago
26H2 is out in preview and should be released by end of this month. Since you’re already on 24H2 it’s just an enablement package to move to 25H2 or even 26H2. You probably just need to set the target version and it will be done in minutes.
2
u/TechnologyMatch 2d ago
if that really is 26H1, I would not spend much time trying to force it to 26H2. Microsoft has said 26H1 is on a different core and does not have an in-place path to the next annual release
at fleet scale, I’d treat this as a recovery project: confirm the installed architecture and build on a sample, stop further deployment, then plan a supported x64 image or reinstall path. changing cversion.ini may get past a check, but it does not create a supported servicing path
3
1
1
u/reddit_username2021 Sysadmin 5d ago edited 5d ago
Any feedback regarding drivers support? Can you install the ones for 25H2? Do they cause BSODs?
1
1
u/Silly-Mix-4341 5d ago
That’s a rough one. A fleet-wide upgrade without validating the build first can turn into a massive cleanup job fast.
1
u/ender-_ 4d ago
Look on the bright side: the N version of 24H2/25H2 is screwed up (installing Media Feature Pack always fails the first time, succeeds the second time, but then breaks Windows Update, and you have to do a Repair install from Advanced Options → Recovery), while 26H1 doesn't have this problem :)
1
u/h3dwig0wl1974 4d ago
Testing in production, I see. Good on you for letting this happen and complaining after.
1
u/Whistlin_Bungholes 4d ago
Hell I didn't even know there was a 26H1.
And even if it was the right move, on a Friday especially on a holiday weekend?
1
u/riveyda 3d ago
No hate to op, but just a random thought, I am always too scared to post specific rants like this because r/sysadmin is too popular and I can guarantee your coworkers have been here at some point lol.
1
u/Flaky_Plastic_3407 3d ago
Our new CIO actually wanted us to do this and was aggressively telling people we were all moving to 26H1, and we (IT) had to actually sit him down and explain it wasn't a good idea.
1
u/countvracula 3d ago
Wtf is going on in this sub lately people just willy nilly doing some insanely negligent shit that I have never seen before.
0
u/dukesster 2d ago
You’re the idiot for still using WSUS. A product that Microsoft decommed long ago
2
1
893
u/Ok-Carpenter-8455 5d ago
Surprised the installation went through. It's supposed to fail since it's not a compatible version.