Does ATI 2020 have a problem on W10 with Error 0xb042f?

Steve, I have been able to get it running within the ISE.

=============

PS C:\> K:\Inet DL\537649-183809\CheckUSBdisk.ps1
File K:\Inet DL\537649-183809\CheckUSBdisk.ps1 cannot be loaded. The file K:\Inet DL\537649-183809\CheckUSBdisk.ps1 is not digitally signed. You cannot run this script
on the current system. For more information about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
    + CategoryInfo          : SecurityError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnauthorizedAccess

PS C:\>  Set-executionpolicy -executionpolicy RemoteSigned process

PS C:\> K:\Inet DL\537649-183809\CheckUSBdisk.ps1
USB drive letter p: removed
USB drive letter p: mounted

============

I had to set the Execution Policy. The the list and I see this.

===========

PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser       AllSigned
 LocalMachine    Unrestricted

=============

Not sure WHO is setting those?

Just an observation here guys,

Are both of you running the same Win 10 as in Pro vs. Home?

Found this in PowerShell docs on MS

Default

• Sets the default execution policy.
• Restricted for Windows clients.
• RemoteSigned for Windows servers.

Windows server = W10 Pro

Windows clients = W10 Home

EDIT: Link

Enchantech wrote:

Just an observation here guys,

Are both of you running the same Win 10 as in Pro vs. Home?

Enchantech, I'm on HOME. I'm 'playing' with this on my PC that has the same model USB drive as my wife's PC, making sure it works. Wife's PC is Pro version.

What you posted is what I did above and caused me to change the setting. Home doesn't have the Group Policy Editor, and I probably need to either set the execution parameter in the script or before calling it or find out where in the registry it is set as the default?

I did set it to ALLSIGNED but I was never prompted on the script and it just failed?

It looks like I found the answer here in Option TWO?

It is a little confusing right now? Here is what I do see from the above link Option 2?

I don't know if it IS set or not, suspect not?

The above link also has some more info on this and it has some .REG files as well to force changes without the Group Policy Editor I assume?

Irv, the key point if using AllSigned is the following statement:

Requires that all scripts and configuration files be signed by a trusted publisher, including scripts that you write on the local computer.

This means that you would have to setup your own certificate authority and then digitally sign all your PS scripts, even your simple profile .ps1 file.

I played a little with signing scripts a while back and gave it up as too much trouble for the purposes I was using PS for, hence I use the RemoteSigned policy which works just fine for what I am doing. 

See webpage: How to digitally sign PowerShell Scripts and / or webpage: How to: (Windows 10) Signing a Powershell Script with a Self-Signed Certificate

Bob, I have been using RemoteSigned on both editions of Windows 10, Home & Pro and see no difference between them.  This is also what has been recommended in the various PS books I have bought to aid in my learning.

Steve,

Okay, a PS wizard I am not.  As well I have not followed this thread to take in all that it has to offer but, I am curious why such difficulty in this instance.

This may have already been stated here so forgive me if it has.  When the PS command is run Get-ExecutionPolicy - List what is the result on both machines here?

I run Win 10 Pro with the above command I get the following return:

• MachinePolicy  Undefined
• UserPolicy Undefined
• Process Undefined
• CurrentUser Undefined
• LocalMachine Unrestricted

I have not run any PS policy command not tried to run the script here.  I wonder if Irv's PC will show CurrentUser as Restricted?

Bob, Irv posted the output of the list in his earlier post where CurrentUser is set as AllSigned.

PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser       AllSigned
 LocalMachine    Unrestricted

On my Win 10 Pro, the list output is as below:

PS D:\powershell> get-executionpolicy -List

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser       Undefined
 LocalMachine    Unrestricted

For myself, I am setting the Process policy via my profile.ps1 settings and haven't touched the other areas.  I have the same profile settings for use by both ISE and the regular PS command window.

There are two separate issues that Irv has encountered. 

One is directly caused by using AllSigned when none of the scripts are signed by a recognised certificate authority.

The second is something in Windows 10 with managing USB external drives which I have seen myself where the drive is physically connected but shows as having zero size / capacity in Explorer and cannot be mounted or dismounted via PS.

