Windows 10: Windows PowerShell acting weird?

Hello,

After updating from insider to 15063 and 15063.11 RTM powershell seems to be showing random symbols, but when I try to copy paste these symbols somewhere else they show up as normal text.

In powershell I see this:





After copy paste I get this:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\WINDOWS\system32>


I also had this issue in 15058 (not in 15048) and also all of my apps were gone and did not function( fixed that by doing manual resets in settings app).

The issue is probably with powershell's data since most other apps had issues with that and needed a reset, but there is no option to reset powershell in the settings app :/

:)

 

Photo app will not stay open in windows 10

Often just uninstalling then reinstalling fixes apps that have the disappearing act.

Command Prompt (admin) two commands;

PowerShell

Get-AppxPackage *photo* | Remove-AppxPackage

then Restart the computer and search the store for Microsoft Photo

 

mobile hotspot not staying

Hi ghost1982,

I agree with you but this is a Windows setting. The mobile hotspot remains active as long as there is at least one connected device, if after 5-6 minutes no device is connected to the mobile hotspot, the system will disable it
automatically.
I do not know if this default setting can be changed by acting on the registry or through the commands in PowerShell.

I'm not aware of it.

Updating Update Creators is an important update, and as it is important, Windows will always try to install it.

 

That looks more like a GPU driver problem. Does this happen with any other programs? What GPU do you have on your computer and are you using a second or external screen?

 

I'm using Insider Preview Version 1703 Build 15063.11 and don't see that problem. Haven't seen an official RTM Version 1703 Build 15063.11 yet.

 

I have a GTX 1070, and I have updated my graphics driver, did not fix the issue. I do not have any similar issues with other applications.

The only thing I could try is doing a complete clean driver install with DDU.

Might be because I am still an insider, shouldn't be an issue, since I had this problem with 15063 too.

 

Before you go down that road, maybe restore the default personalisation settings for the console. Try options Two and Three in the linked tutorial.

Command Prompt - Restore Default Personalization Settings

 

Thanks for the suggestion! Sadly it did not work( option two looked promising) , done option two and ran the batch file as administrator in option three, did not help :/

P.S Seems like Powershell ISE does work, but the default Powershell does not. [GREEN] - works, [RED] - does not work.

 

Should not be doing that at all. Try uninstalling device and driver and reboot to let windows install the default microsoft version. If no, you will have to do a clean install of windows.

 

Just removed my GPU and it is still broken with intel HD graphics, well if fixing it means doing a clean install of windows then that just means it will have to stay broken :/

 

It sounds like either something is corrupt in %localappdata% so a new account would fix it or something is bust with powershell and a repair install would most likely fix it.

Try a new account - if that doesn't work a repair install only takes half an hour (assuming you have the ISO already) and you get to keep all your programs/documents etc.

 

It is VERY likely that something in powershell's data is corrupt, since most apps after upgrading to this build did not work, and only started to work after doing resets( deleting the data and starting fresh) from settings.

Is there any ways to delete the stuff that powershell uses and just make it regenerate everything?

Going to try making a new account and see if powershell is fixed

 

No sadly not. You may be able to do a hide in Windows programs in the Windows updates side of Programs.

Get a video of it doing it and hardware info through Speccy and send to the person in charge of the Insider program. They may ask for dump logs and some other stuff if they need it.

If you have an extra drive, try a clean install on it and se if the problem happens again. If not, then we know something is screwed up on the current drive and needs diagnosed.

If you have a backup before this started, try that first. Also try a Linux Mint Live CD to see if the problem replicates with it. If not, then we are dealing with another what in the H did Microsoft's Software Engineers do to screw up their OS again.

 

Ok, so it goes like this:

I have been on build 15048 where powershell worked normally, then I upgraded to 15058 - broken, then I downgraded back to 15048 - works again. 15063 comes out for insiders I upgrade to it and yet again, same bug, and then I revert back and it works. So in total I have tried 3 times to upgrade to 15063 with no bugs - no luck. Now when the RTM build came out, I decided to update and fix my issues one by one, fixed my apps by resetting data, and now powershell is left.

If the issue can not be fixed without clean installing then it is not worth it. A repair install will most likely fail too, since it probably does not touch any program data, which is where the fault most likely is and I don't have a 2 TB backup drive to back my stuff up *Sad

My hardware shouldn't be the issue ,since I have had windows 10 for a couple of years now, and only the two latest builds have been corrupting something after updating.

IF I knew where powershell keeps its program data, I could transfer a fresh copy from my laptop, since it is currently on build 15063.

P.S I have also installed powershell 6 alpha to see if it also has any issues, and no, it works just fine :/

I have a feeling it is because my OS is really old, well old enough. My laptop( which has a relatively fresh OS) went through 5 insider builds before 15058 and 15063 and it had no issues. If only my insider build didn't have an expiration date, then I could have waited for a couple of months *Tongue

 

Reading the other thread about Insider Preview Version 1703 Build 15063.0 through Version 1703 Build 15063.11 indicates the RTM version will be coming soon. There has been speculation on other sites that Version 1703 Build 15063.11 RTM has been leaked but as with previous test/BETA versions of Windows over the last several years there could be an issue with leaked/unofficial installs.