BetaWiki:Community portal


Early Windows RT builds[edit source]

Recently, we got a number of Windows 8/RT builds in a very short timespan, that are very similar to Windows 7, especially 7792. I would like to simply ask what can be done with them at their current state other than just testing them, like, would some software run on them? Can these builds make WinRT devices more useful, faster or more pleasant to use, for example by patching DWM? I know they're older than regular RT. AlfCraft07 21:49, 2 September 2024 (UTC)

So far, they can't be ran on Windows RT devices due to the fact that drivers don't exist for the surface RT tablet in these builds. Abc123 (talk) 22:32, 2 September 2024 (UTC)
they can run now, including 7822 2001:F90:6019:A8F7:D451:CA17:D53F:99D8 12:17, 11 September 2024 (UTC)

Username change request[edit source]

im requesting a name change to ZacharyFDS. can someone pls do so Discrim5958 (talk) 12:14, 11 September 2024 (UTC)

Staging Windows builds[edit source]

All the recently leaked ARM Windows 8 builds' images come unstaged, and thus they are missing important Windows files, even explorer. To build the full image, it needs to be staged, but my question is, how do you do it? I searched on the internet, but wasn't able to find anything, so I would give a huge thanks to anyone who tells me how to do it. AlfCraft07 10:52, 12 September 2024 (UTC)

Follow these steps:
1. Mount the unstaged image
2. Create a XML file to install the image:
3. Run these commands respectively:
DISM /image:<mount-dir> /apply-unattend:<path-to-xml-file> /logpath:<optional-logpath>
DISM /image:<mount-dir> /add-package /packagepath:<path-to-lp.cab>
4. Commit and unmount WIM.
5. Done

XPSrv (talk) 11:01, 12 September 2024 (UTC) For XML image:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing>
        <package action="install">
            <assemblyIdentity name="Microsoft-Windows-PlaceHolder1Edition" version="PlaceHolder2" processorArchitecture="arm" publicKeyToken="31bf3856ad364e35" language="neutral" />
            <source location="D:\packages\PlaceHolder1.mum" />
        </package>
    </servicing>
</unattend>
Sorry, but where do I find the language pack CAB to install? This XML didn't work, so I used the Ultimate one included with the image. AlfCraft07 12:40, 12 September 2024 (UTC)
Lp.cab is under \langpacks\en-us\. Also you are supposed to edit XML values. For example Ultimate for PlaceHolder1 and 6.1.7792.0 for PlaceHolder2.

XPSrv (talk) 12:42, 12 September 2024 (UTC)

Oh ok. Does it matter if I used the one already included with the image? AlfCraft07 12:44, 12 September 2024 (UTC)
What do you mean by already included with the image? XPSrv (talk) 12:46, 12 September 2024 (UTC)
By "already included in the image" I mean the Ultimate.xml inside the "packages" folder of the unstaged WIM. AlfCraft07 13:01, 12 September 2024 (UTC)
That's a different Ultimate.xml file with different content. So, nope. XPSrv (talk) 13:02, 12 September 2024 (UTC)
I discarded the old image, and tried to stage it all over again with your XML code, changed accordingly. DISM gives error 32 (file is used by another process). What can I do to fix it? The MUM file the XML links to is the one inside the packages folder inside the WIM. AlfCraft07 17:14, 12 September 2024 (UTC)
Nevermind, I was able to apply the unattend file by flashing the WIM to a VHD first. Time to install! AlfCraft07 19:09, 12 September 2024 (UTC)

Ok, so I was able to stage the build as I said earlier, I was finally able to create boot files and create a VHD with 7898. I added the necessary settings modifications with BCDEdit (from the guide for build 7915) but, when booting with Disable Driver Signature Enforcement, it loads the Loading Windows Files screen, but then just locks up. Did I do anything wrong? AlfCraft07 19:38, 12 September 2024 (UTC)

