BetaWiki:Community portal

__NEWSECTIONLINK__

Addition of Xbox development pages
I know this sounds silly, but Xbox is a part of Microsoft and I just feel like we should add Xbox into our software family, What do you guys think? Beta Kiwi 02:34, 4 January 2022 (UTC)

I agree, except I know basically nothing about Xbox, but I still think it should be added. Boa (talk) 20:04, 10 January 2022 (UTC)

I also agree with this idea, there could be some completely new and fascinating concepts such as beta versions of the home menu redesigns. Though, I don't think there are many leaked beta builds of the Xbox development. (IIRC it's Windows 10 under a lot of wrappers and different UI, because of the rs_xbox tag, again I might be wrong.) As said before, past histories and development that is not mean to be seen by the public is really interesting for me. Byronbytes (talk) 19:02, 2 March 2022 (UTC)

What is the first Windows 8 build to remove the classic built-in Windows Games?
Remember when older versions of Windows before Windows 8 had built-in games that you could play like Solitaire, Minesweeper, FreeCell, 3D Pinball, Purble Place etc.? When Microsoft was developing Windows 8, the company wanted to incorporate an app store into the operating system to stay competitive in the drastically changed technology space. However, Microsoft decided to completely scrap the classic versions of these games and instead create Modern versions of these games that are bloated with ads. The classic games may have been removed during Windows 8's development at some point.

What build of Windows 8 completely removed the classic Windows Games? Anyone know what build it was?

WindowsGuy2021 1:43, 7 January 2022


 * The first available build that removed games is 8102 (both EEAP and non-EEAP). User:WindowsServerFan (talk) 20:09, 7 January 2022 (UTC)

User sub-pages
Anyone knows how to create the User sub-pageS?


 * https://lmgtfy.app/?q=user+namespace+mediawiki --AhmadB (talk) 15:43, 10 January 2022 (UTC)


 * Do you mean like This? Beta Kiwi 00:45, 12 January 2022 (UTC)

Different Wiki themes when on specific pages
Ok quick idea

what if when we gone on a random page (Ima say Windows XP because it is a well known one), the theme would change

and what I mean by this? You know when you launch the wiki your greeted by a light blue area, which resembles the watercolor theme fron whistler builds in 2000-2001

But, what if these would change once you gone on a specific page

Such as Windows 7 having lets say maybe a whistler theme but under an areo background, Windows XP would contain a luna-colored area as well as (maybe) one of the animated windows flags in the corner (like xp had), Windows 95 builds would have a gray area due to classic theme not being updated yet

tbh this idea is really stupid but i wanna hear your guyses ideas too.

ty for reading this

-Beta Kiwi 00:55, 12 January 2022 (UTC)

Another silly idea
ok we should add easter eggs (small secrets) in main menu -Beta Kiwi (my signature is still being loaded) 02:52, 12 January 2022 (UTC)

Boot screens #2
Should we remove boot screens and replace them with animated ones? Because no one decided to awnser the first one, I decided to do a part two, what do you guys think? - Beta Kiwi 23:34, 12 January 2022 (UTC)

Edit: I meant that no one decided to support/oppose it

Support

 * 1) Go to User:Beta Kiwi/Whistler2428 to See a preview of it StartbuttonLogo 95-ME.png Beta Kiwi  23:34, 12 January 2022 (UTC)
 * 2) Sounds cool, maybe it could be a setting? Boa (talk) 15:39, 16 February 2022 (UTC)
 * This is not going to be a thing since the user who posted this got blocked and most of users are opposing this idea. But something might change when supporters exceed opposers and Admins change their mind. I won't use this username anymore. I'm going to change it to "XPSrv" on June 4th 2022 (talk) 16:25, 12 February 2022 (UTC)

Oppose

 * 1) A "no" is a "no". -- 23:37, 12 January 2022 (UTC)
 * 2) 😸 Hi. I'm SamCool939. (💬 | 👨‍💻) 23:41, 12 January 2022 (UTC)
 * 3)   Check again, several people made comments on your first Boot Screens post. Xeno (talk) 23:45, 12 January 2022 (UTC)
 * 4) Why? Kendrenogen (talk) 23:47, 12 January 2022 (UTC)
 * 5) Tons of people responded to your last post, so you stating otherwise is a complete lie. Anyway, there's no reason to replace the boot screens with animated ones as the latter is enough to get the point across. Jurta (talk • contribs) 23:50, 12 January 2022 (UTC)
 * Just because people didn't put their responses in the corresponding support/oppose sections does not mean they didn't support/oppose it. Jurta (talk • contribs) 09:54, 13 January 2022 (UTC)

The Purge™️ #2: Purge List
As we plan to conclude the purge proposal amended earlier, I have provided a list of pages that will be purged in one of my sandboxes. Do note that not every page listed on there might be deleted; I just listed those that has a high chance of getting deleted. Alongside, pages that aren't listed here but are deemed non-notable might be subject to deletion once the purge starts. If you have anything important you want to keep, you better back them up to a sandbox or external source.

EDIT: It is unknown when the purge can occur until a bureaucrat gives a finalized time for it but I prefer if there is at least a one week grace period since the posting of this message for other users to get everything backed up before purging. At latest, I would expect it to be done in February or early March.

BF10 (talk) 16:19, 15 January 2022 (UTC)


 * This is just myself being curious, but why haven't you chosen to add the  category to your list? Xeno (talk) 16:14, 21 January 2022 (UTC)
 * They do have notability in terms of important websites towards preserving beta-related software. Only the more important ones were kept (UX.Unleaked since most LH build screenshots came there and BetaArchive because it preserves most of the betas documented here). I doubt any new website pages could possibly be notable enough to be added here. BF10 (talk) 16:26, 21 January 2022 (UTC)
 * So your basically deleting the entire wiki besides pc? KFC (talk) 01:01, 2 February 2022 (UTC)
 * This again, do you all seriously want risk this wiki? And some corrections, FreeBSD, GhostBSD, NomadBSD and OpenIndiana aren't Linux Distros, yes, it's the same family, but they aren't Linux, OpenIndiana is SVR4 and the rest is BSD family. --Vannura (talk) 21:10, 3 February 2022 (UTC)

Question
I'm just wondering, when does this page get put into the next archive? Boa (talk) 14:47, 29 January 2022 (UTC)

I don't think they will do it for some time as some people are replying to some other topics. TechActivate 781 (talk) 17:06 29 Januray 2021 (UTC)

Okay, thanks! Boa (talk) 21:14, 31 January 2022 (UTC)

How can I become an autocomfirmed user?
Hello! I am wondering how I could become an autoconfirmed user! I have some images for Windows Storage Server 2003 R2 and I am unable to upload screenshots at The Upload Page, Thanks -Windows2022 (talk) 23:45, 3 February 2022 (UTC)

You need 10 edits and to be registered for 3 days I think 82.219.7.150 09:45, 4 February 2022 (UTC)

Curious about macOS Sierra 16A271f
Hi, New contributer here. I couldn't find and gather enough evidences to conclude macOS Sierra 16A271f build was actually rolled out to public(developers). Googling the build number only returns two relevant results, one of them being some sketchy Geekbench result, which for all I know could be for internal testing at Apple, and another one being here at BetaWiki (which only fuels my suspicion). This is quite an anomaly even considering it's a minor hotfix to a beta build, since most (if not all) of the time when you google the build number returns at least one forum thread from somewhere which references it in some form. I thought I might have to discuss it here before I commit to erasing the entry. LPFchan (talk) 16:53, 7 February 2022 (UTC)

What is going on with The Windows Insider Dev Channel?
It has been over 2 weeks since Microsoft released an new build in the Dev channel. (The latest build is Windows 11 build 22543 as of this writing.)

Last week, I remember Microsoft announcing that there would not be an new build for that week because the build that they were apparently testing did not meet quality standards so, it was not eligible to be released in the Dev channel.

It has been a week since Microsoft announced the changes that were coming to the Insider Program this year and there has not been any updates on The Windows Insider Blog as of this writing.

I have heard that Microsoft will be preparing to sign off the Nickel (22H1) Semester in the next few weeks and next month, Insiders will start receiving builds from the Copper (22H2) Semester.

I am not an participant in The Windows Insider Program but, I do check this website periodically every Wednesday and Thursday to see if the latest builds have been documented which I have been doing since I first discovered this website in early 2021.

Hopefully, Microsoft will release a new dev build next week if it does meet the quality standards to be released to Insiders. It is likely that it is a new build of Nickel since we have a few weeks of February left.

So, we may receive 2 more Nickel builds within the next 2 weeks since Microsoft will not sign off the 22H1 Semester until early March.

WindowsGuy2021 1:51, 10 February 2022
 * Basically they're doing a semester transition (Nickel > Copper) that's causing a hefty amount of issues, they did just do a huge build skip from 22554 to 25054, after all. Jurta (talk • contribs) 19:59, 10 February 2022 (UTC)


 * Yeah, I may have heard something about that somewhere. When were builds 22554 and 25054 complied? Is this the first time that issues occurred as they started a semester transition? Did they have that problem when they transitioned the Dev channel from Cobalt to Nickel in September 2021? WindowsGuy2021 2:10, 10 February 2022
 * 22554 was compiled on 7 February 2022 and 25054 was compiled a day later on 8 February 2022. Not sure if these issues occured when they transitioned from Cobalt to Nickel, or any other transitions for that matter. Jurta (talk • contribs) 20:20, 10 February 2022 (UTC)


 * Finally, Microsoft has released a new build of Windows 11 in the Dev Channel! Turns out it is indeed an Nickel build. Microsoft has also released an new build of Windows Server as well. It is apparently the first build of Windows Server based on Copper.

The new build has many changes which could explain why it took 2 weeks to release this build to Insiders in the first place. It even has an change where the Pro SKU requires an Internet Connection during OOBE. (Although, it is possible to bypass the internet connection requirement using an workaround.)

I think that Nickel (22H1) is getting very close to being signed off and we will start receiving client builds based on Copper (22H2) in early March 2022.WindowsGuy2021 2:46, 16 February 2022

Update: Microsoft is getting ready to transtion the Dev channel to the Copper semester. (22H2) WindowsGuy2021 2:39, 6 April 2022

Update 2: Well, some of the information that I typed here has now aged very poorly as it has been revealed that Nickel is 22H2 and Copper is 23H2. WindowsGuy2021 12:13, 21 April 2022

Well.. They finally moved the Dev Channel to Copper.. [[User:Cliria|Cliria]}

Regarding Windows 11 build 25054
Aren't tweets regarded as not a good source for build tags? If so, then why do pages for Windows 11 build 25054, both  and , exist when the source for both of them isn't a proper source? Jurta (talk • contribs) 10:18, 11 February 2022 (UTC)
 * Seems like nobody's going along with this, added prods to both pages. Jurta (talk • contribs) 18:14, 11 February 2022 (UTC)

Dark theme
I would like to have dark theme in Betawiki because when I use my computer for more than 2 hours, Light theme becames bad.


 * What would it even look like? (I use dark mode for most things, but the normal theme is fine for me) 90.155.76.234 21:19, 11 February 2022 (UTC)
 * I think a dark blue on background with some black-to-cyan (a light black i think?) on foreground (with a White Text, obvious), but is just my opinion. --Vannura (talk) 22:36, 11 February 2022 (UTC)
 * That'd be cool, I hope that gets added. Boa (talk) 19:27, 14 February 2022 (UTC)

Removing non-preinstalled game articles
To simplify down the earlier purge to remove less relevant material, I believe that we should remove most of the game articles that are not pre-installed in the operating systems from this wiki. As mentioned in the previous proposal, they aren't notably edited as often as most of the operating system pages (most of the articles in the category hasn't been edited in years and have deletion proposals running for them) and the scope is too wide to allow all games here. As a result, we should reconsider that most of the game articles aren't notable enough to be kept here compared to more suited wikis such as The Cutting Room Floor and Hidden Palace. As mentioned earlier by Orbitron on the original proposal:

"The game articles (that aren't Windows games) are relatively useless as well, great example being the legendary Create with Garfield article, which has since been deleted, as there's Wikipedia pages for many of these already, and The Cutting Room Floor and The Hidden Palace exist for this wiki's exact scope, but obviously for games instead."

No other operating system or application pages will be removed for right now; only most of the non-preinstalled game articles will be removed. This would mean everything in Category:Games except for Full Tilt! Pinball (included in Windows 95 Plus!/98 to XP) and Reversi (two versions included from Windows 1.0 to XP). Articles such as Minesweeper, Solitaire, and Chess (both the Windows Vista/7 and Mac OS X versions) would also be allowed as long they are based upon the pre-installed versions included in builds and not third-party games. Everything else can otherwise be ported to the aforementioned two wikis. BF10 (talk) 15:47, 23 February 2022 (UTC)

Support

 * 1) As already mentioned, there are far better wikis out there for game related content. Xeno (talk) 15:51, 23 February 2022 (UTC)
 * 2) This makes sense as this site is more geared towards operating systems and their betas. WaterMelon (talk) 00:48, 24 February 2022 (UTC)
 * 3) Boa (talk) 07:17, 24 February 2022 (UTC)
 * 4) I fully agree. 90.155.76.234 21:32, 24 February 2022 (UTC)
 * 5) We should definitely remove these because while we do cover betas, games have more suitable wikis. However, we should keep noteable OS'es and apps that have an ammount of betas. For example: the iPhone wiki barely does a good job at covering betas, as the pages are mostly just firmware key pages, not about the OS. Orangera1n (talk | edits)
 * They've already been removed.Xeno (talk) 17:28, 15 March 2022 (UTC)

Windows Vista Build 5212
The BetaWiki page for Windows Vista build 5212 says that there is a new option called "Run Elevated" in the right click menu. But I saw this feature in build 5112.TechActivate 781 (talk • contribs)

Insults on your Discord Server
Just asking. I don't care about you swear or not anymore. I'm totally OK with that. But I'm wondering why insulting people is allowed on your discord server while it's not allowed on website? XPSrv (talk) 16:42, 28 February 2022 (UTC)

Help me
The wiki edit summary is autofilled. I keep inputting the same summary, how I can disable it? Eg. If I type "P" it shows "I see some glimpse of an appearently an wallpaper, and I'm not sure that it comes with Win7.". I am using Firefox, and autofill for addresses are disabled. It is extremely annoying and it causes misleading/confusing results. Even setting  to the text area doesn't seem to help. It is very annoying. Help me! Eg. If I add a new unleaked Windows 8 build eg. build 7970 (that build is just a example) then I save my edits with "I see some glimpse of an appearently an wallpaper, and I'm not sure that it comes with Win7." instead of "Adding an unleaked build from example.dll in the build 7850 tools."

Office 2007 Themes
Where are the themes of Office 2007 that are in pictures? I saw it in BetaWiki at some point, but now it's gone. TechActivate 781 (talk • contribs)

Proposal: accounts must be created by admins for new users.
I have been noticing vandalism like every other day, primally for new accounts. I think this could reduce vandalism by a lot as people would need to contact an admin to create their account. We can have a email address for that, and a temporary password and username is given. I also think that non-autoconfirmed users should have their edits moderated as well, because of the uptake in vandalism from new accounts. Orangera1n (talk | edits) 11:16, 30 March 2022 (UTC)

Support

 * 1) OK. What is the email adress for this? - 105.105.18.57

