The ability to preview PowerShell (.ps1) scripts from Window’s File Explorer is not enabled by default, or so it seems. A quick one line PowerShell command fixes that in a jiffy!
Set-ItemProperty Registry::HKEY_CLASSES_ROOT\.ps1 -Name PerceivedType -Value text
That’s it! Open up File Explorer and you’ll now be able to preview PowerShell scripts!
P.S. This was tested on Windows 10
It was recently posted by OnMSFT that a small percentage of PCs may fail to update to the 15042 Insider Build. When that happens, your computer will hang on a black screen after reboot. I know … I just encountered it.
Fortunately, I was aware of the bug before I proceeded, and knew where to go to get the fix. thanks to this post from Microsoft Answers!
Here’s what you need to do:
reg delete HKEY_LOCAL_MACHINE\system\setup\upgrade\nsimigrationroot /f
netsh int ipv6 set locality state=disabled
reg delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nsi\{eb004a01-9b1a-11d4-9123-0050047759bc}\28 /f
As always, if you are in the insider ring, it pays to stay up-to-date on insider releases and issues.Insider releases are NOT meant to be run on production machines.
It’s been well documented that updates for Windows 10 (such as the 1607 Anniversary update) will cause issues with interfacing to the 2012 R2 Essentials Server. Two things in particular:
Until now, the process that I had taken to resolve this on each workstation was as follows:
Well, now, it comes to pass that we can make this process a bit faster, as we can eliminate the first two steps (dropping workstation to a workgroup, and logging in with the local admin account).
So here’s how the steps now look, while remaining logged in as the current domain user account:
I came across a very interesting 30 minute video from Microsoft Channel 9 that discusses the evolution of how Windows handles memory – paging, cache, and now memory compression – from Windows 7 to Windows 10.
You can see if your memory is being compressed by going to Task Manager –> Performance –> Memory.
Here is the video from Microsoft’s Channel 9:
Have you encountered a situation where Windows 10 will try to install an update that you don’t want installed? Perhaps for a non-existent printer? Or an update that you just aren’t ready to test, like a new video driver?
Windows 10 seems to love doing things automatically, without any real control over what it does. Fellow MVP’er, Susan Bradley, pointed me to a Microsoft driver tool that will allow you to resume control of some of these updates and troubleshoot such situations.
Check out Microsoft KB 3073930 titled: How to temporarily prevent Windows or driver update from reinstalling in Windows 10
I’ll keep this short, sweet and to the point. Beware of the “Windows 10 Upgrade” notice!
First, I really like Windows 10, and I encourage people when buying a new computer to get Windows 10. I have also done a fair number of in-place upgrades to Windows 10. All of them were successful upgrades, although I had unique challenges with two of them that took time to resolve.
Microsoft released Windows 10 at the end of July 2015, and made it a free upgrade for most people. In the past six months, Microsoft has been pushing nag messages and prompts to remind you to upgrade to Windows 10.
But, with less than two months to go, Microsoft has upped the nagging to almost full scale trickery. The details can be read in this PCWorld article.
But here is the catch: you may think you are saying “No” to the Windows 10 upgrade by clicking on the X in the top right corner of the popup window. But it’s just the opposite. Clicking on the X is being treated the same as clicking on OK at the bottom of the window.
Please be careful!
Microsoft’s Technet website posted detail solutions to a wide variety of common Windows 10 issues on May 3rd, 2016.
Here’s a quick overview of topics covered:
SOLUTIONS RELATED TO …
Active Hours is a new feature recently released within the Insider (beta) version of Windows 10, and will be part of the upcoming anniversary release of Windows 10.
Think of Active hours as your business work hours, or the time frame that you most use your computer. By setting Active Hours, you can make sure that your computer will NOT automatically restart after updates are installed during those times.
By default, Active Hours is defined as 8am to 5pm (relative to your time zone).
To change your Active Hours,
Unfortunately, the valid range for active hours is 10 hours. And, keep in mind – you are defining your busiest work hours so as to avoid automatic reboots. Personally, I would have preferred if this would have been the time frame when we would want reboots to occur.
And for those Group Policy people, yes, Active Hours can be set and changed within the Group Policy Editor.
Go to: Local Computer Policy –> Computer Configuration -> Administrative Templates -> Windows Components -> Windows Updates and locate the “Turn off auto-restart for updates during active hours” policy.
I’m on the Microsoft Insider list for Windows 10, which provides beta releases of Windows 10 as Microsoft makes them available.
Over the weekend, Build 14328 was made available, and for the most part, it’s getting rave reviews. Sure, there are things people don’t like, features not yet implemented, and outstanding issues (mostly with drivers) – but overall, it seems to me that Windows 10 is getting pretty stable.
The obvious big change with this build is a somewhat revamped Start Menu, or what Microsoft now calls the “Start Experience”. You still have the list of all apps in alphabetical order, as well as your tile menu.But you now have a selection of important functions, such as Power, Settings and File Explorer along the left rail (see below).
So, if you are on the Insider Build list, give this new build a run. But please remember, it is BETA, which means unexpected bugs can occur, and even system crashes. All that is to say – don’t install BETA software on a production system unless you are willing to take the risk ANDE you have good backup!
I recently upgraded an HP 700-410xt workstation from Windows 8.1 Pro to Windows 10. The upgrade itself went very well, and the user noticed immediate improvement with the various Adobe suite of products that he uses.
However, he reported that the each morning his workstation would have an error message on the screen regarding LogonUI.exe, or a low memory warning:
Note — he closes all his apps and locks the computer at night. I was able to monitor the computer that evening and identified that the LogonUI.exe service was indeed consuming all available memory.
I did the normal effort of making sure that Windows 10 patches were up to date, as well as computer drivers. I even went so far as to disable any apps with “live tile” turned on.
Finally, several other MVPs that were trying to assist asked (1) is this an HP computer, and (2) were there any fingerprint or biometric software installed? The answer was YES to both questions. The computer in question had the HP Simplepass program installed, although the user was not using any fingerprint scan device.
And then it turns out that this issue with LogonUI.exe has been affecting HP computers for at least two years, both on Windows 8.1 and Windows 10. In all cases, uninstalling software such as HP SimplePass or HP OmniPass fixed the low memory issue with LogonUI.exe!
I uninstalled HP Simplepass, rebooted the computer, and a day later, the user reported all was fine!