If you didn't get any error during staging image, it must be a build-specific bug and I'm unable to help on build-specific errors. Sorry about that. XPSrv (talk) 19:46, 12 September 2024 (UTC)

Yeah, after flashing the WIM to a VHD, everything went smooth as butter. What kind of configuration was needed by build 7792 after staging?

I used roughly the same batch file as 7915 to run this build. AlfCraft07 19:56, 12 September 2024 (UTC)

About -bootloader %BL% ^[edit source]

I am trying to install build 7822 of windows 8. the command is working well until the qemu-system-arm part where if you put the command in if will give you an error. is there something I am supposed to add something there? — Preceding unsigned comment added by 2601:600:8E80:D330:3DC0:39F1:596C:44E9 (talkcontribs)

You need to change the path of %BL% according to the location of your firmware file. Otherwise it will (obviously) throw out a “no such file or directory” error because that BL variable is targeting a nonexistent path/file. AlfCraft07 04:52, 23 September 2024 (UTC)

can I get a little example? — Preceding unsigned comment added by 76.146.36.211 (talkcontribs)

Where is your HARMONY.fd file located? AlfCraft07 20:28, 5 October 2024 (UTC)

in the fw file — Preceding unsigned comment added by 76.146.36.211 (talkcontribs)

a little help[edit source]

hello, it's me again, can a get a little example for the command for 7822? this is the command i used yesterday: qemu-system-arm ^

   -M tegra2-qemu -m 1G -accel tcg,thread=multi ^
   -bootloader %BL% ^
   -device usb-tablet,id=mouse -device usb-kbd,id=kbd ^
   -drive if=sd,index=1,format=vpc,file=%SETUP% ^
   -drive if=sd,index=0,file=%MAIN% ^
   -serial null -nic none ^
   -s ^

do I use the file "BOOTMGR.EFI" as the bootloader? and is this a good iso? here: Windows 8 build 7822 (ARM32) : Microsoft : Free Download, Borrow, and Streaming : Internet Archive — Preceding unsigned comment added by 76.146.36.211 (talkcontribs)

About Windows 10 builds[edit source]

how come you guys aren't adding the windows 10 Cumulative Update Preview builds like 19045.4894 — Preceding unsigned comment added by 76.146.36.211 (talkcontribs)

That's a security bugfix for CVE-2024-38014. Featureless CUs don't deserve a place on the wiki per previous community consensus - hell, it's even listed as such in our guidelines. - pivotman319 (📫) 22:58, 24 September 2024 (UTC)

VMware Workstation crashing my system when starting VMs.[edit source]

At start, i used VMware Workstation (version 10 at the time), it was working completely fine, and then after i upgraded it (to version 12.5.9), it also works, but at one day, when i tried to boot the VM, the system (not the VM) crashes with a bugcheck code PAGE_FAULT_IN_NONPAGED_AREA (may have caused by GenuineIntel). Do you have any suggestions on how to fix this, but i want to keep the VMware Workstation version 12.5.9 for virtualizing Windows Longhorn builds. Thanks.

—— This newly signed comment was added by Windows logo (2012).svg Lazytown Sportacus (LazytownSpo4015)Talk page 02:26, 7 October 2024 (UTC)

How do I create a proper watercolor.css?[edit source]

I have gotten tired of seeing this Watercolor.css, so I want to make my own using a very green looking Watercolor with the BW logo as used on the Vector Legacy (2010) theme. Shams1917 (talk) 20:01, 12 October 2024 (UTC)

You can start with making the User:Shams1917/watercolor.css page and making edits. You do need some CSS experience though, needless to say. Try looking at other users watercolor.css for some ideas. BF10 (talk) 23:50, 12 October 2024 (UTC)

Help with build 4042[edit source]

Can I get help running Windows longhorn build 4042 on vmware? I am trying to install build 4042 but after the VM is set up The boot screen just loops what should I do

