talksr Posted January 29, 2025 Posted January 29, 2025 (edited) I have come across an issue on some of our 22H2 Win 11 systems. If a user attempts to install the 24H2 update, the system shows the following message: We couldn't install some updates using the account you're signed in with. Try signing in with another account. I am assuming this means the user doesn't have the correct permissions. Is there any way to get around this? I would rather systems are fully up to date than have to go around and log in as an admin to facilitate this. If I review the feature update policy within Intune for 24H2, it doesn't give me any options to allow non-admin accounts to install. The system in question is in a corresponding included group and 24H2 is set as ImmediateStart and Required update. Any suggestions would be greatly appreciated. Edited January 29, 2025 by talksr
Oaktech Posted January 29, 2025 Posted January 29, 2025 Is the device signed in to more than one account after a 'switch user' has been done? I've seen that message in that circumstance because Windows can't release files it needs because they're locked by another login? 1
talksr Posted January 29, 2025 Author Posted January 29, 2025 Is the device signed in to more than one account after a 'switch user' has been done? I've seen that message in that circumstance because Windows can't release files it needs because they're locked by another login? No, I have re-booted, no other users signed in. It is also doing it if I am signed in as admin which leads me to believe this is actually a system incompatible with 24H2 but rather than just say this, MS is giving this misleading message. If it won't even go on as admin user and nobody else is signed on, the message doesn't make sense.
mjhardisty Posted January 31, 2025 Posted January 31, 2025 Does your Feature Update include "When a device isn't eligible to run Windows 11, install the latest Windows 10 feature update" ticked? What happens if you do log onot one of these devices as admin and try to manually update it? 1
talksr Posted February 3, 2025 Author Posted February 3, 2025 Does your Feature Update include "When a device isn't eligible to run Windows 11, install the latest Windows 10 feature update" ticked? What happens if you do log onot one of these devices as admin and try to manually update it? Thanks for your post. It has this: Install Windows 10 on devices not eligible to run Windows 11=Enabled Actually, I have just editied it and it does have "When a device isn't eligible to run Windows 11, install the latest Windows 10 feature update" and yes, it is ticked. If I go on a system as admin, I get exactly the same error with a manual update.
mjhardisty Posted February 3, 2025 Posted February 3, 2025 Have you the ability to autopilot reset one and see if it rebuilds and updates itself?
talksr Posted February 3, 2025 Author Posted February 3, 2025 Have you the ability to autopilot reset one and see if it rebuilds and updates itself? Yes, I will initiate one before I go home and will have a look on Wednesday and see how it has gone. Will let you know the outcome.
talksr Posted February 5, 2025 Author Posted February 5, 2025 Have you the ability to autopilot reset one and see if it rebuilds and updates itself? It did the trick! How come?!
mjhardisty Posted February 5, 2025 Posted February 5, 2025 More than likely some issue with a recent update, or failed update or simliar that's prevented the upgrade. A good result though, just rebuild the troublesome devices! 1
talksr Posted February 5, 2025 Author Posted February 5, 2025 More than likely some issue with a recent update, or failed update or simliar that's prevented the upgrade. A good result though, just rebuild the troublesome devices! Ah ok. Thanks for the suggestion, that was something I would not have considered. The only thing that seems different is for some reason it has reinstalled with UTC-08:00 Pacific Time (US & Canada) time zone. I am assuming maybe that is something to do with the base Windows 11 image?
mjhardisty Posted February 11, 2025 Posted February 11, 2025 Yep, it'll probably take US time from the default langauge of the OS. You can change it on the OOBE in deployment profiles or via configuration settings (Configure Time Zone). 1
talksr Posted February 12, 2025 Author Posted February 12, 2025 Yep, it'll probably take US time from the default langauge of the OS. You can change it on the OOBE in deployment profiles or via configuration settings (Configure Time Zone). Just had a look on Intune, and it would seem the correct address is selected which is strange. If I go to Intune>Devices>Windows>Enrollment>Windows Autopilot Deployment Profiles, the OOBE profile has the following configurations: Hmm, strange.
mjhardisty Posted February 12, 2025 Posted February 12, 2025 Configuration setting is the way then, to fofce GMT.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now