I am not sure why the second issue arises but it seems to be associated with a failed mount or dismount in some way, after which the only way that I could recover it was to physically pull the USB plug and then reconnect it again!

Note: the issue with my own USB 3.0 drive randomly disconnecting appears to have 'gone away' after I uninstalled the Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) controller device from Device Manager, then restarted the computer (laptop) to have it get reinstalled again.

Steve,

Yeah, the AllSigned is definitely wrong.  Probably needs to be Undefined which I believe = Restricted by default.

Can I ask why your use ISE rather than regular PS?

At this point given Irv's issue, I think the driver you mention is a major player in the issue if not the real cause of failure.  I would think that a Windows version upgrade hosed the driver in some way so that it drops the drive intermittently. 

I suggest using Device Manager to uninstall the Intel USB 3.0 eXtensible Host Controller - 1.0 which is what Irv should have on his machine then, shutdown the PC and start it again cold.  Should cause Windows to find new hardware, register the controller anew, and reinstall the driver.

Bob, to answer the question: Can I ask why your use ISE rather than regular PS?

Simply because it is very much easier to use than the regular PS blank command entry window and it is where I develop and test my scripts, allowing for debug based on results shown in the lower panel of the ISE plus integrated help panels etc.

Steve Smith wrote:

Irv, the key point if using AllSigned is the following statement:

Steve, I am probably making some progress and discovering where 'things' are kept.

For instance, in my Registry:

This is what sets it I guess?

When I start Powershell I get this:

===============

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded. The file C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS C:\> Get-ExecutionPolicy - List
Get-ExecutionPolicy : Cannot bind parameter 'Scope'. Cannot convert value "-" to type
"Microsoft.PowerShell.ExecutionPolicyScope". Error: "Unable to match the identifier name - to a
valid enumerator name. Specify one of the following enumerator names and try again:
Process, CurrentUser, LocalMachine, UserPolicy, MachinePolicy"
At line:1 char:21
+ Get-ExecutionPolicy - List
+                     ~
    + CategoryInfo          : InvalidArgument: (:) [Get-ExecutionPolicy], ParameterBindingExceptio
   n
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.GetExec
   utionPolicyCommand

===============

The list is this:

=============

PS C:\> Get-ExecutionPolicy -Lis

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser       AllSigned
 LocalMachine    Unrestricted

=============

So Local Machine matches the Registry. From the link I posted about 'Option TWO' I see this:

==================

1. Open PowerShell.

2. Copy and paste the command below into PowerShell for the execution policy your want to set, and press Enter.

Set-ExecutionPolicy AllSigned -Scope CurrentUser -Force

Set-ExecutionPolicy Bypass -Scope CurrentUser -Force

Set-ExecutionPolicy Default -Scope CurrentUser -Force

Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force

Set-ExecutionPolicy Restricted -Scope CurrentUser -Force

Set-ExecutionPolicy Undefined -Scope CurrentUser -Force

Set-ExecutionPolicy Unrestricted -Scope CurrentUser -Force

3. You can now close PowerShell if you like.

===================

Do you think the above would actuially fix my problem? I don't want to jump out of the frying pan into the fire here :-)

Steve, these are my 2 Powershell profiles. The ISE one is basically the same as you have with some incomplete minor changes:

C:\Users\ispal_000\Documents\WindowsPowerShell>dir
 Volume in drive C is OS
 Volume Serial Number is EEE1-088E

 Directory of C:\Users\ispal_000\Documents\WindowsPowerShell

05/10/2020  05:24 PM    <DIR>          .
05/10/2020  05:24 PM    <DIR>          ..
05/10/2020  05:24 PM               968 Microsoft.PowerShellIISE_profile.ps1
05/10/2020  05:25 PM                57 Microsoft.PowerShell_profile.ps1
               2 File(s)          1,025 bytes
               2 Dir(s)  28,923,928,576 bytes free

The contents of the Powershell one is a Single line:

C:\Users\ispal_000\Documents\WindowsPowerShell>type microsoft.powershell_profile
.ps1
Set-executionpolicy -executionpolicy RemoteSigned process
C:\Users\ispal_000\Documents\WindowsPowerShell>

