Normally the reliable way to create a bootable disk is simply to use the MS media creation tool to directly create a bootable flash drive, for example as per the tutorial here.So I downloaded the newest Windows 10 I found on Microsoft's website
Have you tried the alternative command form @garlin suggested?
How are you launching Powershell?
Are you starting Powershell from the appropriate shortcut?
Winget --info
works for me.
I downloaded Windows 10 directly from Microsoft's site (https://www.microsoft.com/en-us/soft...d/windows10ISO). Then followed the on-screen instructions to create the bootable USB.
I don't see Garlin's alternative.
I'm opening the Start Menu, scrolling to & opening the Windows Powershell folder & selecting "Run as Administrator" on the Windows Powershell shortcut.
Unfortunately, Winget just isn't working on my comfuser.
- - - Updated - - -
I'll give Option 13 a try tomorrow.
Replace with the actual package name.
Code:Get-AppxPackage -AllUsers Microsoft.ZuneMusic_11.2309.6.0_x64__8wekyb3d8bbwe | Remove-AppxPackage
Thanks for the code, but it didn't work for me.
Here are 3 examples of errors I received:
PS C:\Windows\system32> Get-AppxPackage -AllUsers Microsoft.MicrosoftStickyNotes_6.0.1.0_x64__8wekyb3d8bbwe | Remove-AppxPackage
Get-AppxPackage : The term 'Get-AppxPackage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ Get-AppxPackage -AllUsers Microsoft.MicrosoftStickyNotes_6.0.1.0_x64_ ...
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-AppxPackage:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
======================================================================
PS C:\Windows\system32> Get-AppxPackage -AllUsers Microsoft.ZuneVideo_10.22091.10051.0_x64__8wekyb3d8bbwe | Remove-AppxPackage
Get-AppxPackage : The term 'Get-AppxPackage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ Get-AppxPackage -AllUsers Microsoft.ZuneVideo_10.22091.10051.0_x64__8 ...
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-AppxPackage:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
======================================================================
PS C:\Windows\system32> Get-AppxPackage -AllUsers Microsoft.MicrosoftOfficeHub_18.2306.1061.0_x64__8wekyb3d8bbwe | Remove-AppxPackage
Get-AppxPackage : The term 'Get-AppxPackage' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ Get-AppxPackage -AllUsers Microsoft.MicrosoftOfficeHub_18.2306.1061.0 ...
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-AppxPackage:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Unfortunately, Option 13 didn't work for me either.
The evidence suggests your Powershell installation may be corrupt.
This seems strange, as you said you clean installed Windows, I think. (If you did, that would have meant you booted from the install disk and deleted all partitions making up the old Windows installation and then installed to unallocated space
You would then have had to configure a user account during the installation and would have had no personal data and no installed programs.
Please confirm that's what you did. Thanks.
Last edited by dalchina; 25 Nov 2023 at 01:21.
I downloaded Windows 10 directly from Microsoft's site (https://www.microsoft.com/en-us/software-download/windows10). Then followed the on-screen instructions to create a bootable USB.
1. I shut down the comfuser, turned it back on & went into the BIOS to set boot to the USB.
2. I deleted all partitions so I can install Windows onto Unallocated Space, then I created the initial Local Administrator account.
3. After Windows was finished installing, I went into Settings>Update & Security>clicked Check for updates & did that about 4 times to make sure I had everything available.
Try Geek Uninstaller (freeware)
Download zip file, open in windows Explorer, extract (copy & paster) geek.exe file to the Desktop
Run geek.exe file > select View menu > Microsoft Store Apps
Double click on desired app(s) to uninstall
Note : The usual program for this is RevoUninstaller (freeware) but occasionally I find that if Revo can't find an app, geek will.
Ok, I'm (finally) back up & running ... correctly.?
Either Nov. 29th/30th, I was looking in the BIOS & realized it was missing the UEFI.
Usually, when I go into the BIOS, the 1st screen shows 3 drive-looking icons; UEFI, my SSD & my Optical Drive.
But the UEFI wasn't shown that time. So I loaded-up the BIOS's Optimized Defaults, rebooted using the Windows 10 USB & reinstalled Windows.
Installation went smoothly, updates went smoothly & I was able to uninstall a few Windows Apps using a combination of Option 9 & Option 13 (Option 10 did nothing for me). There are a few that still will not uninstall, but that's ok for now. So I don't know if the UEFI had anything to do w/my problems, but it's been fixed now.
Brink's Options helped me enough that I didn't need Revo Uninstaller or Geek Uninstaller this time. But I have used Revo Uninstaller in the past w/great success.
Quote
