Windows 10 and Office Excel

**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.

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

Original Device Manager Properties V after first major update

_ Some USB files have been repeated, and sorted under various manufactures Headings, including a lot which I do not have or know about
ExtraUSBNamesAfterFirstUpdates.JPG : https://imgur.com/qVWZQiR
Some corruption occurred of USB sticks were connected to the computer. I had a similar problem with a ransom virus sometime ago http://www.eileenslounge.com/viewtopic.php?f=37&t=19352 . Possibly the lesson to learn here is to remove all external storage devices , that is to say, generally do not leave them for longer than needed in the computer, and certainly remove them if updates might be expected.

_ Files associated with the mouse have also been duplicated. Problems were also experienced with the mouse and keyboard after the updates.

_ A file is added , kdnic.sys , belonging to a new listed Microsoft Kernel Debug Network Adaptor

_ Some system devices have been added, many of which are something to do with Microsoft
They result in new files volmgr.sys , basicdisplay.inf_amd64_307898c750ba9e44\BasicDispl ay.sys , basicrender.inf_amd64_ba2a8de08ea0d469\BasicRender .sys

Code:

 Hauptplatine		
		
Hauptplatinenressourcen		
		
Hauptplatinenressourcen		
		
Hauptplatinenressourcen		
		
High Definition Audio Controller		
		
		dmk.sys
		hdaudbus.sys
		portcls.sys
Hochpr„zisionsereigniszeitgeber		
		
Legacyger„t		
		
LPC-Controller		
		msisadrv.sys
Microsoft ACPI-Konformers System		
		acpi.sys
Microsoft Basic Display Driver		
	basicdisplay.inf_amd64_307898c750ba9e44\BasicDisplay.sys	
Microsoft Basic Render Driver		
	basicrender.inf_amd64_ba2a8de08ea0d469\BasicRender.sys	
Microsoft Hyper-V-Virtualisierungsinfrastrukturtreiber		






























Volume-Manager		
		volmgr.sys

ExplorerBefore DeviceManager Earlier and Marz17 2020.xlsm : https://app.box.com/s/gsgwwbqggel397ufnruegjyfst51p3g6

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

Cmd / Powershell Window command line way change after updates

After the update a major change has occurred to the lists produced from cmd or powershell
The small amount of files originally present are still there , but in addition a large amount of other files are now present.
This was the stand previously There were 5 folders and 61 files with these extensions:
sys 1
dll 15
bin 3
cpa 1
vp 5
els 4
bag 1
xml 11
js 3
gdl 1
cab 1
ini 3
cat 4
inf 4
pnf 4
gpd 3
exe 1
We now have 12 Folders, a couple of extra file types.
Here complete composition of 232 files is
sys 2
dll 46
bin 3
cpa 1
vp 5
bag 1
xml 36
js 5
gdl 3
cab 1
ini 51
cat 8
inf 8
pnf 8
gpd 47
exe 1
dpb 5
ppd 1

ExplorerBefore cmd Compare Marz 2020.xlsm : https://app.box.com/s/2qgxb0ut5f7fc22jq5x8csbq80fc1yp2
Macro used for above table http://www.excelfox.com/forum/showth...ll=1#post12835

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

