Closed Bug 1465374 Opened 6 years ago Closed 3 years ago

Win10 loaners missing interactive features

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED INACTIVE

People

(Reporter: pmoore, Unassigned)

References

Details

Attachments

(1 file)

In bug 1458083 it was difficult for a user to gain elevated permissions due to several interactive features being disabled/broken.

1) It wasn't possible to view installed applications via the Start Menu
2) Right clicking the Start Menu didn't provide an option to open an elevated command shell.
3) Right clicking the Start Menu had a broken link to running Powershell (see screenshot).
4) Searching for an app from the Start Menu is broken/disabled.
looking at the screenshot, the error refers to a missing file in the task user AppData folder:

Z:\task_1527672240\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Windows PowerShell\Windows PowerShell.lnk

i wonder if the task user creation process is either missing some step that would copy the Start Menu folder from the default user, or perhaps the process that should do that simply needs more time to run after user account creation. i'm not sure which. it would need to be debugged by watching what happens after the task user account is created by the gw process.
I think the creation of the start menu items probably on first interactive logon of the user, rather than on user creation. My suspicion is that this file exists under C:\Users\task_......\Windows PowerShell.lnk instead. Perhaps the (internal Windows) process that creates this file does not respect the Known Folder locations of the user.

In other words, my guess is this is fallout from when we decided to move the APPDATA folder to the Z: drive.

Now we know how the base images are created, my guess is it would be better to set the system Profiles Directory to the Z: drive at OS installation time, rather than post installation. Perhaps this will solve it for us.

I haven't recently checked to see if this is still a problem, or was a one off.
(In reply to Pete Moore [:pmoore][:pete] from comment #2)
> I haven't recently checked to see if this is still a problem, or was a one
> off.

I just tested this and it was still an issue for me.

still an issue?

Not actively working on this at the moment.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: