Windows 10 and Office Excel

[DocAElstein]

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