Windows 10 and Office Excel

**DocAElstein** · 03-20-2018, 04:09 PM

This macro,
http://www.excelfox.com/forum/showth...ge18#post12360
http://www.excelfox.com/forum/showth...ll=1#post12522
, is used again to analyse the results from above
sys 95 (71) [41]
dll 13 (11) [1]
bin 6 (2) [0]
cpa 1 (1) [0]
vp 5 (5) [0]
Totals 120 (90) [42]

I get slightly different results to previously. Probably due to
_ a) forgetting to underline already coloured that were not in DriverStore, so only in driver.
_ b) I also screwed up the logic in the macro a bit, Because….after the change to make an underlined for a case of an already coloured, but not matched in drivers ( http://www.excelfox.com/forum/showth...ll=1#post12810 ) , The following logic, from here ( http://www.excelfox.com/forum/showth...ge18#post12360 ) , is not valid……._
_.......the code snippet below would be a typical appropriate logic code line to achieve filling the corresponding 3 variables, if appropriate, to indicate the presence of a file type in
__ Device Manager __ ( DriverStore ) __ [ drivers ]

Code:

Case "SYS" Let Sys = Sys + 1: If rngStr.Font.Italic = True Then Let Sys2 = Sys2 + 1: If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Sys3 = Sys3 + 1

An entry must be both in Device Manager and be italicised , before it is possible to be underlined. Hence the long line use is valid………………._

The simple change we need is to remove the last If from the same physical line to a separate line. While we are at it , we might as well do it for all .
The logic then is more straight forward
The Case case , decides to add the count for the file type… at this popint…
If the cell is ( italicised ) , it is in DriverStore
If the cell is [ underlined ] , it is in drivers
Just to make it clear , this snippet shows me in the process of changing
Sub FileTypesHereInDeviceManagerPropertiesUndDriverSto reUnddrivers()
http://www.excelfox.com/forum/showth...ll=1#post12522
to
Sub FileTypesHereInDeviceManagerPropertiesUndDriverSto reUnddrivers2()

Code:

                    Select Case UCase(Xtn)
                     Case "SYS"
                      Let Sys = Sys + 1
                      If rngStr.Font.Italic = True Then Let Sys2 = Sys2 + 1
                      If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Sys3 = Sys3 + 1
                     Case "DLL"
                      Let Ddl = Ddl + 1
                      If rngStr.Font.Italic = True Then Let Ddl2 = Ddl2 + 1
                      If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Ddl3 = Ddl3 + 1
                     Case "BIN"
                      Let Bin = Bin + 1
                      If rngStr.Font.Italic = True Then Let Bin2 = Bin2 + 1
                      If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Bin3 = Bin3 + 1
                     Case "CPA"
                      Let Cpa = Cpa + 1: If rngStr.Font.Italic = True Then Let Cpa2 = Cpa2 + 1: If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Cpa3 = Cpa3 + 1
                     Case "VP"
                      Let Vp = Vp + 1: If rngStr.Font.Italic = True Then Let Vp2 = Vp2 + 1: If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Vp3 = Vp3 + 1
                     Case Else
                      Debug.Print "Case Else   " & rngStr.Value
                      Let Els = Els + 1: If rngStr.Font.Italic = True Then Let Els2 = Els2 + 1: If rngStr.Font.Underline = xlUnderlineStyleSingle Then Let Els3 = Els3 + 1
                    End Select
                Else ' not a file path

Here the results from the previous and current macro
sys 95 (71) [41]
dll 13 (11) [1]
bin 6 (2) [0]
cpa 1 (1) [0]
vp 5 (5) [0]
Totals 120 (90) [42]

sys 95 (71) [44]
dll 13 (11) [1]
bin 6 (2) [0]
cpa 1 (1) [0]
vp 5 (5) [0]
Totals 120 (90) [45]

ExplorerBefore DeviceManager V DriverStore2.xlsm : https://app.box.com/s/xokdiupd311mtvzwcsazh15ou13nolnq

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

General notes…attempting to summarise

The files found by the cmd prompt way are very small in number compared to any other way , and appear to be almost all the files found by any way for the graphic card, (Intel(R) G41 Express Chipset (Microsoft Corporation - WDDM 1.1) ). These are types dll , bin , vp and just one bin and one cpa
That is approximately 20 files out of approximately 60 files in total for the cmd prompt way. The remaining 40 or so files are not to be found in the list from the Device Manager Properties . They are of the type
sys 1
dll 7
bin 2
bag 1
xml 11
js 3
gdl 1
cab 1
ini 3
cat 4
inf 4
pnf 4
gpd 3
exe 1
Only the graphic card info was in the list from the Device Manager Properties

For the Double Driver List we see in addition files belonging to
HP OfficeJet Pro 8720 PCL-3
HP OfficeJet Pro 8720 PCL-3\amd64
So some more types were found. These are types are one of a sys, cpa , bag , gdl , cab, exe and a few dll, bin , vp , xml , js , cat, g pd
The remaining files not to be found in the Double Driver are
dll 1
xml 3
js 1
ini 2
cat 2
inf 4
pnf 4
gpd 1

So the list from Command Prompt things seems to contain very little.

So I did do a quick check of cmd against drivers and DriverStore
Nothing at all was found in drivers. The entire files were found in DriverStore grouped in a very similar way..
_._________________
From Device Manager Properties we have 120 files, with 5 different types
sys 95
dll 13
bin 6
cpa 1
vp 5
Total 120
From DoubleDriver
The full list from Double Drivers looks like this
sys 128
dll 49
bin 3
cpa 1
vp 5
els 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
dpd 0
cab 1
bag 1
ppd 1
exe 1
dpb 4
Total 448

Here we look at the files from Device Manager ( that are in Double Driver )
sys 95 (70)
dll 13 (11)
bin 6 (2)
cpa 1 (1)
vp 5 (5)
Totals 120
Most of the missing files sys are for “WAN Miniport”
ExplorerBefore DeviceManager V DoubleDriver2.xlsm : https://app.box.com/s/mrea4z64s63wxs7rsx2j7s8pjypvin35

Looking back at Double Driver we can list the extra files that it has compared with Device Manager
sys 78
dll 38
bin 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
cab 1
bag 1
ppd 1
exe 1
dpb 4

Making comparisons to the large Folders, drivers and DriverStore..
Device Manager Properties in drivers
In drivers we have File types , 3x .sys , 12x .dll 1x .sam , 10x .dll.mui , 125x .sys.mui
Here for the Device manger list, we see the files ( appearing in drivers )
sys 95 (46)
dll 13 (1)
bin 6 (0)
cpa 1 (0)
vp 5 (0)
We should note that almost all paths found from the Device Manage Properties ( apart from a few audio and most of the graphic files) show a “drivers” in the path. About half of the .sys are in the de-DE Folder, but they need to be matched to an extra .mui

Device Manger Properties in DriverStore:
In DriverStore we have 2783 files of types
sys 389
dll 275
bin 68
cpa 1
vp 5
bag 20
xml 144
js 8
gdl 35
cab 1
ini 185
cat 45
inf 706
pnf 93
gpd 174
exe 1
inf_loc 508
pnf 93
hlp 9
ntf 8
ppd 27
dat 6
dpb 12
cty 2
msc 2
xst 1
In this case, all the files in the dn-DE or en-EN folders have the extension inf_loc So we would not expect to find any files from Device manager there, in de-DE.
Almost all the files are found. A few .bin files are missing and some audio .sys and most of the “WAN Miniport” .sys files .
The extra files that are not found are
sys 318
dll 264
bin 64
bag 20
xml 144
js 8
gdl 35
cab 1
ini 185
cat 45
inf 706
pnf 93
gpd 174
exe 1
inf_loc 508
pnf 93
hlp 9
ntf 8
ppd 27
dat 6
dpb 12
cty 2
msc 2
xst 1

An interesting final conclusion for Device Manager Properties is that in drivers none of the files in the Device Manager properties are found, or half if we include those with the extra .mui
Most of the files are found in the DriverStore, but they are grouped in many folders each with a few files in them. These Folders have the name FileRepository

Double Driver in drivers
Double Driver has a much larger , ( 448 ) , and varied file collection than Device Manager Properties, but similarly to for device manager, in drivers we don’t find many of them , and mostly only if we match to ( files with an extra .mui in drivers )
We find 104 .sys.mui with the same file name as those in the 128 .sys in Double driver. There is just one matched .dll to the 49 .dll in Double Driver
This leaves unaccounted for in Double Driver
sys 24
dll 48
bin 3
cpa 1
vp 5
els 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
cab 1
bag 1
ppd 1
exe 1
dpb 4

For the case of the Double Driver in DriverStore, we have a more complicated situation. In total there is 2783 files.

After a few fail attempts, we started again….
http://www.excelfox.com/forum/showth...ge22#post12395

And summarised here…. http://www.excelfox.com/forum/showth...ge29#post12481

Here is the summary list of Double Driver to ( DriverStore ) and [ drivers ]
sys 128 (127) [58]
dll 49 (47) [1]
bin 3 (3) [0]
cpa 1 (1) [0]
vp 5 (5) [0]
inf 81 (78) [0]
ini 107 (26) [0]
cat 4 (4) [0]
gpd 29 (29) [0]
xml 27 (27) [0]
gdl 2 (2) [0]
js 3 (3) [0]
dpd 0 (0) [0]
cab 1 (1) [0]
bag 1 (1) [0]
ppd 1 (1) [0]
exe 1 (1) [0]
dpb 4 (4) [0]
Total 448 (360) [59]
Almost all the files from Double Driver are in DriverStore. ( The missing .ini files are all copies of the one file, restore.ini )
Extra files not accounted for left in DriverStore are
.sys 261
.dll 226
.bin 65
.inf 625
.ini 78
.cat 41
.gpd 145
.xml 117
.gdl 33
.js 5
.bag 19
.ppd 26
.dpd 8

**DocAElstein** · 03-20-2018, 04:09 PM

General notes…attempting to summarise

The files found by the cmd prompt way are very small in number compared to any other way , and appear to be almost all the files found by any way for the graphic card, (Intel(R) G41 Express Chipset (Microsoft Corporation - WDDM 1.1) ). These are types dll , bin , vp and just one bin and one cpa
That is approximately 20 files out of approximately 60 files in total for the cmd prompt way. The remaining 40 or so files are not to be found in the list from the Device Manager Properties . They are of the type
sys 1
dll 7
bin 2
bag 1
xml 11
js 3
gdl 1
cab 1
ini 3
cat 4
inf 4
pnf 4
gpd 3
exe 1
Only the graphic card info was in the list from the Device Manager Properties

For the Double Driver List we see in addition files belonging to
HP OfficeJet Pro 8720 PCL-3
HP OfficeJet Pro 8720 PCL-3\amd64
So some more types were found. These are types are one of a sys, cpa , bag , gdl , cab, exe and a few dll, bin , vp , xml , js , cat, gpd
The remaining files not to be found in the Double Driver are
dll 1
xml 3
js 1
ini 2
cat 2
inf 4
pnf 4
gpd 1

So the list from Command Prompt things seems to contain very little.

So I did do a quick check of cmd against drivers and DriverStore
Nothing at all was found in drivers. The entire files were found in DriverStore grouped in a very similar way..
_._________________
Device Manager Properties
From Device Manager Properties we have 120 files, with 5 different types
sys 95
dll 13
bin 6
cpa 1
vp 5
Total 120
From DoubleDriver
The full list from Double Drivers looks like this
sys 128
dll 49
bin 3
cpa 1
vp 5
els 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
dpd 0
cab 1
bag 1
ppd 1
exe 1
dpb 4
Total 448

Here we look at the files from Device Manager ( that are in Double Driver )
sys 95 (70)
dll 13 (11)
bin 6 (2)
cpa 1 (1)
vp 5 (5)
Totals 120
Most of the missing files sys are for “WAN Miniport”
ExplorerBefore DeviceManager V DoubleDriver2.xlsm : https://app.box.com/s/mrea4z64s63wxs7rsx2j7s8pjypvin35

Looking back at Double Driver we can list the extra files that it has compared with Device Manager
sys 78
dll 38
bin 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
cab 1
bag 1
ppd 1
exe 1
dpb 4
So we have a lot of extra files and new types in Double Driver which are not in Device manager properties.

Making comparisons to the large Folders, drivers and DriverStore..
Device Manager Properties in drivers
In drivers we have File types , 3x .sys , 12x .dll 1x .sam , 10x .dll.mui , 125x .sys.mui
Here for the Device manger list, we see the files ( appearing in drivers )
sys 95 (46)
dll 13 (1)
bin 6 (0)
cpa 1 (0)
vp 5 (0)
We should note that almost all paths found from the Device Manage Properties ( apart from a few audio and most of the graphic files) show a “\DRIVERS” in the path. About half of the .sys are in the de-DE Folder, but they need to be matched to an extra .mui The path given in Device manager properties shows no reference to this folder, \de-DE

Device Manger Properties in DriverStore:
In DriverStore we have 2783 files of types
sys 389
dll 275
bin 68
cpa 1
vp 5
bag 20
xml 144
js 8
gdl 35
cab 1
ini 185
cat 45
inf 706
pnf 93
gpd 174
exe 1
inf_loc 508
pnf 93
hlp 9
ntf 8
ppd 27
dat 6
dpb 12
cty 2
msc 2
xst 1
In this case, all the files in the dn-DE or en-EN folders have the extension inf_loc So we would not expect to find any files from Device manager there, in de-DE.
Almost all the files are found. A few .bin files are missing and some audio .sys and most of the “WAN Miniport” .sys files .
The extra files that are not found are
sys 318
dll 264
bin 64
bag 20
xml 144
js 8
gdl 35
cab 1
ini 185
cat 45
inf 706
pnf 93
gpd 174
exe 1
inf_loc 508
pnf 93
hlp 9
ntf 8
ppd 27
dat 6
dpb 12
cty 2
msc 2
xst 1

An interesting final conclusion for Device Manager Properties is that in drivers none of the files in the Device Manager properties are found, or half if we include those with the extra .mui
Most of the files are found in the DriverStore, but they are grouped in many folders each with a few files in them. These Folders have the name \FileRepository

Double Driver in drivers
Double Driver has a much larger , ( 448 ) , and varied file collection than Device Manager Properties, but similarly to for device manager, in drivers we don’t find many of them , and mostly only if we match to ( files with an extra .mui in drivers )
We find 104 .sys.mui with the same file name as those in the 128 .sys in Double driver. There is just one matched .dll to the 49 .dll in Double Driver
This leaves unaccounted for in Double Driver
sys 24
dll 48
bin 3
cpa 1
vp 5
els 1
inf 81
ini 107
cat 4
gpd 29
xml 27
gdl 2
js 3
cab 1
bag 1
ppd 1
exe 1
dpb 4

For the case of the Double Driver in DriverStore, we have a more complicated situation. In total there is 2783 files.

Here is the summary list of Double Driver to ( DriverStore ) and [ drivers ]
sys 128 (127) [58]
dll 49 (47) [1]
bin 3 (3) [0]
cpa 1 (1) [0]
vp 5 (5) [0]
inf 81 (78) [0]
ini 107 (26) [0]
cat 4 (4) [0]
gpd 29 (29) [0]
xml 27 (27) [0]
gdl 2 (2) [0]
js 3 (3) [0]
dpd 0 (0) [0]
cab 1 (1) [0]
bag 1 (1) [0]
ppd 1 (1) [0]
exe 1 (1) [0]
dpb 4 (4) [0]
Total 448 (360) [59]
Almost all the files from Double Driver are in DriverStore. ( The missing .ini files are all copies of the one file, restore.ini )
Extra files not accounted for left in DriverStore are
.sys 261
.dll 226
.bin 65
.inf 625
.ini 78
.cat 41
.gpd 145
.xml 117
.gdl 33
.js 5
.bag 19
.ppd 26
.dpd 8

Files from a typical Driver Disc sold as including Windows 10 drivers.

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

In support of this post, which I wrote to get some ideas on my conclusions so far...
http://www.eileenslounge.com/viewtopic.php?f=55&t=34247

Posted Forum question: -

File types produced in Windows(10) Device back up way /Methods

Different Files and File types produced in Windows (10) Device back up ways / Methods

Hi
I have spent a lot longer than I wanted to trying to understand about Driver back up generally, and in particular for Windows 10.
I do realise that Windows 10 during instillation and via updates is very good at keeping drivers update, so I don’t need to worry too much about them.. But my purpose of the exercise has been part of a general attempt to understand how Windows and Windows 10 works.

I am particularly confused with the different files that are produced by the different ways of doing it.

I do have an initial summary here, http://www.excelfox.com/forum/showth...ge39#post12662 , along with about over 300 posts starting here, http://www.excelfox.com/forum/showth...age2#post12122 , showing various cross checks and comparisons of files obtained from the various ways.. , but I don’t think you will want to view any of that. I certainly don’t. But I did it, and have attempted a very very brief summary here..

These are the ways I compared, on a new working, Windows 10 computer..

_ Files generated via a cmd or Powershell
_ Manually made listed from inspection of the Device Properties in the Device Manager Devices List. ( Lets call these Device Manager Properties List )
_ The back up files produced by a commonly used 3rd party Software, DoubleDriver
_ The files in the folder drivers ( typically found at like… C:\Windows\System32\drivers )
_ The files in the folder DriverStore ( typically found at .. C:\Windows\System32\DriverStore )

Here is a very brief summary of my findings..
The number of files generated by cmd or Powershell is relatively small. I can’t see that being of much use.

The files indicated in the manually made list from inspection of the Device Manager Properties List , Device Manager Properties List, are almost all to be found in the back up files produced by the Software, DoubleDriver . But there are lots of other files and file types in that list from Double Driver

Most of the files indicated in Device Manager Properties List, are given as being in the folder \drivers. That is to say, the path indicated is almost always to … C:\Windows\system32\DRIVERS……
But , in fact, they are not there at all, unless you compare with files names with extension .sys type from Device Manager Properties List to files with the same name but with a different extension, .sys.mui in the folder \drivers
In addition they appear in a Folder with the name \de-De .
So the full path is different to that given in Device Manager Properties List: - In fact the full path is actually like
C:\Windows\System32\drivers\de-DE\______.sys.mui
, not as indicated as
C:\Windows\System32\drivers\______.sys
I find approximately half the .sys files that are indicated in the Device Manager Properties List at … drivers\de-DE\______.sys.mui

Most of the files indicated in the Device Manager Properties List , are found in the \DriverStore folder, but they are grouped in many folders each with a few files in them. These small Folders are then themselves in a Folder with the name \FileRepository . So we are looking at a path of like
C:\Windows\System32\DriverStore\FileRepository\One OfManyFoldersWithAFewFilesInIt\_____

In order to find the files in the back up from Double Driver in \drivers Folder, then once again we must compare .sys files from the Double Driver back up to .sys.mui in \drivers\de-DE\__ .
But we have a lot of other files and file types in Double Driver which are not to be found in the folder \drivers

Almost all the files given in the back up from Double Driver are to be found in the folder \DriverStore.
But in addition there are a lot of extra files and file types in the Folder \DriverStore

These are the three things, I would be interested in any comments to..
_1) My research has chucked up thousands of information on the internet to explain how to do the different ways. I can’t find any information to explain the different results from the different ways, not even at sites explaining more than one of the ways. This is what is puzzling me the most. Has anyone got any explanation or comments on the different results obtained from the different ways
_2) The cmd/power shell way seems not much use
_3) Why don’t people just copy the entire \DriverStore and be done with it. Since that would appear to me to have all ( and more ) than you need.

I realise, that some things may become clearer when I do a re install and then look again at the Driver issue.
But I doubt I will get around to that for a while. So I just thought I would see if anyone has any comments on my observations so far.

Thanks

Alan

**DocAElstein** · 03-20-2018, 04:09 PM

http://www.eileenslounge.com/viewtop...=34247#p265648

Originally Posted by CraigS26

A guest "expert" on the AskWoody.com blog offered this article for backing-up W10 & 7 Drivers, and HOW he did it is all I can offer.
I DO trust his expertise for capturing All essential Drivers should (ie) a corrupted driver occur, but I cannot reconcile this with the Double Driver issue..
I got 135 Drivers from the method and IF you accept this is a good backup plan maybe you can re-state questions from there - If Not relevant to your real needs, advise and Hans will pick-up from there.
https://www.askwoody.com/newsletter/...s/#langalist-0

Craig,
I seem to have been hit quite badly by last Tuesday’s updates, - almost every second thing I try to do is either different or broken…_
_...The mouse won’t work properly, Snipping tool is broken , things couldn’t be typed in the search window – had to spend an hour finding a keyboard that worked…haven’t found a mouse that works properly yet…… the usual “fun”
but I have tried to re look as best I can at my Driver lists along with that article you referenced…..

_ the article mentions to Show hidden devices in the Device Manager. I had not done that previously. In my case it just reveals three extra devices, giving me in total 34 new paths listed, all of which are not unique, so in total I have 9 new files. I have added those to my lists ### , and done some re cross checking.

