Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Multiple problems #803

Closed
1 task done
dennbenn73 opened this issue Oct 27, 2023 · 6 comments
Closed
1 task done

[Bug] Multiple problems #803

dennbenn73 opened this issue Oct 27, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@dennbenn73
Copy link

Steps to reproduce

  1. Downloaded and checked file integrity of prebuilt asset WSA_2309.40000.10.0_x64_Release-Nightly-MindTheGapps-13.0-as-Pixel-5-RemovedAmazon.7z
  2. Extracted archive to folder on C:\ of Surface Pro 9 (Core i7-1265U, 16GB RAM)
  3. Executed Run.bat but was not prompted with request for WSA administrative permission
  4. Opened Terminal (Admin) and executed PowerShell.exe -ExecutionPolicy Bypass -File .\Install.ps1 command

Expected behaviour

Executing Run.bat and/or Install.ps1 files should install prebuilt WSA as described by the instruction guide.

Actual behaviour

  1. Gapps was not installed.
  2. Subsystem resources are locked on 'Partially running' setting - cannot be adjusted to 'As needed' or 'Continuous' settings.
  3. Attempting to open WSA 'Manage developer settings' causes subsystem force close with permission error message: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item."
    permission_error

Windows version

11.0.22621.2506 (22H2)

Build Issue number

No response

Version requirement

  • I am using latest commit of WSA-Script commit
@dennbenn73 dennbenn73 added the bug Something isn't working label Oct 27, 2023
@github-actions
Copy link

We are checking your Issues body and head ...

https://github.com/YT-Advanced/WSA-Script/actions/runs/6670736570


@YT-Advanced
Copy link
Owner

YT-Advanced commented Oct 28, 2023

First, uninstall your installed build, then delete the extracted folder.
Next, extract again but with a short folder name, example: "WSA"
Install again (NOTE: Allow administrator request) and check back

@dennbenn73
Copy link
Author

There wasn't any request for Admin privilege during the either installation attempt. I have shortened the folder name, and was given the same error message.
permission_error

I had the official WSA installed before; how do I know if the previous installation has been completely removed?

@YT-Advanced
Copy link
Owner

You can check if WSA still shown in Settings or Control Panel. And also go to this path and delete it %LOCALAPPDATA%\Packages\MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

@dennbenn73
Copy link
Author

dennbenn73 commented Oct 28, 2023

I think I am looking in the correct location C:\Users\denn_\AppData\Local\Packages\ and I didn't see any folder named MicrosoftCorporationII.WindowsSubsystemForAndroid_8wekyb3d8bbwe

Windows 11 is a permissions nightmare.

EDIT:
Here is what else I have tried:

  1. Decrypted drive and disabled Bitlocker.
  2. Installed 'Take Ownership' registry file and used on all WSA files before and after installation.
  3. Made sure that I am system adminstrator by opening Terminal (Admin) and running these two commands:
    PS C:\Users\denn_> $currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
    PS C:\Users\denn_> $currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
    True

@s1204IT
Copy link
Collaborator

s1204IT commented Apr 30, 2024

Please install the latest version.

@s1204IT s1204IT closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants