Tripredacus

This function is browser based, not on the OS. In Firefox (at least) I think that if you ever put No or Never after logging into something it will not let you go back to being able to save it in the future. You may have to look into your saved logins list in the browser and clear the negative option from the list.

The flood control change did exactly what we wanted it to. It wasn't going to stop people from making posts. The only way to prevent the new accounts from making those spam posts was to prevent all members from being able to make any posts. That is the reality of what features are available in the forum software. Having to deal with hundreds instead of thousands is a good trade off. The expectations and function of flood control has nothing to do with the usability of the forum from a regular person's viewpoint, it is solely to assist Moderators in dealing with the situation on the back end. In the future, do not OTSP about these types of things in tech threads. Make a thread in this section instead.

Flood control disabled.

You can do it. I install the nVidia Control Panel in audit mode then run Sysprep and it is fine. But I do it with a .cmd file that runs on ComSpec, not Powershell. But it depends, some Appx authors do not make their Appx the way MS wants them to, and can't be used. I have run into one Appx that a client sent to me that did not install properly, but Windows gave different errors that indicated what they needed to do. It could be that the one you tried has some hard-coded things in it that mean it wouldn't work from Audit Mode. You can try using an XML with system and put FirstLogonCommands in oobeSystem phase to install the appx when a created user account logs in for the first time.

To build an image with a provisioned Appx. When in Audit Mode, you have to make sure that the OS never connects to the internet. That means does not open the Store or even install updates. Doing so can and will corrupt the "Administrator" profile on the system. In reality what happens is that when you are in Audit Mode, some of those actions write to portions of the Administrator profile, which Sysprep deletes and re-creates. This is why those particular things can cause the OS to become undeployable, particularly apps.

Flood control enabled for users in the Members group. Sponsors and Developers are not effected by this change. If you are a Sponsor or Developer and get a message from the forum saying you cannot post, send to me a PM and I will take a look. Also make sure to not report all posts that a spammer makes. One of their posts is fine. You may not even have to report any of the posts during this current situation as we are going to be checking more often.

It is something that our ancestors have nothing to relate to. I'm sure there are a lot of people in the 90s that didn't think that the internet would last this long.

I can no longer tell whether or not Windows 11 is popular. Before EOL for Windows 10 I could tell that Windows 11 was in the vast minority. That is always the case when a new OS comes out, but there seemed to be an even greater drop-off than in previous years. It is possible that the sales focus has shifted. I have taken exactly zero support calls on Windows 11 which is saying something considering how long it has been available. Then again, there also hasn't been any surge in the IOT side of things, which was a trend in past OS releases where a client will want to stay on the old OS that can't be sold. The same people that are buying IOT now are the same ones who just have the qualified devices that were getting it before.

It is done.

Merged. Do not create duplicate topics.

I'm not particularly interested in cloud gaming as it is, forgetting multiplayer already having issues with server latency that has a real effect on games, putting it into cloud doesn't actually help that. Of course, the companies who do make these services are not interested in this experience or preservation, only to make a buck. So for ported titles (aka things on PC or console already) there is no no big whoop about it. When it comes to exclusive things, that is where the problem lies. There are games that were on the Gaikai platform before Sony bought them that are lost forever. Some of them have physical client versions that are unusable. All online only or required titles have this same fate eventually, they will get lost to time or be unusable at some point.

The link posted above does not fully encapsulate the URL leaving off the locale part, and it seems like that site default to German (de) if the locale is not used.

That is the application level, not the OS level.

Webp being such a terrible idea, how about any methods to block it at the OS level, no matter what browser you are using? Since as I am reading, the WEBP vulnerability is not limited to Chrome or even Windows.

Retroarch has MAME cores.

Are you able to post on MSFN from this Puppy computer or are you using something else?

I presume it is to show ads. For Nexus (the modding site) it is to show you the donation message.

Manual quoting works of course. I guess I was being lazy.

I quoted the MS quote in your post. Unlike previous versions of IPB, you can't change the text on the quote bar. I was adding to that text, not necessarily replying to you. :p

I doubt it has anything to do with Windows. The EFI bootloader hands off to Windows and I'm fairly certain that Windows itself is agnostic to which bootloader was actually used. Especially since Windows is not an EFI application, it is still just the same x86 or amd64 binary that the bootloader chains to no matter which bootloader is being used. The previous example I gave relates to nothing that Microsoft or Windows does, but rather how firmwares can not follow the spec. Whereas BIOS can't boot an EFI Application because it doesn't know what it is, UEFI is supposed to only boot EFI applications. Obviously there are various situations where you can boot a legacy bootloader under UEFI but this is not by design. I'm also not sure whether or not the firmware or the bootloader even cares about the disk type. I don't think enough testing has been done to actually conclude whether or not MS is telling the truth about what actually works vs not, regardless of what they support.

I was under the impression that the white screen at startup was due to Google trying to install an update that was previously downloaded. Back when Chrome was supported on Win7 I would see this every day I opened the browser, but since there are no more updates, it just opens right away.

Testing reputation limits in place for regular members. No restrictions for sponsors.

I can see why, As it says in the bottom "The current filter excludes all 216,001 events". As is common with procmon, the target PID is not always the one that you need to filter for. Things I can see in the PML: - two missing DLLs (api-ms-win-core-fibers-l1-1-1.DLL, api-ms-win-core-localization-l1-2-1.DLL) of course these are the internal names. I do not know what actual file the launcher is looking for. There are others that are better at decoding these than me. - three files the launcher can't find (doesn't mean they aren't present, but the error could be caused by something else. All of these are in the game folder) : petromod_nvidia_profile_identifier,ogl, oculusmedium.exe, aurora.dll The above errors do not seem to impact the application launching, so they may be normal to see when this game launches. There is also a series of "INVALID DEVICE REQUEST" errors from Steam itself. I do not think it is related but this Result is not one I have seen. It may be normal for Steam to do this, I also have not tried to Procmon Steam before so it might be normal. Steam reports this while attempting to access Drive C: Unfortunately, Procmon doesn't seem to catch or indicate anything. Svchost calls faultrep.dll at 7/26/2023 05:51:17.3827742 immediately after mcclauncher crashes but there is no indication as to why that program has crashed. Interesting that later WerFault.exe (the process that ends up writing the event log you found) also cannot find the core-fibers DLL. Looks like Windows may have made a .dmp file for the crash here: C:\Users\CalmCreeper360\AppData\Local\CrashDumps

I'm not sure it is on MS that this happens. I think it is a combination of the specification as well as whether or not the firmware manufacturer is compliant with it. There is still the interesting case of the Intel NUC with a specific (now lost to time I imagine) BIOS version that allowed booting Win7/8 on MBR disk on UEFI with CSM disabled. I don't think the OS has anything to do with it. Maybe the bootloaders in Win10+ changed to put a block in to do what you say. But in any case, it is not the norm that you can boot MBR under UEFI that is for sure.

The annoying part of Malwarebytes is the first month after install where it bugs you constantly about sending them money. I don't like active solutions because of the overhead, the fact that it tries to be active by default is annoying also.