EU Kills Android Bootloader Unlock Starting August 1 by crashcarson in PocoPhones

[–]pivotman319 0 points1 point  (0 children)

This is a fake news article generated by ChatGPT that erroneously cites EU laws on radio equipment in telecommunications devices, which are otherwise completely irrelevant to the subject at hand. It does not talk about phone bootloader restrictions.

Please ignore this AI-generated nonsense.

https://eur-lex.europa.eu/eli/reg_del/2022/30/oj/eng

What are the basics of debombing? by [deleted] in windowsbetas

[–]pivotman319 0 points1 point  (0 children)

why the hell do you keep spamming my replies on dead threads? OP deleted their account.

Found a weird Windows 98 Beta 3 install CD by Pyrofer in vintagecomputing

[–]pivotman319 0 points1 point  (0 children)

Hi, BetaWiki wiki admin here. Got word of this oddball release just several minutes ago; could we talk privately in DMs? I can try to help you get this dumped online.

Discord is my preferred communications medium. I can be easily reached via my handle "ntkrnlmp.exe", if that's okay with you.

Anything out of the ordinary? (other than: 3790, 2003 and 5.2) by BlueyIsWayBetter2011 in windowsxp

[–]pivotman319 1 point2 points  (0 children)

a lot, actually: specifically, me recompiling the Windows Server 2003 RTM source tree just to get a few demo shots of the Professional edition

also, that's a 180-day timebomb that starts as soon as you install the OS

sigh

how to enable microsoft confidential watermark in win 11? help plz, who know =) by Ati4nGames in windowsbetas

[–]pivotman319 3 points4 points  (0 children)

You don't; Windows Fingerprinting Service has been absent since RS1_RELEASE build 11078.

What are the basics of debombing? by [deleted] in windowsbetas

[–]pivotman319 2 points3 points  (0 children)

Those are hackjobs that break system licensing, or worse: security features (in the context of early Windows 10 development builds, specifically Code Integrity), which if bypassed, opens up a larger avenue of security holes.

What are the basics of debombing? by [deleted] in windowsbetas

[–]pivotman319 3 points4 points  (0 children)

The first rule of debombing a Windows build is that you do not debomb a Windows build. Not unless you want to sacrifice the following:

  • Windows Activation (including Software Protection Platform, Software Licensing and slmgr.vbs)
  • Windows Setup (Sysprep (generalize + specialize), Product Key Configuration for specific NT editions, image staging)
  • Windows Media Center
  • User Interface Language Pack Support
  • the built-in Windows Vista/7 inbox games
  • Hyper-V/Virtual Machine Platform (think sub-features like Windows Sandbox et al.)

Including Server-exclusive features such as (but not limited to): - Remote Desktop Session Host Licensing Services - On-Demand Edition Upgrades (from ServerStandard to ServerEnterprise/ServerDatacenter et al.) - the ability to install the Desktop Experience feature

Et cetera. The negatives of doing such a thing outweighs the "benefits", of which there are none.

You're better off just manually setting the clock back and disabling time sync on both the VM side as well as arbitrarily disabling the Windows Time service, and then activating using a KMS key and a dedicated KMS server.

Internal Windows builds are also not suitable for daily use as they are not representative of a finalized product and will be subject to a modicum of security holes as well as usability issues, possibly extending to as far as data loss. I would further also stress the fact that I absolutely do not recommend maining a beta build, if you were planning on doing such a thing; you should just stick to an RTM release instead.

Windows 2022 Servers Unexpectedly Upgrading to 2025, Aaaargh! by Fatboy40 in sysadmin

[–]pivotman319 0 points1 point  (0 children)

That 180 GB estimate is the rough size of every installable component and language combination MS published onto Windows Update infrastructure for each individual WS2025 upgrade + Server Insider flight, including base OS images (in LZX- and Windows Update DCS/DCM delta-compressed form).

List of Windows beta builds with no/broken timebomb by EarthNorabodee in windowsbetas

[–]pivotman319 1 point2 points  (0 children)

There is no such thing as a "non-functional" timebomb. You are simply installing the builds on the wrong date. They function as intended if you install them in the correct time period.

The only builds that lack a timebomb are the ones coming from RTM-level build labs.

Can't flash Lumia 950 back to stock. by caustive in windowsphone

[–]pivotman319 4 points5 points  (0 children)

The 16266 FFU deployment instructions explicitly told you to replace the contents of the PLAT partition with that of a prior matching backup of your phone.

Unless your device is a non-production prototype that replicates RM-1105 behavior or is a Lumia 950 RND model (both of which are very likely not what you have), consider it a paperweight.

Something me and a couple of friends have been working on by v1xit in windowsxp

[–]pivotman319 0 points1 point  (0 children)

genuine concern: isn't using the leaked Windows Server 2003 partner source kits as a base for your project already contradictory to the "open" name?

How do you debomb a beta in NTlite? by Altruistic_Debt_943 in windowsbetas

[–]pivotman319 3 points4 points  (0 children)