Oppose

 * 1) I Completely DISAGREE - 154.121.66.132
 * 2) Too much effort for such a small gain. Not worth it Xeno (talk) 13:04, 1 April 2022 (UTC)
 * 3) Good idea, but it probably wouldn't work. Boa (talk) 07:40, 3 April 2022 (UTC)
 * 4) I don't think the vandalism problem is bad enough to warrant something like this, since there are enough people here that any vandalism gets promptly reverted anyway. -- Jb881122 (talk) 12:36, 4 April 2022 (UTC)
 * 5) 😸 Hi. I'm SamCool939/NekoSam395. (💬 | 👨‍💻) 08:37, 5 April 2022 (UTC)
 * 6) Sorry, but this idea is Idiot and Absurd. --Vannura (talk) 17:32, 7 April 2022 (UTC)
 * 7) People can just contact an admin for an account and then pursue their vandalism. This is not going to do anything other than waste people's time. Jurta (talk • contribs) 17:36, 7 April 2022 (UTC)
 * 8) I withdrew. Orangera1n (talk | edits) 21:11, 7 April 2022 (UTC)
 * 9) A captcha can prevent spams as well, and letting admins to create users will add unnessary burdens to admins.--GT610 &#124; Sorry for my poor English! (talk) 05:51, 8 April 2022 (UTC)
 * 10) Honestly this idea is not that bad, but I'm 95% sure that the admins don't really want to wasting their time on this. • Kiki79250CoC (Talk • Contribs • My Toaster™ specs) 06:22, 8 April 2022 (UTC)
 * 11) This idea wouldn’t solve anything. IP addresses can still edit pages, so this would really just cause a huge amount of accounts not being created. This is one of the reasons BetaArchive Wiki had so little documentation for a while. -Meow (talk) 01:26, 10 April 2022 (UTC)

GitHub References
While some builds that are mentioned on GitHub come from more than one repository and fall under the acceptable notability guidelines. I believe that the majority are not notable as they just say "Hey, this build exists!", only consist of a build number and don't mention any notable bugs or features. Not to mention that I feel that these build pages clog up their respective OS version pages. Given that most Win10/Win11 updates have recently been removed, I feel like these references should follow suit. Especially since right now, Copper is around 45% GitHub references.

I think there are three potential ways forward: These are just some thoughts I've had over the last few days. Xeno (talk) 21:14, 7 April 2022 (UTC)
 * 1) Delete and disallow most build references that come from GitHub (This would be extremely unfair)
 * 2) Move the references to a separate page and potentially format them into a table as seen on my sandbox. Table Sandbox (The table is just a personal preference)
 * 3) Keep things as is


 * I think the second option you suggested is the most appropriate solution. It serves to mention that we know these builds exists without having a page for each of them. (I also think this idea can be extended to other "unnotable builds" as well, just a list to reference their existence). • Kiki79250CoC (Talk • Contribs • My Toaster™ specs) 06:15, 8 April 2022 (UTC)

I want to create pages!
Please, let me create pages! --PrelevatedInsider (talk) 10:53, 10 April 2022 (UTC)
 * Why? What pages do you want to create? Jurta (talk • contribs) 10:57, 10 April 2022 (UTC)
 * My user page and every non-existent pages! --PrelevatedInsider (talk) 12:42, 10 April 2022 (UTC)

I want my custom Userpage and Sandbox!
I want these to tell others about me and for testing BetaWiki features and my editing skills with condition that nobody will ever touch the page. --GoldieAxolotel1320 (Talk) 14:40 Apr 10 2022 GMT+01:00 Warsaw
 * You're copying my message! --PrelevatedInsider (talk) 12:57, 10 April 2022 (UTC)
 * I need this too! --GoldieAxolotel1320 (Talk) 15:09 Apr 10 2022 GMT+01:00 Warsaw
 * Same. --Vannura (talk) 14:42, 13 April 2022 (UTC)