Code:

Bildverarbeitensgeräte (  Image processing equipment  )
WSD-Scandienst
C:\WINDOWS\system32\drivers\ksthunk.sys
C:\WINDOWS\system32\drivers\WSDScan.sys
		C:\WINDOWS\system32\drivers\WSDScDrv.dll
WSD-Scandienst
C:\WINDOWS\system32\drivers\ksthunk.sys
C:\WINDOWS\system32\drivers\WSDScan.sys
C:\WINDOWS\system32\drivers\WSDScDrv.dll

Speichervolumes ,  ( Storage volumes )
Volumes
C:\WINDOWS\system32\DRIVERS\fvevol.sys
C:\WINDOWS\system32\drivers\iorate.sys
C:\WINDOWS\system32\drivers\rdyboost.sys
C:\WINDOWS\system32\drivers\volsnap.sys
C:\WINDOWS\system32\DRIVERS\volume.sys
Volumes
C:\WINDOWS\system32\DRIVERS\fvevol.sys
C:\WINDOWS\system32\drivers\iorate.sys
C:\WINDOWS\system32\drivers\rdyboost.sys
C:\WINDOWS\system32\drivers\volsnap.sys
C:\WINDOWS\system32\DRIVERS\volume.sys
Volumes
C:\WINDOWS\system32\DRIVERS\fvevol.sys
C:\WINDOWS\system32\drivers\iorate.sys
C:\WINDOWS\system32\drivers\rdyboost.sys
C:\WINDOWS\system32\drivers\volsnap.sys
C:\WINDOWS\system32\DRIVERS\volume.sys
Volumes
C:\WINDOWS\system32\DRIVERS\fvevol.sys
C:\WINDOWS\system32\drivers\iorate.sys
C:\WINDOWS\system32\drivers\rdyboost.sys
C:\WINDOWS\system32\drivers\volsnap.sys
C:\WINDOWS\system32\DRIVERS\volume.sys
Volumes
C:\WINDOWS\system32\DRIVERS\fvevol.sys
C:\WINDOWS\system32\drivers\iorate.sys
C:\WINDOWS\system32\drivers\rdyboost.sys
C:\WINDOWS\system32\drivers\volsnap.sys
C:\WINDOWS\system32\DRIVERS\volume.sys

	


WSD-Druckanbeiter ( WSD print provider ) 
	WSD-Druckgeräte
C:\WINDOWS\system32\DRIVERS\WSDPrint.sys
	WSD-Druckgeräte
C:\WINDOWS\system32\DRIVERS\WSDPrint.sys
	WSD-Druckgeräte
C:\WINDOWS\system32\DRIVERS\WSDPrint.sys

Ref:
### ExplorerBefore DeviceManager V DriverStore3.xlsm : https://app.box.com/s/6dep3amv3ewvikvz0piuwx4k4qwkvt9m
http://www.excelfox.com/forum/showth...ge40#post12664

**DocAElstein** · 03-20-2018, 04:09 PM

[FONT=Arial][size=3] [COLOR="#000033"]

I have repeated the 3rd party DoubleDriver Software produced Files backup and while I was at it done a similar thing with the DriverBackup. I have not found a lot of information about DriverBackup. It my main research in the last couple of months it never came up.

This was the previous list from Device Manager Properties, along with the new hidden devices We had 20 entries, and now we have 23 entries
[size=2][color=black] Audio, Video und Gamecontroller (2)
Audioeingänge und

**DocAElstein** · 03-20-2018, 04:09 PM

slkhflskhfslkhf

**DocAElstein** · 03-20-2018, 04:09 PM

Updates Attack

I had the first major update attack last week .
I had done my best to differ updates since I bought the computer from new. I managed to delay the updates for almost 2 months.
Eventually when I tried to do anything related to updates, the options were greyed out, and red text came up saying something to the effect of …
You have already delayed updates many times. We are going to update your computer on this date: ______
They kept their promise.
Every second thing is changed or broken. I am still in the process of repairing things and/or bringing back data that has been corrupted.
Amongst other things, some changes have been made to the Driver files held on the computer. These were relatively small change. I will attempt to summarise these in this and the following posts.