— Preceding unsigned comment added by Benthewindowsfan (talkcontribs)

i also has this in 4053 2001:F90:6017:D673:1935:BDDD:DA24:DCF4 11:32, 21 October 2024 (UTC)
Hey man you should try changing the date to one inside the timebomb(smash the f2 button when starting up to enter bios) then exit and save — Preceding unsigned comment added by dvdoodd77 (talkcontribs) 20:04, 10 December 2024

Usage of <code>[edit source]

It is starting to seem very clear that people here will always use <code> instead of <code style="word-break: break-word"> for reg files, even after the many pages edited with this change. I have changed multiple pages to use <code style="word-break: break-word"> instead of <code> and I thought people would learn, but turns out that is not the case. How do we make this usable at times when there is a registry file or a really long directory? 37.39.146.11 03:46, 21 October 2024 (UTC)

I appreciate your effort but I don't think expecting people to add the style just because you added it to a bunch of articles is reasonable. Not all people understand CSS and it can be time consuming to look up the attribute to get it right. In fact, the idea that any contribution done in good faith is a good contribution and there is no expectation to "learn" is the very nature of wikis - anybody can come and add information, and if it doesn't look the best, more experienced editors will come and improve upon it. Anyway this is something that should really go to MediaWiki:Common.css rather than be added inline to each code block. --Ryuzaki (talk | contribs) 09:42, 21 October 2024 (UTC)

Windows XP supports amd64[edit source]

The chart https://betawiki.net/wiki/Microsoft_Windows#Supported_platforms here under Supported Platforms suggests that Windows XP does not support amd64, but thye made a specific build called x64 edition — Preceding unsigned comment added by Myth (talkcontribs)

If you had botherd to check the note list, you would know that it's referring to the original release from 2001 only, and the fact that the AMD64 release is just a version of Windows Server 2003 with XP branding and whatnot. Degrader (talk) 20:03, 23 October 2024 (UTC)
XP x64 is actually based on Server 2003. --Ryuzaki (talk | contribs) 20:41, 23 October 2024 (UTC)
Then why are XP and Server 2003 not one entry? Since Server 2003 is based on XP and the other server releases are merged with their home counterparts, they should be merged. — Preceding unsigned comment added by Myth (talkcontribs)
Because Server 2003 has a newer codebase and xpclient branch forked from main branch after build 2522. After that,changes in Server 2003 line were reverse-integrated into main line and the main line build number jumped to 3xxx.— Preceding unsigned comment added by Ephedra (talkcontribs)

Arm7 QEMU emulation[edit source]

Please can anyone provide me with the tegra2_qemu emulator as I need to emulate Windows RT. — Preceding unsigned comment added by SomerandomWindowsguy (talkcontribs)

A download link together with all the necessary tools and a guide are included in every Windows 8 ARM build's page. AlfCraft07 11:59, 26 October 2024 (UTC)
Well I meant a compiled set of tools not the source code. — Preceding unsigned comment added by somerandomWindowsguy (talkcontribs)
If you’re on Windows, they will just work. You need to compile the Tegra2 QEMU only if you’re running macOS or Linux. AlfCraft07 09:07, 27 October 2024 (UTC)
Well can tou give it to me? — Preceding unsigned comment added by 2402:E280:3E2A:1CE:48AB:A21:D6E9:513B (talkcontribs)
As I said. Go to an ARM build's page. Open that Installation section and click the link. Oh nevermind, I understand now. To download the Tegra2 QEMU, go to Actions, select the first option. Click on Summary, and then download either the dynamic or static build (both will work). If you have a low resolution display I recommend the static build as the dynamic locks up in full screen. AlfCraft07 12:19, 28 October 2024 (UTC)

Suggestion: Add common pages for windows codenames[edit source]