However Powershell does complain about it? Guess the policy is set on starting?

I'll wait to hear from you or Enchantech before going forward and possibly making this worse.

 

Steve Smith wrote:

The second is something in Windows 10 with managing USB external drives which I have seen myself where the drive is physically connected but shows as having zero size / capacity in Explorer and cannot be mounted or dismounted via PS.

I am not sure why the second issue arises but it seems to be associated with a failed mount or dismount in some way, after which the only way that I could recover it was to physically pull the USB plug and then reconnect it again!

Note: the issue with my own USB 3.0 drive randomly disconnecting appears to have 'gone away' after I uninstalled the Intel(R) USB 3.1 eXtensible Host Controller - 1.10 (Microsoft) controller device from Device Manager, then restarted the computer (laptop) to have it get reinstalled again.

Steve, we are mixing two systems here.

First, my PC has NEVER failed under ATI. It has always seen the USB drive on backup start, and never lost it during a backup.

Second is that I'm only using you CHECKUSBDRIVE.PS1 here on MY PC which seems to have the MOUNT problem?

Third is that on my Wife's PC Windows itself, has NEVER lost the ability to read the drive whereas ATI has had a problem reading it at the start of the backup and reports the drive cable needs to be unplugged and plugged back in, and only once did it report the drive was unavailable during processing of the backup where it had already written 57.1MB's to it.

As for your 'cure', the Host Controller, you have it for USB 3.1, all our USB's are either 2.0 or 3.0, so she has a different controller:

So this probably isn't an issue, but it was installed on 2/20/2020, maybe near the time her system started to have problems? Note, no ROLL BACK option and UPDATE says this is the latest? I can't see a Windows Update that she got that even mentions external drives or USB changes?

