The trick, William Potter, is not minding that its sh*t.Yup. One ends up banging their head up against a brick wall constantly my friend, and for what?
So, I'll install the sh*t, live with the sh*t, and that's it lmao.
Last edited:
The trick, William Potter, is not minding that its sh*t.Yup. One ends up banging their head up against a brick wall constantly my friend, and for what?
So, I'll install the sh*t, live with the sh*t, and that's it lmao.
Done several tests across the .431 .440 .450 builds, in VMWare, and have come to the conclusion that deleting/disabling anything on each, results in no performance gain whatsoever, and breaks system, unless one is careful, but updates, (unless you have this thing banished from the net?), will restore most of the hard work one has done to circumvent anything, although not all.
Funnily enough?, a gain was noticed in the system performance when all was left untouched??, albeit minor, WTF!!?? lol.
If you really must run this sh*t, then I recommend just installing as it is, bypassing the MS Account (if you so wish), then just uninstalling whatever afterwards. (Quite surprised how many it let me uninstall) Disable services etc., and turning off what you don't want running, and leave it be afterwards. This system breaks very easily, and at the slightest thing removed, and I suppose that is the way MS designed it to be?
I do wish to stress, that my post is not just about 'performance', but rather about the time we now take, and care, to not allow this crap to consume us all? It was merely an info post to say that, despite all we may try, then I have (myself) come to the conclusion that 'its just is not worth the effort', to waste what little time we now have in this world, to fight against the unwinnable, aka, disabling this and that, or removing this from there.
Yeah I totally feel your pain. I just put in 20 hours total today and yesterday, and made no progress on my issue either. It sucks big time when things end up being out of your hands.
if that's what makes you guys happy, then more power to you, but allow me to offer my counterpoint.So, I'll install the sh*t, live with the sh*t, and that's it lmao.
Telemetry is important for big companies now a days. They need information and that information is very valuable. There is a reason why they decided to make windows free for this exact reason.if that's what makes you guys happy, then more power to you, but allow me to offer my counterpoint.
It was never about performance, at least to me. All that telemetry, all the data breaches, all those software blocked from being installed, its just a byproduct of an attempt to shift public's perception from 'its mine to use it as I see fit' to 'I can use it and that is enough', just like it is with cloud gaming, streaming services and the like. But consider for a moment how all the big tech companies collect telemetry, yet keep pushing features no one wants and getting rid of things that work and are used (and if you think its just microsoft, check out the Hangouts vs Google Chat threads on the net) just because its what THEY (and that's a vague, faceless mob of suits) think its best.
Sorry but I refuse. The moment I cannot Lite Windows to a point I feel satisfied anymore is the moment after I'll never use it, even knowing I'll probably lose 'features' on that deal. Just like I refuse to use cloud gaming. I do not trust big tech companies with my data nor do I want them telling me what I should or should not watch or listen to. Microsoft is especially guilty of this as they've been collecting a LOT of telemetry and yet, as noted, taking all we use and like in windows and force-feeding crap down our throats at every chance they get. So once again, NO. I'll put all the time and effort needed to have control over my data and especially, keep my privacy.
That's where I draw the line, and I believe if more people would stand on this line with me, we could pressure them to change for the better.
Which would probably be fair enough, if they actually 'listened', and 'acted' on what that telemetry was telling them. They don't though, as they remove/add, and fail to fix what really needs fixed, regardless of what the end user wants, so what's the point?There is a twist in this though, they also wanted to know what customers wanted out of there operating system and the only true way of getting that is through telemetry.
22H2's Entitlement release hasn't been enabled, so the real UI changes won't leak out until Fall.Has anyone by chance tried out the W10 version of the 22H2? I'm curious how much of W11 they're bringing over to W10.
A: Money.Which would probably be fair enough, if they actually 'listened', and 'acted' on what that telemetry was telling them. They don't though, as they remove/add, and fail to fix what really needs fixed, regardless of what the end user wants, so what's the point?
I totally agree, but @ 60 years of age nearly, lol, I'm tired of beating the dead horse, and fighting to get what I think is right. I'm running this garbage now, with what I know I can remove, but it's only inevitable before I can't even do that, and I'm not prepared to waste whatever time I have left on this planet? fighting a losing battleA: Money.
B: Control
C: Both.
That is the exact reason I'll make as hellish for them to get my data as I feasibly can.
So what’s the trick? Understanding how OOBE is structured is a good first step. It’s a UWP app called CloudExperienceHost, written in JavaScript and HTML (with some native code hooked in). You can find the JavaScript and HTML source files in C:\Windows\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy. While you could probably hack that up, that wouldn’t be supported. But during the execution of that app, it needs to display the terms of use web page (and other web pages, e.g. the Azure AD sign-in flow, OOBEAADV1). How does it do that? By embedding an HTML IFRAME into a page being hosted in the UWP app’s web view. That web view is based on Internet Explorer (which will never fully die).
But then how do we retrieve that value later? Understanding how the web view works is key to that. The Internet Explorer engine running inside the Cloud Experience Host app does it’s normal storage “stuff,” but instead of writing to the user’s IE storage location, it writes to an app-specific location.
Maybe at some point the Cloud Experience Host app will switch from using a WebView to instead using a WebView2 control. If that happens, then it will use the Chromium way of storing local data, which will break the PowerShell scritp. I’m guessing we won’t need to worry about that any time soon.