DoubleDriver Software ( and DriverBackup Software ) Changes

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. ( I had to install .NET Framework 3.5, ( which is often needed in Windows 10, and in much of my research is suggested of one of those ”useful so missing from Windows 10, Windows 10 features”.. )
The Files in the back up produced from these two software are almost identical. There are just a few less in DriverBackup. These are some Processor .sys files and some other .sys files

DoubleDriver Software Changes Earlier and Marz 2020 after updates
The changes are not relatively high. Something has been removed to do with a snapshot, a Microsoft Hyper-V Virtualization Infrastructure Driver has been added.
A large number of files are no longer present related to ( non Microsoft ) third party printers.
5 Microsoft Media Drivers have been removed.
Some entries for the USBs are strange indicating that something possibly went wrong when fiddling with them.

Previously we had [ also in DriverStore ] ( also in 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]
cab 1 (1) [0]
bag 1 (1) [0]
ppd 1 (1) [0]
exe 1 (1) [0]
dpb 4 (4) [0]
Total 448 (360) [59]

We now have
sys 126
dll 10
bin 3
cpa 1
vp 5
inf 73
ini 73
cat 2
Total 294

It would appear that the large amount of 3rd party drivers have been removed. The other changes are the removal of half a dozen media things, including a “snapshot” thing, which may correlate to the broken Snipping Tool.
A “Microsoft Hyper-V Virtualization Infrastructure Driver” has been added.

ExplorerBefore DoubleDriver Driverbackup Marz17 2020.xlsm : https://app.box.com/s/zipl4e4m3oqup2n86nntwgkdc9p8oe8b
ExplorerBefore Double Driver Earlier V Marz 17 2020.xlsm : https://app.box.com/s/y2msnfnyiphpt7gxr6b874avn5l18s91

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

drivers Changes

The main changes are approximately 20 removed files from folders en-US and de-DE
Only 3 files are new

This was the composition before.
sys 3
dll 12
sam 1
dll.mui 10
sys.mui 125
Total files is 151
Total Folders is 13

After the update it has changed to
sys 3
dll 14
sam 1
dll.mui 10
sys.mui 105
Total files is 133
Total Folders is 13

ExplorerBefore drivers compare.xlsm : https://app.box.com/s/u31jzfb7a4skpluj0q8h46s223f92uru

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

DriverStore Changes

Almost all Folder names have changed, over 600 changeed folder names in total.
The most noticeable change is that a lot of files have been removed, approximately 850
There are about 151 new files Spread over approximately 25 new Folders.

Previous File composition of DriverStore was

Code:

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
 sam          0 
inf_loc   508
pnf       93
hlp       9
ntf       8
ppd       27
 tbl          0
icc          0 
dat       6
dpb       12
cty       2
msc       2
xst       1
 dll.mui        0
sys.mui         0 
Total files is  2783
Total Folders is    794

We now have

Code:

 sys       360
dll       138
bin       118
cpa       1
vp       5
bag       1
xml       57
js       5
gdl       11
cab       1
ini       65
cat       23
inf       664
pnf       32
gpd       72
exe       1
 sam       0 
inf_loc   495
pnf       32
hlp       5
ntf       4
ppd       6
 tbl       0
icc       0 
dat       7
dpb       5
cty       2
msc       2
 xst       0
dll.mui   0
sys.mui   0 
Total files is  2080
Total Folders is    689

These are the new files

Code:

 b57nd60a.inf_loc
backupwmbclass.inf_loc
hidspi_km.inf_loc
iaLPSS2i_GPIO2_CNL.inf_loc
iaLPSS2i_GPIO2_GLK.inf_loc
iaLPSS2i_I2C_CNL.inf_loc
iaLPSS2i_I2C_GLK.inf_loc
intelpmax.inf_loc
microsoft_bluetooth_a2dp.inf_loc
microsoft_bluetooth_a2dp_src.inf_loc
microsoft_bluetooth_hfp.inf_loc
microsoft_bluetooth_hfp_ag.inf_loc
microsoft_bluetooth_hfp_hf.inf_loc
netrtwlane01.inf_loc
Netwtw02.INF_loc
NETwtw06.inf_loc
SmartSAMD.inf_loc
UcmUcsiAcpiClient.inf_loc
wvid.inf_loc
AMDGPIO2.inf_loc
AMDI2C.inf_loc
BthLCPen.inf_loc
BthOob.inf_loc
c_linedisplay.inf_loc
fidohid.inf_loc
PerceptionSimulationHeadset.inf_loc
prnms014.inf_loc
AcxHdAudio.sys
acxhdaudiop.inf
amdgpio2.inf
amdgpio2.sys
amdi2c.inf
amdi2c.sys
b57nd60a.inf
backupwmbclass.inf
BthLCPen.inf
BthOob.inf
fidohid.inf
heat.inf
hidspi.sys
hidspi_km.inf
HidTelephony.dll
vhf.sys
iaLPSS2i_GPIO2_CNL.inf
iaLPSS2i_GPIO2_CNL.sys
iaLPSS2i_GPIO2_GLK.inf
iaLPSS2i_GPIO2_GLK.sys
iaLPSS2i_I2C_CNL.inf
iaLPSS2i_I2C_CNL.sys
iaLPSS2i_I2C_GLK.inf
iaLPSS2i_I2C_GLK.sys
intelpmax.inf
intelpmax.sys
microsoft_bluetooth_a2dp.inf
microsoft_bluetooth_a2dp_src.inf
microsoft_bluetooth_hfp.inf
microsoft_bluetooth_hfp_ag.inf
microsoft_bluetooth_hfp_hf.inf
e1i65x64.sys
eeprom_ar6320_3p0_NFA324i_5_RV_0520.bin
eeprom_ar6320_3p0_NFA324i_5_RV_0521.bin
eeprom_ar6320_3p0_NFA324i_5_RV_0522.bin
eeprom_ar6320_3p0_NFA344a_highTX_LE_7.bin
eeprom_ar6320_3p0_NFA344a_highTX_LE_8.bin
eeprom_ar6320_3p0_NFA344a_highTX_LE_9.bin
eeprom_ar6320_3p0_NFA344A_power1213_DE_0419.bin
eeprom_ar6320_3p0_NFA344A_power1213_DE_P87G.bin
eeprom_ar6320_3p0_NFA344a_VA_1.bin
eeprom_ar6320_3p0_NFA364xp_LE_1.bin
eeprom_ar6320_3p0_NFA364xp_LE_2.bin
eeprom_ar6320_3p0_NFA364xp_ssku.bin
eeprom_ar6320_3p0_NFA364xp_ssku_DE_0522.bin
eeprom_ar6320_3p0_NFA364xp_ssku_DE_0523.bin
eeprom_ar6320_3p0_NFA364xp_ssku_DE_0524.bin
eeprom_ar6320_3p0_NFA364xp_ssku_RV_0519.bin
eeprom_ar6320_3p0_SS_620.bin
eeprom_ar6320_3p0_SS_620_K.bin
eeprom_ar6320_3p0_SS_720.bin
eeprom_ar6320_3p0_SS_720_K.bin
eeprom_ar6320_3p0_TX8_clpc.bin
eeprom_ar6320_3p0_TX8_lte_clpc.bin
eeprom_qca9377_1p0_NFA435_olpc_LE_2.bin
eeprom_qca9377_1p1_NFA425_olpc_A_BC_CBXA0.bin
eeprom_qca9377_1p1_NFA425_olpc_A_T103HAF.bin
eeprom_qca9377_1p1_NFA425_olpc_A_TP203NA.bin
eeprom_qca9377_1p1_NFA425_olpc_A_TP203NAH.bin
eeprom_qca9377_1p1_NFA425_olpc_L.bin
eeprom_qca9377_1p1_NFA425_olpc_L_LE_1.bin
eeprom_qca9377_1p1_NFA435_olpc_A_TP401NA.bin
eeprom_qca9377_1p1_NFA435_olpc_DE_089C.bin
eeprom_qca9377_1p1_NFA435_olpc_DE_P87G.bin
eeprom_qca9377_1p1_NFA435_olpc_DE_P88G.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_10.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_11.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_12.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_13.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_14.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_15.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_3.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_4.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_5.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_6.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_7.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_8.bin
eeprom_qca9377_1p1_NFA435_olpc_LE_9.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_A.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_B.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_C.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_D.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_E.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_F.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_G.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_H.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_I.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_J.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_K.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_L.bin
LE_CTL_ar6320_3p0_NFA344a_highTX_M.bin
netrtwlane01.inf
rtwlane01.sys
cxwmbclass.sys
Netwfw02.dat
netwtw02.inf
Netwtw02.sys
IntelWifiIhv04.dll
IntelWifiIhv06.dll
Netwfw06.dat
netwtw06.inf
Netwtw06.sys
PCLmRenderFilter.dll
PerceptionSimulationHeadset.dll
PerceptionSimulationHeadset.inf
prnms014.cat
prnms014.inf
prnms014.PNF
MSMPS-manifest.ini
MSMPS-pipelineconfig.xml
MSMPS.xml
RdpIdd.dll
rdpidd.inf
rt640x64.cat
rt640x64.inf
rt640x64.PNF
rt640x64.sys
SmartSAMD.inf
SmartSAMD.sys
UcmUcsiAcpiClient.inf
UcmUcsiAcpiClient.sys
virtualdisplayadapter.inf
Vid.sys
wvid.inf

ExplorerBefore DriverStore Comparison Marz 2020.xlsm : https://app.box.com/s/oy8pnuizk6xng1msqlsxho7l8e0bi0t8
Explorer Before DriverStore Comparison Marz 2020.xlsm : https://app.box.com/s/4zx7b8d2gwjix7u68zit6o22x7q0kwm2