basically, it's info about the development of the codename, the infobox has the image of the most popular build, its dev time (reset time also if needed) and other things. it can be the main source of info for the codename, including the features that were in the most builds but got removed in the release, and more, 1st common page to get added: longhorn. — Preceding unsigned comment added by 2600:1011:A115:3B92:6592:336D:F191:A8EA (talkcontribs)

List of Microsoft codenames literally documents every known Microsoft codename in the simplest way as possible. Additionally:
  • Adding these codenames does not mean we have truely found the origins of them. Codenames does not really have true origins in the past.
  • The Windows Vista page has already documented the Longhorn project and the reset. Making another page would just be useless whatever.
60.246.151.0 13:28, 31 October 2024 (UTC) — last updated 21:55, 31 October 2024 (UTC)

How much time is needed to upload a image to BetaWiki?[edit source]

I really want to know. As I am new — Preceding unsigned comment added by UsernameNotAvailable (talkcontribs)

BW:FAQ has the information 2001:F90:40A0:F84:58CB:553E:223F:6897 13:22, 19 November 2024 (UTC)

"Windows Insider Blog" rival[edit source]

In my opinion, putting official announcement in a separate external links section in Windows 10 and 11 pages is pretty weird and makes the page clutter. So, an WIB rival would be a nice addition, and it also helps shorten the page too.

—— Preceding SIGNED comment added by A150.png insomnia {{Ic fluent person 12 filled.svg talk Ic fluent list 20 filled.svg contribs Ic fluent mail 20 filled.svg email me }} | 15:58, 1 December 2024 (UTC)

First, I am not sure how it makes the page cluttered if it's literally in a separate section towards the end of the page. Not to mention "helping shorten the page" is not really a benefit, either. If anything, the rivals should be moved to external links since that's the common practice on other wikis. --Ryuzaki (talk | contribs) 16:34, 18 December 2024 (UTC)

Support[edit source]

  1. Per myself. —— Preceding SIGNED comment added by A150.png insomnia {{Ic fluent person 12 filled.svg talk Ic fluent list 20 filled.svg contribs Ic fluent mail 20 filled.svg email me }} | 15:58, 1 December 2024 (UTC)
  2. Cool Idea! I support this idea. Adrikikicp (talk) 20:21, 17 December 2024 (UTC)
  3. I also agree it is useful. TechActivate 781 (talk) 16:24, 18 December 2024 (UTC)

Oppose[edit source]

Recommended Windows 8 beta builds for daily use?[edit source]

I know there were a lot of Windows 8 betas leaked and shared after a month. But what build is recommended to install? My dad has a x86 Lenovo laptop going around, which means the build must have x86 architecture. - Leon — Preceding unsigned comment added by Leon (talkcontribs) 20:11, 17 December 2024‎ (UTC)

No builds from whatever (including Windows 10 / 11 Insider Preview builds) are suitable for daily use, they tend to be unstable and oldest ones might not work properly due to timebombs. But I reccomend you the build 8513 because it's close to the RTM (it's an RTM Escrow) or Developer Preview, Consumer preview or Release preview. Adrikikicp (talk) 20:20, 17 December 2024 (UTC)
to Adrikikicp - I can get a debombed Windows 8 beta iso or i can do the debombing manually. I would try your reccomendations on a VM to see which is the best, and then run Rufus and flash my ISO to my USB - Leon — Preceding unsigned comment added by Leon (talkcontribs) 12:33, 18 December 2024‎ (UTC)
I would say e- nvm i'm not gonna help someone who wants to main outdated betas 188.236.235.241
Build 9200 or 9600. -Degrader (talk) 15:18, 18 December 2024 (UTC)
I wouldn't recommend those builds as they are early in their development and potentially corrupt/destroy your device. -UsernameNotAvaliable
9200 and 9600 aren't early; they are the RTMs of Windows 8 and 8.1. TechActivate 781 (talk) 16:23, 18 December 2024 (UTC)
does 9200.16456 work properly? 60.246.151.0 22:13, 18 December 2024 (UTC)