Deprecate The Use of The Term "Development Semester"
I don't think Nickel and Copper should be called the 22H1 and 22H2 development semesters, respectively, given that Microsoft has most likely switched to a yearly-based development cycle rather than semester-based with recent internal mentions of Windows 11's 23H2 release being Copper. Some may argue that the development semester is not related to the version number, but it would be very awkward as we get further and further into the future when development semester and the version number diverge (for example, Gallium would be either 23H2 or 25H2). Therefore, I think we should stop using the term "development semester" after Nickel. Charka123 (talk) 00:25, 11 April 2022 (UTC)
 * I honestly agree 100%. Imagine the mess in the near future once we reach 2024 or 2025! Cliria (talk)
 * Well, they are called development semesters for a reason... The 22H2 development semester is for the 2023 release, aka 23H2. Same also applies for 22H1, being called 22H2 instead of 22H1. --Icanttellyou (talk) 09:05, 13 April 2022 (UTC)
 * We can't do much until Microsoft confirms that themselves. It's likely we'll just keep it the same until we have enough proof whether Microsoft did switch to development cycles from development semesters. Jurta (talk • contribs) 16:25, 13 April 2022 (UTC)

About 22H2.
Now that it's basically confirmed that Nickel is 22H2 and Copper is 23H2?. What's next? How are development semester gonna be like in the future now that Microsoft only plans to launch one major update per year. Cliria (talk •

Make a document about the 22H2 builds
If Nickel released a Build then the 22h2 doesn't have that build. So, if make a document, once we plus that build in Nickel, the 22H2 will have this build too. 2001:f90:40c0:a072:5189:e019:ae56:b207 09:20, 11 May 2022 (UTC+08:00)

I cannot find the dll files for Windows Fax and Scan even when using Resource Hacker!
Turns out that Windows will not let you open certain dll files because these are protected operating system files. For example I tried to open the actual Windows 10 icon for Sync Center but, it would not let me open it in Resource Hacker. I tried to find the icon for Windows Fax and Scan and even after copying the following directory file path of %windir%\system32\WFS.exe and pasting it into the breadcrumbs bar, it would not let me in. Some programs have easily accesible dll files but programs like Sync Center and Windows Fax and Scan have their dll files buried in protected system files that it makes it hard to easily extract their icons.

Can you please give me some advice of how to work around this? I am trying to do this so I can add the real icon to my newly created Windows Fax and Scan page.

WindowsGuy2021, 4:56, 21 April 2022
 * You can use "Icon Viewer" by Bot Productions. I used Windows 7's Windows Fax and Scan and uploaded it because I'm running Windows 11 Insider Preview builds and Microsoft removed Windows Fax and Scan from System32. TheMinecraftHunter (talk) 17:00, 22 April 2022 (UTC)

My computer runs Windows 10 version 21H2, not Windows 7.

Where can I download Icon Viewer?

WindowsGuy2021, 12:11, 22 April 2022
 * You can get it here. ToMi (talk) 17:39, 22 April 2022 (UTC)

Why is the font different now?
For some reason. The Font has changed to be smaller and more zoomed out Cliria (talk •
 * JaGoTu upgraded MediaWiki to 1.3.7 give it some time to iron out the kinks. Xeno (talk) 12:53, 25 April 2022 (UTC)
 * Ah.. Aright Cliria (talk •

IP User contributions was broken!
The IP user Contributions is broken on my iPad 4 The broken place. It will says "Bad username givenCannot look for contributions without a user or with a user that does not exist.". Is JaGoTu upgraded this? 2001:F90:40C0:C165:31C8:8D04:B69D:C959 08:30, 26 April 2022 (UTC)
 * He upgraded MediaWiki to 1.3.7. Anonymous editing as 197.202.105.211 09:06, 29 April 2022 (UTC)
 * Yes, but I say "The IP user Contributions is broken on my i..." 2001:f90:40c0:a072:685b:71cc:9ad:fff 02:45, 30 April 2022 (UTC)

More Vandals.
A brand new month. More vandals that will appear.. Why can't we have a month without these vandals ruining everything? Cliria 13:29, 1 May 2022 (UTC)

Where can you find the Install.Wim file in a Windows installation?
I just want to know where you can find Install.Wim in any version of Windows. Is the file located in ISO images of various Windows versions online? What if I need a icon for a program that does not exist on Windows 10 version 21H2 (The Operating System my laptop runs) but want to still find high-quality icon images.

I know that you can extract the Install.Wim file and can use Resource Hacker to locate icons that you can't really find elsewhere withen the Windows OS.

What if I want to extract the icons for the Universal Windows Apps like Quick Assist, where are the icons for the modern apps in Windows 10 located at?

WindowsGuy2021, 4:03, 2 May 2022
 * The  is inside the sources folder of the installation image. You can open it with tools such as 7-Zip. - 88.67.241.20 (talk) 21:34, 2 May 2022 (UTC)


 * For UWP apps, you can check the  folder, although the   folder is hidden and you will need to take ownership of it to access it on your own Windows install. You could also access it through   as well on a Windows ISO. Windows OS (talk) 22:30, 2 May 2022 (UTC)

Okay, where can I locate the sources folder to find my install.wim file? I tried to gain access to the WindowsApps folder but, it won't let me in and I tried to change the owner of the folder and did not do anything. Can you tell me how to exactly take ownership of the folder?

WindowsGuy2021, 7:13, 2 May 2022
 * The sources folder is located at the root of the install media. For the permissions, you already know what to do. --Nara Insider (talk) 15:14, 3 May 2022 (UTC)

What happened with the servers?
In the last few days, I received multiple HTTP 502 host errors when accessing this site. Was something bad happened there?
 * Yeah, the wiki is currently targeted by DoS attacks. Stuff like this simply happens on the Internet from time to time. We'll see what we can do but don't really worry about the downtime. -- 12:51, 4 May 2022 (UTC)
 * Wait for JaGoTu to fix that. 105.111.109.145 15:51, 7 May 2022 (UTC)

What happened to the main page?
I tried to go to the main page, but then it showed that they have to check my browser before I can access betawiki.net. But when it redirected, it's still the same. Did something terrible happened to betawiki.net? TheOfficialJJPM7984 (talk) 00:04, 12 May 2022 (UTC)
 * I have that protection too.
 * That's just Cloudflare's DDOS protection checking your browser, it's nothing to worry about. Xeno (talk) 00:07, 12 May 2022 (UTC)
 * If you have problems accessing BetaWiki due to this Cloudflare DDoS protection system, you can access any page other than the main page, since only the main page is affected from the DDoS protection. - 212.23.130.206 (talk) 07:50, 12 May 2022 (UTC)

24H2?
Now with the Dev Channel having been moved from Nickel (22H2) to Copper (23H2). It's fair that I create the 24H2 page? Cliria
 * Why? It's not like there is any information about it... -- 10:46, 12 May 2022 (UTC)
 * Nevermind.. I will just wait until we starting getting information. Cliria 10:53, 12 May 2022 (UTC)

Purging Vibranium (Win10 2004 thru 21H2) and Cobalt (Win11) update pages
To reduce clutter throughout each Windows version's build pages (from VB onwards), I'm holding a vote here to see if anyone's fine with getting rid of the unnecessary update pages for the above mentioned Windows versions, as they do not have any notable changes. The only pages that will be kept (as they feature significant UI changes) are the following:

Vibranium

 * Windows 10 build 19041.329
 * Windows 10 build 19041.423
 * Windows 10 build 19041.962
 * Windows 10 build 19042.608
 * Windows 10 build 19042.844
 * Windows 10 build 19042.962
 * Windows 10 build 19042.1023
 * Windows 10 build 19043.1023
 * Windows 10 build 19044.1499
 * Windows 10 build 19044.1618

Cobalt

 * Windows 11 build 22000.282
 * Windows 11 build 22000.466
 * Windows 11 build 22000.526
 * Windows 11 build 22000.588

Let me know what you think about these proposed changes below. - pivotman319 (📫) 18:11, 12 May 2022 (UTC)

Support

 * 1) Agreed, we should only cover the ones with notable changes. -- 18:12, 12 May 2022 (UTC)
 * 2) I agree, there is no reason to have pages of builds that don’t contain anything important. WaterMelon (talk) 18:22, 12 May 2022 (UTC)
 * 3) Three's a trio. I'm in favor as there are a ton of unnoteworthy builds and removing some of the update builds is a great start. Xeno (talk) 18:23, 12 May 2022 (UTC)
 * 4) As the one who began the whole post-GA thing, I fully agree with this. Jurta (talk • contribs) 20:07, 12 May 2022 (UTC)
 * 5) Boa (talk) 20:51, 12 May 2022 (UTC)
 * 6) I agree, many of the post-GA builds of Vibranium and Cobalt are nothing more but security updates and quality updates that fix bugs and security issues and they clog up the build lists for those pages. It only makes since to cover post-GA builds that have actual notable changes like the ones listed above. WindowsGuy2021, 3:59, 12 May 2022
 * 7) I'm pretty sure I have proposed long time ago that any Update RTM builds wouldn't be allowed here (aside from service pack betas and build 6003). Many if not all of these pages deserve to go, otherwise it'd be cluttered with over thousands of pages of Update RTM builds. BF10 (talk) 01:15, 13 May 2022 (UTC)
 * 8) Nara Insider (talk) 11:31, 13 May 2022 (UTC)
 * 9) Kendrenogen (talk) 16:30, 13 May 2022 (UTC)

Who the hell are running those vandals
They are all saying the exact the same thing with the same shit over and over again. It's almost like.. they are just one person abusing bans most likely. Cliria

Purging of cumulative updates of betas (Only for Manganese and up)
I think we should purge all of the cumulative updates of betas in post-20H1 Dev Channel as they do not contain any useful content as well as notable changes. I meant all builds with these labs without notable changes: This proposal excludes all builds from 22000.51 to 22000.184.
 * rs_prerelease_flt
 * fe_release_svc_prod(1-3)
 * fe_release_svc_im
 * co_release_svc_prod(1-3)
 * co_release_svc_im
 * ni_release_svc_prod(1-2)

Oppose
I think it wasn't. Look into this one.
 * rs_prerelease_flt (from 20H1)
 * 18965.1005 (20H1): This build changes the version numbers for a few system components.
 * 18970.1005 (20H1): Nothing updates
 * 19551.1005 (Manganese): See Windows 10 build 19551.1005
 * 19564.1005 (Manganese): You must use an IDE or SATA hard drive if you want to install this build in VMware, otherwise the setup won't be able to find the drive.
 * 19608.1006 (Manganese): Nothing updates
 * 19613.1005 (Manganese): Nothing updates
 * 20211.1005 (Iron): Error update of build 20211.1000.
 * 20231.1005 (Iron): Nothing updates
 * 20236.1005 (Iron): Nothing updates
 * 20241.1005 (Iron): Nothing updates
 * 21292.1010 (Cobalt wave 1 Cilent): See Windows 10 build 21292.1000
 * 21292.1010 (Cobalt wave 1 Server): Only the update files of this build were released to Windows Update on 15 January 2021 alongside its client counterpart.
 * 21296.1010 (Cobalt wave 1): Nothing updates
 * 21301.1010 (Cobalt wave 1): Nothing updates.

And there some build like this lol. 2001:f90:40c0:a072:9aa:460c:a255:8787 19:40, 17 May 2022 (UTC+08:00)
 * 1) I wouldn't say all. Take 22581.100 for example. This "service pipeline" reintroduces tabbed File Explorer. Xeno (talk) 11:32, 17 May 2022 (UTC)
 * These can be excluded from this proposal. But rest of them doesn't seem that useful.

Restore Windows 11 build 22000.346 page
Restored as requested. - pivotman319 (📫) 14:04, 13 June 2022 (UTC)

I don't understand why the page for build 22000.346 was removed as a part of getting rid of post-GA update pages. It actually had some notable changes, including the redesigned fluent emojis and changes to the BSOD color. Some of the pages that had fewer changes were actually kept, such as 22000.282 (which only contained minor tweaks and adjustments) and 22000.526 (only added Microsoft Account page in Settings). Considering that these two post-GA updates were kept, I think 22000.346 should stay too. Charka123 (talk) 20:24, 17 May 2022 (UTC)
 * Yeah, at least unleaked post-GA updates should stay.