# Running Installer on Windows 10

**URL:** <https://community.localwp.com/t/running-installer-on-windows-10/6780>\
**Category:** Support\
**Tags:** local-classic\
**Created:** [June 5, 2018, 9:02pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780 "2018-06-05T21:02:05Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![aqi](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@aqi](https://community.localwp.com/u/aqi)\
**Post date:** [June 5, 2018, 9:02pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/1 "2018-06-05T21:02:05Z")

</div>

Does the Windows Local installer require an account with administrator privileges?

Or can it be run from a non-administrator account with “run as administrator” checked?

I tried the latter and it seemed to work ok. But a couple of days later, I tried to start Local, but the EXE file that starts it disappeared, so the desktop icon failed.

FYI I prefer to run day-to-day with a non-administrator account for security purposes.

---

<div class="post-metadata">

**Author:** ![neilh](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/neilh/32/3954_2.png) [@neilh](https://community.localwp.com/u/neilh)\
**Post date:** [June 6, 2018, 8:47am UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/2 "2018-06-06T08:47:02Z")

</div>

Same issue here. Installation of Local on a secure network is a complete nightmare. Would appreciate some input and advice from the Flywheel crew on this very subject! Oh, and if you do install with temp admin privileges, then revoke them and return to being a “standard” user, every time you create or delete a site in Local, you still need admin privileges to amend the HOSTS file (via node.js request).

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [June 6, 2018, 2:57pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/3 "2018-06-06T14:57:39Z")

</div>

> [@aqi](#):
>
> Does the Windows Local installer require an account with administrator privileges?

Local can run without administrative priveledges. If it needs to escalate something you will receive a UAC prompt while running Local. Like @neilh said, you’ll commonly see this when the `hosts` file needs updated or when installing Local.

> [@aqi](#):
>
> But a couple of days later, I tried to start Local, but the EXE file that starts it disappeared, so the desktop icon failed.

I can’t think of any reason why this would happen outside of Local’s files getting removed somehow. Does `local-by-flywheel` still exist in `%LocalProgramFiles%/Programs`?

* * *

> [@neilh](#):
>
> Installation of Local on a secure network is a complete nightmare.

Can you describe the issues you are running into?

> [@neilh](#):
>
> you still need admin privileges to amend the HOSTS file (via node.js request).

This is intentional and it works similarly on macOS.

---

<div class="post-metadata">

**Author:** ![neilh](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/neilh/32/3954_2.png) [@neilh](https://community.localwp.com/u/neilh)\
**Post date:** [June 6, 2018, 3:06pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/4 "2018-06-06T15:06:35Z")

</div>

@clay The issue was around there being no guidance as to HOW we should implement Local on a secure network. We’ve had to find our way in the dark, but we appear to have got there, esp if the HOSTS admin requirement is a deliberate feature of the product. In which case I guess we can live with that. However, one thing we noticed - like @aqi - is that the install _disappeared_ if Local was installed using elevated privileges, then the user logged out, elevated admin privilege was then removed, and finally the user logged back in as a standard user. Next day the Local install had disappeared. We’re currently testing an alternative approach whereby we remove the admin privilege _during the same elevated session_ as the install. It _seems_ to have fixed this bizarre behaviour, but time will tell…

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [June 6, 2018, 3:12pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/5 "2018-06-06T15:12:01Z")

</div>

> [@neilh](#):
>
> However, one thing we noticed - like [@aqi](https://community.localwp.com/community/u/aqi) - is that the install _disappeared_ if Local was installed using elevated privileges, then the user logged out, elevated admin privilege was then removed, and finally the user logged back in as a standard user.

Aha, makes sense! Local’s installer will install per-user. When right-clicking on Local’s installer and running it as an administrator, it’s not installing it into the current user’s `%LocalAppData%` folder.

Long story short, you should never have to use “Run as Administrator…” with Local including installing it. If you do, let us know and we’ll look into why.

---

<div class="post-metadata">

**Author:** ![neilh](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/neilh/32/3954_2.png) [@neilh](https://community.localwp.com/u/neilh)\
**Post date:** [June 6, 2018, 3:30pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/6 "2018-06-06T15:30:20Z")

</div>

Hi @clay we tried the right-click method, and that didn’t work. Hence our frustrations. The install that disappeared was the second approach whereby we granted the user elevated admin privileges, they then logged in (as a de facto admin), installed Local, logged out, admin privileges for that account were removed, and then they logged back in as a standard user. The next day the Local install had disappeared. Removing the admin privilege during the same session (rather than getting them to log out first), _seems_ to have resolved it. But we’ll keep an eye on it.

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [June 6, 2018, 3:43pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/7 "2018-06-06T15:43:42Z")

</div>

Got it. I really appreciate all of the details!

When you tried right-clicking and running as administrator, was this the installer/setup or Local after it had been installed?

Do you remember what happened? Would it simply not open?

---

<div class="post-metadata">

**Author:** ![neilh](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/neilh/32/3954_2.png) [@neilh](https://community.localwp.com/u/neilh)\
**Post date:** [June 6, 2018, 3:48pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/8 "2018-06-06T15:48:54Z")

</div>

The right-click approach installed Local in the localadmin user folder tree, so then we tried giving permission to these folders to the user, but that just threw up other issues, which I think included an inability to download and install WordPress? Certainly when running Local as an ordinary user, Local couldn’t detect and display the WordPress version being used in VirtualBox. Bit vague, but we quickly ditched that approach, so details are a bit sketchy.

---

<div class="post-metadata">

**Author:** ![clay](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/clay/32/8248_2.png) [@clay](https://community.localwp.com/u/clay)\
**Post date:** [June 6, 2018, 3:50pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/9 "2018-06-06T15:50:55Z")

</div>

Aha. I don’t blame you!

One last question for now, did you ever try installing it without running the setup as an administrator?

Thanks again for all of the info.

---

<div class="post-metadata">

**Author:** ![MarkBuskbjerg](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/markbuskbjerg/32/8801_2.png) [@MarkBuskbjerg](https://community.localwp.com/u/MarkBuskbjerg)\
**Post date:** [November 3, 2019, 8:55am UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/10 "2019-11-03T08:55:07Z")

</div>

> [@clay](#):
>
> Long story short, you should never have to use “Run as Administrator…” with Local including installing it. If you do, let us know and we’ll look into why.

Should I interpret this as “I don’t need to have admin rights to install Flywheel”?

I can’t install without getting admin rights on my computer. And it is kinda of a big deal to have in my organization. I can have it for like 30 minutes at a time and only if my teammanager grants it first. So being able to do this without admin rights would sure be nice!

I need to grant admin rights for a change to Microsoft Visual C++ 2015-2019 Redistributable - or something like that.

Is there a guide to installing without admin rights?

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\
**Post date:** [August 25, 2020, 6:34pm UTC](https://community.localwp.com/t/running-installer-on-windows-10/6780/11 "2020-08-25T18:34:41Z")

</div>