Googling USB Disconnects that all seem to be about continual disconnect/connect, not really mounting problems? Again, from a pure Windows perspective (using the drive, looking at in Explorer or Explorer++ that I use I have never had a problem on her drive, as well as DISKMGMT always seeing it?

I will however see if deleting the driver and rebooting will help, but only if it fails again and I made the other Suspend change already on her PC.

Irv, before PowerShell can load and run the profile.ps1 script, you first need to issue the Set-executionpolicy -executionpolicy RemoteSigned process command from a command line within the PS application you are using, then restart that PS application.

Doing the above should then allow the profile to be loaded and executed.

Sorry about the mix up with your different computers for the original issue for this topic - your posts tend to be quite lengthy (this one has 60 posts in the topic so far!) and we deal with lots of other user topics across all the forums too, so very easy to get confused at times when juggling a number of different topics and issues.

Steve Smith wrote:

Irv, before PowerShell can load and run the profile.ps1 script, you first need to issue the Set-executionpolicy -executionpolicy RemoteSigned process command from a command line within the PS application you are using, then restart that PS application.

Doing the above should then allow the profile to be loaded and executed.

Steve, seems something else is causing this as I did what you suggested:

---------------------------

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded. The file C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS C:\> Set-executionpolicy -executionpolicy RemoteSigned process
PS C:\> exit

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded. The file C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS C:\>

----------------------------

Not even trying to use the ISE... running in an Administrator CMD prompt...

Steve Smith wrote:

Sorry about the mix up with your different computers for the original issue for this topic - your posts tend to be quite lengthy (this one has 60 posts in the topic so far!) and we deal with lots of other user topics across all the forums too, so very easy to get confused at times when juggling a number of different topics and issues.

Steve, yes, this thread has gone off topic. Understand, even I have to scroll back up to see old stuff. That and links I posted put some on review and are just coming in today.

I wish we had a way for the 3 of us, you, me, and Bob (guess that is his name) off-line via e-mail.

I has to be a problem that can be cured I'd think with the SETTING page about Developer's that appeared above recently (Sunday, May 10, 20:22) or the one today (5/11, 15:05) with all the SET-EXECUTION commands to issue.

Irv, try issuing Set-executionpolicy -executionpolicy RemoteSigned without including the final 'process' limiter for scope.

Irv,

In PowerShell or PowrShell ISE run the command below first:

Set-ExecutionPolicy Default -Scope CurrentUser -Force

Next, run the command Steve posted to set the Execution Policy as is below:

Set-executionpolicy -executionpolicy RemoteSigned -Scope process

Now close PowerShell and reopen it and type:

Get-ExecutionPolicy -list

Which should return:

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser       Undefined
 LocalMachine    Unrestricted

The above indicates that "Process" is set at "RemoteSigned" which is correct to run the script and

'CurrentUser" is set as "Undefined" which by default is an Restricted policy.

The above should allow use of the script.

Bob, nope, still bad...

====================

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded. The file C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1
is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at
https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS C:\> Set-ExecutionPolicy Default -Scope CurrentUser -Force
PS C:\> Set-executionpolicy -executionpolicy RemoteSigned -Scope process
PS C:\> exit

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

. : File C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be
loaded because running scripts is disabled on this system. For more information, see
about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:3
+ . 'C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShel ...
+   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : SecurityError: (:) [], PSSecurityException
    + FullyQualifiedErrorId : UnauthorizedAccess
PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser      Restricted
 LocalMachine    Unrestricted

PS C:\>

====================

I just renamed the POWERSHELL profile so there is none. I don't get the error (expected as there is nothing to read) and the list stays the same.

I decided to run the commands from Steve and then the list... look what I got:

==================

PS C:\> Set-executionpolicy -executionpolicy RemoteSigned -Scope process
PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser      Restricted
 LocalMachine    Unrestricted

PS C:\> Set-ExecutionPolicy Default -Scope CurrentUser -Force
Set-ExecutionPolicy : Windows PowerShell updated your execution policy successfully, but the
setting is overridden by a policy defined at a more specific scope.  Due to the override, your
shell will retain its current effective execution policy of RemoteSigned. Type
"Get-ExecutionPolicy -List" to view your execution policy settings. For more information please
see "Get-Help Set-ExecutionPolicy".
At line:1 char:1
+ Set-ExecutionPolicy Default -Scope CurrentUser -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (:) [Set-ExecutionPolicy], SecurityException
    + FullyQualifiedErrorId : ExecutionPolicyOverride,Microsoft.PowerShell.Commands.SetExecutionPo
   licyCommand

==============

See the above error, got to find the OVERRIDE!

I did issue Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Undefined and got the same list you have:

===============

PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process    RemoteSigned
  CurrentUser       Undefined
 LocalMachine    Unrestricted

=================

Closed and ran again, but there were some changes to the list, but Process was lost?

=============

C:\>powershell
Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Try the new cross-platform PowerShell https://aka.ms/pscore6

PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser       Undefined
 LocalMachine    Unrestricted

=================

Ran Set-executionpolicy -executionpolicy RemoteSigned -Scope process adding -force, still not there when I restart?

Steve Smith wrote:

Irv, try issuing Set-executionpolicy -executionpolicy RemoteSigned without including the final 'process' limiter for scope.

 After I made the changes for Bob and ran the command I got this:

==================

PS C:\> Get-ExecutionPolicy -list

        Scope ExecutionPolicy
        ----- ---------------
MachinePolicy       Undefined
   UserPolicy       Undefined
      Process       Undefined
  CurrentUser       Undefined
 LocalMachine    RemoteSigned

===================

Then entered ISE and it came up without error. However it seems the ISE profile was not run? Contents as of now:

==================

    # Irv's PowerShellISE profile
    # Saved in "C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1"
    # Set-executionpolicy -executionpolicy Bypass process
    Set-executionpolicy -executionpolicy RemoteSigned process

    Write-Host 'Welcome to' "$env:computername" -ForegroundColor Green
    Write-Host "You are logged in as" "$env:username" -ForegroundColor Green
    Write-Host "Today:" (Get-Date) -ForegroundColor Green
    Set-Location d:\powershell\
    Write-Host "PowerShell"($PSVersionTable.PSVersion.Major)"awaiting your commands."

    function edit ($file) {
    if (Test-Path ${env:ProgramFiles(x86)}\Notepad++\notepad++.exe) {
     & "${env:ProgramFiles(x86)}\Notepad++\notepad++.exe" $file}
     else {
    if (Test-Path $env:ProgramFiles\Notepad++\notepad++.exe) {
     & "${env:ProgramFiles}\Notepad++\notepad++.exe" $file}
     else {& "notepad.exe" $file }
      }}

    Get-executionpolicy

====================

Shouldn't the lines for Write-Host appear if it used the Profile? Or do I have to manually load the profile into the ISE and run it? Odd as if I run $profile in the ISE it reports this:

====================

PS C:\> $profile
C:\Users\ispal_000\Documents\WindowsPowerShell\Microsoft.PowerShellISE_profile.ps1

PS C:\>

====================

Steve, sorry for the length of my REPLIES... I worked in Development/Support for IBM on OS/2 and I was accustomed to collecting all the data I needed on problems. So I tend to report everything that seems to be important to me so to help the person looking at it.

Irv, if the profile runs on launch of PS or ISE then the lines for write-host will be shown prior to the prompt for any new commands.

Were you at Boca Raton for the OS/2 development?  It was the default OS we used at IBM UK for many years before moving to Windows 2000 on our PS/2 model 80's.

My time was spend in MidRange Tech Support for System 34,36,38 then AS/400 / iSeries which was developed out of Rochester, Minnesota where I spent time on assignment & courses.

Steve, YES, that would be what I expected, but it isn't happening? Don't know why? The errors I got before would indicate to me it IS reading the profile, or at least tried too?

Yes, that was where I worked (irv@bcrvm1) and moved to Austin with OS/2. Retired as the Release Manager and Fixtool developer. Worked with MS before 'our' divorce and handled development builds then. Spent 10 years in OS/2 before retiring. Fun times.

Uhh, NEVER MIND! I am sorry to say IT DOES run now... the ISE profile. My old eyes missed I spelled the filename wrong. PWERSHELLIISE.PS1, 2 'I's' after the 'L'. Corrected that, and it ran, as does the CHECKUSBDRIVE:

What a LONG ride this has been! Sorry.

Whew!  :-)

To quote Shakespeare (I think) - All's well that ends well!

I only got to visit Austin the once on a convention held there for tech leaders, otherwise endured the freezing winters & hot summers of Rochester, MN.  We did have some good tech schools in Italy (Rivotella near Lake Garda) and in Paris & Mainz near Frankfurt that I got to spent time in for IBM along with those here in the UK, so got in some good airmiles along the way.

Steve Smith wrote:

To quote Shakespeare (I think) - All's well that ends well!

I only got to visit Austin the once on a convention held there for tech leaders, otherwise endured the freezing winters & hot summers of Rochester, MN.  We did have some good tech schools in Italy (Rivotella near Lake Garda) and in Paris & Mainz near Frankfurt that I got to spent time in for IBM along with those here in the UK, so got in some good airmiles along the way.

Well, only the Powershell problem is resolved, not the original topic :-( Still wait and see about that.

Don't know why you had the problem at startup, but you did know that the drive was not mounted. We do not think we ever had that problem? Time will tell I guess if the 'changes' made fixed it?

Was in Austin for 6 years, gained some weight with the BBQ there. Nothing like it where we live now! Retired there and moved back to Florida near one of our daughters.

When we hosted MS workers for OS/2 in Boca, you'd think those people never saw a beach. The MS 'culture' was completely different from us IBM developer's. We work golf shirts and semi-dress pants. T-shirts and shorts was what they sometimes wore. Took off during the day for the beach, but worked many many hours anyway. When they first arrived they put mini-fridges in the office and stocked it with snacks and drinks. One night IBM Security made the rounds and cut the plugs off... can't do that.

When I transferred to Austin, a few years later we came back to So. Fl. for our daughter's wedding. I was totally shocked, I forgot how crowded it was. Still do, we travel to Ft. Lauderdale or Miami for cruises.

Quick update. Started OK today and continues to run. 3:30PM now, started at 10AM. SUPER slow right now. 5 1/2 hours gone, says 9 1/2 to go, but it usually takes about 10 hours to complete. No way I know to tell 'where' it is, but I suspect is in her GAMES folder on D: drive. That folder is huge, some folders are from the early 2000's and I bet she'll never even know what they are much less play them. 741 folders, almost all of the 1TB drive it seems. I can't get her to delete ANY of them...