Edge

Some time ago my copy packed up. The blue screen comes on for a few
seconds and then nothing. I have not bothered because I have others,
but is there a way to get it back?
--
Myth, after all, is what we believe naturally. History is what we must
painfully learn and struggle to remember. -Albert Goldman

On 1/26/2018 2:46 AM, Martin Edwards wrote:
Some time ago my copy packed up.Â* The blue screen comes on for a few
seconds and then nothing.Â* I have not bothered because I have others,
but is there a way to get it back?

I have no 3rd party menu so I'm doing this in the native mode:
I right click on menu/start button and then 'apps & features'
In the list is 'microsoft edge' click it and there is an 'advanced
options' to click.

Under that is both a repair and reset. That's my stab at it.

Martin Edwards wrote:
Some time ago my copy packed up. The blue screen comes on for a few
seconds and then nothing. I have not bothered because I have others,
but is there a way to get it back?

The instructions can change with which Win10 version you are using.

Right-click Start : Run and enter "winver" as a command.
The version tells you what you're running.

*******

For example, the latest release is 16299.xxxx and that
corresponds to 2017-09, aka "1709". Some people have received 2017-09 only
in the last few weeks (months after its official release), so it's not
necessarily a given that this new technique applies to you.

https://www.groovypost.com/howto/res...ndows-10-1709/

In 1709, MSEdge is a "regular App", which doesn't mean a
damn thing to me. There is a GUI with Reset and Repair
options for MSEdge in 1709.

I'm not 100% convinced the old Powershell method even works any more.

On much older Windows 10, it's as they say in the article.
You could use Powershell to cause the Windows Store to
re-download MSEdge.

https://www.groovypost.com/wp-conten...wershell-1.png

The first part of that command, generates the fullname for the
App. Maybe in C:\Windows\Systemapps, you could also see the fullname
of MSEdge in there. The "digits" on the end of the name, are not
a personal identifier - all OS installations use that identifier,
and it means "this is a Microsoft software product". The OS has
two identifiers, one beginning with an 8 and one with a C and
these are common to a large number of things Windows installs.

In any case, first determine what you're running with "winver",
so we can focus on instructions for your version. If you have
1709 (16299.xxxx), you might be able to fix this with a GUI
interface (assuming you can find it - it's not a given that
these GUI things are easy to find).

Paul

On 1/26/2018 12:53 PM, Paul wrote:
Martin Edwards wrote:
Some time ago my copy packed up. The blue screen comes on for a few
seconds and then nothing. I have not bothered because I have others,
but is there a way to get it back?

The instructions can change with which Win10 version you are using.

Right-click Start : Run and enter "winver" as a command.
The version tells you what you're running.

*******

For example, the latest release is 16299.xxxx and that
corresponds to 2017-09, aka "1709". Some people have received 2017-09 only
in the last few weeks (months after its official release), so it's not
necessarily a given that this new technique applies to you.

https://www.groovypost.com/howto/res...ndows-10-1709/


In 1709, MSEdge is a "regular App", which doesn't mean a
damn thing to me. There is a GUI with Reset and Repair
options for MSEdge in 1709.

I'm not 100% convinced the old Powershell method even works any more.

On much older Windows 10, it's as they say in the article.
You could use Powershell to cause the Windows Store to
re-download MSEdge.

https://www.groovypost.com/wp-conten...wershell-1.png

The first part of that command, generates the fullname for the
App. Maybe in C:\Windows\Systemapps, you could also see the fullname
of MSEdge in there. The "digits" on the end of the name, are not
a personal identifier - all OS installations use that identifier,
and it means "this is a Microsoft software product". The OS has
two identifiers, one beginning with an 8 and one with a C and
these are common to a large number of things Windows installs.

In any case, first determine what you're running with "winver",
so we can focus on instructions for your version. If you have
1709 (16299.xxxx), you might be able to fix this with a GUI
interface (assuming you can find it - it's not a given that
these GUI things are easy to find).

Paul
Thanks to both.

--
Myth, after all, is what we believe naturally. History is what we must
painfully learn and struggle to remember. -Albert Goldman

On 1/27/2018 7:48 AM, Martin Edwards wrote:
On 1/26/2018 12:53 PM, Paul wrote:
Martin Edwards wrote:
Some time ago my copy packed up. The blue screen comes on for a few
seconds and then nothing. I have not bothered because I have others,
but is there a way to get it back?

The instructions can change with which Win10 version you are using.

Right-click Start : Run and enter "winver" as a command.
The version tells you what you're running.

*******

For example, the latest release is 16299.xxxx and that
corresponds to 2017-09, aka "1709". Some people have received 2017-09
only
in the last few weeks (months after its official release), so it's not
necessarily a given that this new technique applies to you.

https://www.groovypost.com/howto/res...ndows-10-1709/



In 1709, MSEdge is a "regular App", which doesn't mean a
damn thing to me. There is a GUI with Reset and Repair
options for MSEdge in 1709.

I'm not 100% convinced the old Powershell method even works any more.

On much older Windows 10, it's as they say in the article.
You could use Powershell to cause the Windows Store to
re-download MSEdge.

https://www.groovypost.com/wp-conten...wershell-1.png

The first part of that command, generates the fullname for the
App. Maybe in C:\Windows\Systemapps, you could also see the fullname
of MSEdge in there. The "digits" on the end of the name, are not
a personal identifier - all OS installations use that identifier,
and it means "this is a Microsoft software product". The OS has
two identifiers, one beginning with an 8 and one with a C and
these are common to a large number of things Windows installs.

In any case, first determine what you're running with "winver",
so we can focus on instructions for your version. If you have
1709 (16299.xxxx), you might be able to fix this with a GUI
interface (assuming you can find it - it's not a given that
these GUI things are easy to find).

Paul
Thanks to both.

It turns out that I have W10 1703. After some confused noodling around
I got it up again and it worked. It can't be the power of prayer, I'm
an agnostic. Thanks to all anyway.

--
Myth, after all, is what we believe naturally. History is what we must
painfully learn and struggle to remember. -Albert Goldman