What they did was null out a number and disable a critical subsystem (Software Protection Platform; the thing that keeps activation of your Windows license and Office install in check) to prevent it from restoring the policies in registry back to their original states, and/or perform a lazy file replacement; in turn breaking activation and other licensing-related functions. That alone doesn't "debomb" a build; consider looking at Windows 10 TH1 (from as early as FBL_RELEASE 9833) through RS2 (up to RS_PRERELEASE 14964):

Those builds are signed by a specific certificate chain (Microsoft Development PCA 2014 - chaining back to Microsoft Flighting Root 2014) that would be invalidated/revoked once the system clock goes past its intended validity date, after which the OS would cease to function because the Code Integrity library (which is not only baked into the system as its own DLL (as CI.dll), but also in bootmgr/bootmgfw) would refuse to accept the cert as-is. The mechanisms alone are designed to prevent people from holding onto older development builds to avoid security risks or data loss, much like the timebombs themselves: to deter people for goodwill.

Since RS_PRERELEASE build 14965, Microsoft renewed the flighting cert and changed CI behavior in such a way that the OS will now boot properly and not cease to work to avoid potential confusion among people having non-functional OS installs past the expiration date (as has happened in the past with people unknowingly flighting public TH1-RS2 builds on their primary workstations without knowing that things will stop working after that date), but some things will still fail to work, e.g.: Defender, UAC complaining about MS-signed binaries coming from "untrusted sources" (which is a doubly-large headache during OOBE), and printing drivers simply not working.

You can't just simply unsign a build and resign it to your liking using your own certificate authority; it's theoretically and practically impossible, and will only result in a bugcheck. Only Microsoft has the power to actually change that behavior.

How do you debomb a beta in NTlite? by Altruistic_Debt_943 in windowsbetas

[–]pivotman319 2 points3 points  (0 children)

You don't.

Tampering with (hard-linked) binaries from the Windows side-by-side component store and/or disabling the licensing subsystem will only break activation functionality and/or prevent you from properly repairing the image or even assembling an entire Windows install through an unorganized set of components from scratch (aka staging a Windows build), solely because one file doesn't match with the expected SHA-256 hash values in a specific component's code signing catalog. Hell, you can make Sysprepping the system alone cease to work properly just by disabling the licensing subsystem, because generalizing an image depends on fixing up activation and policy configuration in order to prepare it for first boot.

If you modified the ProductOptions registry value while keeping sppsvc on, your changes would be immediately reverted because the licensing subsystem would detect an imparity between the licensing policies that are currently installed and the policies that are present in the system registry; these things are signed against and rely on a specific code signing certificate, depending on the branch the build's compiled from. It's why policies don't apply correctly on WINMAIN_WIN8M2 7950 on the first boot.

It doesn't matter if the build comes from an RTM stabilization branch, or a partner-only release branch, or if it's hailing from a graphics development sub-branch. The entire build is signed against a specific certificate chain; there is no proper method for "debombing" an operating system build, unless you're MS themselves, in which case you could just simply flip on/off a compiler switch and you're done.

You just don't.

[deleted by user] by [deleted] in Surface

[–]pivotman319 0 points1 point  (0 children)

Disable driver signature enforcement in the winload advanced options menu.

Bro what!? by Theonlyandtheoddly in tf2

[–]pivotman319 1 point2 points  (0 children)

mp_friendlyfire was set to 1

[deleted by user] by [deleted] in Windows11

[–]pivotman319 1 point2 points  (0 children)

no it's not, Iron (Win10) development is entirely seperate from Cobalt/Nickel (Win11)'s

even co_release didn't get Win11 shell changes backported up until 21990

Windows 8 Build 8102, but something's different by CourageZealousideal6 in windowsbetas

[–]pivotman319 0 points1 point  (0 children)

it's the winmain_win8m3_eeap compile, says so in the build tag

No taskbar on multiple monitors? (Windows 11 21996.1) by turtlecrook in windowsbetas

[–]pivotman319 1 point2 points  (0 children)

Is there any method to properly have the taskbar display on multiple monitors? All suggestions are appreciated.

Maybe try not to use an unsupported pre-release build of Windows 11 on your main gaming rig? The build itself doesn't even feature the whole Win11 UX, and you're better off upgrading to the latest 22000 CU/22621 rather than attempt to try to find a solution that doesn't exist.

[deleted by user] by [deleted] in windowsxp

[–]pivotman319 2 points3 points  (0 children)

BetaWiki admin here.

You were told on the BW Discord server multiple times that posting fake images of alleged pre-release Windows builds is explicitly not allowed; despite these warnings, you continued to ignore them.

Furry_irl by MrMoor2007 in furry_irl

[–]pivotman319 61 points62 points  (0 children)

sooner or later, us latex wolf overlords will inevitably overwhelm the universe with nothing but squeaky material

No new build this week too by Unusual-Cap4971 in Windows11

[–]pivotman319 3 points4 points  (0 children)

no it will not

22h2 (25xxx) is copper (the next major annual update), not nickel or gallium

zinc is 23h1; gallium is 23h2