Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #18026
| From | T <T@invalid.invalid> |
|---|---|
| Newsgroups | alt.comp.os.windows-11 |
| Subject | Re: OT: Win Server 2025 luafv error |
| Date | 2025-03-28 16:02 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <vs79pa$3hbdi$1@dont-email.me> (permalink) |
| References | <vrv0eu$3vqia$1@dont-email.me> <vrv1ud$24lc$1@dont-email.me> <vrv65r$3vqia$2@dont-email.me> <vs0bt4$1ae99$1@dont-email.me> <vs69gu$2shfd$1@dont-email.me> |
On 3/28/25 6:51 AM, ...w¡ñ§±¤ñ wrote: > Graham J wrote on 3/26/2025 12:54 AM: >> >> So who is the "software vendor" who prepared your server? >> >> > > This whole scenario looks like it is really related to 3rd party support > on a client device by installing Windows Server 2025(WS2025) due to: > - WS2025 not requiring(unlike Windows 11) TPM2/Secure Boot for installation > - WS2025 End or Support(Fixed Lifecycle policy) > -> Mainstream Support 2029, Extended Support 2034 > - UAC intervention(disabled) by the client or the 3rd party installer > > Fyi... > - if the client's device is an 'Enterprise' managed device - WS2025 > should, as of Mar 27 2025, be updated with KB5053656. > - if not an 'Enterprise' managed device and not updated with > KB5053656, it may be necessary to use GPO to deploy the recommended > rollback returning the device prior to the March 25th WS2025 update. > Hi Winston, "User Account Control: Run all administrators in Admin Approval Mode" Fixed the issue. Since the Point of Sale vendor ghosted me on whether or not they disabled it and if they still needed it, I presume it was 99% their doing. And that they disabled it becasue they got timed of pressing "yes" when they installed all their utilities. Thank you! -T
Back to alt.comp.os.windows-11 | Previous | Next — Previous in thread | Find similar | Unroll thread
OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-25 12:33 -0700
Re: OT: Win Server 2025 luafv error Graham J <nobody@nowhere.co.uk> - 2025-03-25 19:58 +0000
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-25 14:11 -0700
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-25 14:28 -0700
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-25 14:59 -0700
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-25 22:47 -0700
Re: OT: Win Server 2025 luafv error Graham J <nobody@nowhere.co.uk> - 2025-03-26 07:54 +0000
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-26 09:25 -0700
Re: OT: Win Server 2025 luafv error ...w¡ñ§±¤ñ <winstonmvp@gmail.com> - 2025-03-28 06:51 -0700
Re: OT: Win Server 2025 luafv error T <T@invalid.invalid> - 2025-03-28 16:02 -0700
csiph-web