Replies

I’ve found this a nuisance in the past.
If you check the properties of the drive it may well be indexing. This takes time, so just untick the index box and you may find instant ejection is possible.

I found it ok and downloaded the zip file, but it’s password protected!

A1ex

You just log in to Roboform and synchronise

1 user thanked author for this post.

Moonbear

I installed the May SSU ok, are there some update files I need.

I would appreciate a monthly list of the required kb files for each months updating process, if that’s possible.

A1ex

I ran your latest version and got the following;

Get-Date : Cannot bind parameter ‘Date’. Cannot convert value “15/2020” to type “System.DateTime”. Error: “String was
not recognized as a valid DateTime.”
At E:\Downloads\Get-WinVer.ps1:670 char:28
+ $(Get-Date($x[$($Cntr)].Substring(132,10).Trim())
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-Date], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.GetDateCommand

You cannot call a method on a null-valued expression.
At E:\Downloads\Get-WinVer.ps1:670 char:34
+ $(Get-Date($x[$($Cntr)].Substring(132,10).Trim())
+ ~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

Get-Date : Cannot bind parameter ‘Date’. Cannot convert value “29/2020” to type “System.DateTime”. Error: “String was
not recognized as a valid DateTime.”
At E:\Downloads\Get-WinVer.ps1:670 char:28
+ $(Get-Date($x[$($Cntr)].Substring(132,10).Trim())
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Get-Date], ParameterBindingException
+ FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.GetDateCommand

You cannot call a method on a null-valued expression.
At E:\Downloads\Get-WinVer.ps1:670 char:34
+ $(Get-Date($x[$($Cntr)].Substring(132,10).Trim())
+ ~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull

and yet copied to the clipboard was;

Edition: Windows 10 Pro 64-bit

Version: 2004

Build: 19041.113

Installed: 05/01/2020 11:22

Just scanning through this topic I noticed you are using Norton Security.

I stopped using this some years ago because it proved such a memory hog, perhaps as a quick check you could try  running with it off – you may be surprised,

A1ex

1 user thanked author for this post.

LHiggins

I solved the size problem by turning off system restore on C:. I thought I had already turned it off since I backup regularly with Acronis True Image, but it had become active again somehow.
SVI is now much smaller.

Thanks to cyberSAR for the additional info.

A1ex

So what’s the process to recover drivers, is it just a case of using the .inf files?

A1ex

2 users thanked author for this post.

CADesertRat, Seattle27

Thanks PKCano, got me using Power Shell and I got to reset all Store Apps that had gone missing.
A1ex

Any advice on how to restore it?
A1ex

I’m using v1903.
Thanks for the video moonshine, but my pop up window merely tells me I need a new app, it doesn’t mention the app store and the ‘OK’ button does nothing.
If I recall correctly I’ve disconnected the app store, could this be affecting my result?

A1ex

I used diskpart create partition primary and took it from there successfully.
Thanks all for your input.

A1ex

1 user thanked author for this post.

jburk07

I tried again when 18894 came out. Again it failed and reloaded 18885, but incomplete.
All my Program Files and Program Files(x86) content went missing, apart from the essential MS stuff, yet strangely the registry entries were all OK. I found this out when I tried reinstalling stuff. Info such as registering codes was still there.
This was proving too much a labour of love so I gave up and returned to 18885 from my disc image.
To avoid the problem repeating I’ve dropped back to the Slow Ring.
I’ve not really had any problems with upgrades in the past, I’m wondering if the transition to 20H doesn’t sit right with my older hardware (motherboard is Asus P8Z68-V/GEN3)

Alex

I’ve tried to follow this thread and must admit I’m utterly confused.
I’ve dual booted W7 and W10 for some time now, I started with both operating systems on the same hard drive, but then acquired a second ssd and moved one system to that, using True Image as a back-up medium.
When I boot either operating system the system drive always appears as “C:”. At first the alternative system appeared as G:, which happened to be the first available letter after my data drives, which are seperate. This resulted in some minor problems with system restore and the ever present danger of accidentally altering something in that drive, so I removed the drive letter from the unused system using Disk Management, and did the same for the other drive.
I now boot into either as if the second did not exist and have no problems.
My point is that dual booting should sort out the operating system to be C:, without introducing other drive letters. You appear to be treading a dangerous path if the second system remains active while the first is in use.
Alex

I’ve tried to load this twice, each time it stops with an error (no message) and resets me back to my previous version, and not always properly completed, I’ve had to use my previous images to restore (thank goodness I keep them). I’ve put the PC on 7 days hold from updating for now.
Anybody else suffering?