Describe the bug
A clear and concise description of what the bug is.
Issue is that when using update-osdcloudusb -Drivers Microsoft, Sometimes it says the file already exists and then skip it, When you run the command again, it shows that its already downloaded when you missing some drivers.
Based on the log it looks like it uses the same name for 4G LTE north America, Twice, and it does not look for Verizon LTE.
This is repeated multiple time during downloading surface Drivers and a clean USB.
Knows missing Drivers
Microsoft Surface 3 LTE Verizon Win 10 1903
And Based on logs, the repeated drivers.
This info is not to claim missing drivers but to bring awareness of the possibility.
The following can be accepted, but providing the info so we are aware.
Surface Book 2, On the catalog, it shows.
1832, and 1793 are to be downloaded
however, SurfaceBook2_Win10_19044_23.092.25730.0 is downloaded. ( this can be a good thing but is misrepresented..)
Repeated instances with the following.
SurfaceBook3_Win10_19044_23.092.28627.0
Is there a difference between these
![image](https://private-user-images.githubusercontent.com/29134216/278212259-c6fc481d-92df-42b6-b299-0837c4cf66e8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwOTYyMDMsIm5iZiI6MTcyNDA5NTkwMywicGF0aCI6Ii8yOTEzNDIxNi8yNzgyMTIyNTktYzZmYzQ4MWQtOTJkZi00MmI2LWIyOTktMDgzN2M0Y2Y2NmU4LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE5VDE5MzE0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE5YjNiYjkxNjRmM2I2ZGNjMDA2MTNjMmNhNmM0NDFlNmY3ODRhNmRmMWNkYzRiNGZkZGVlOWRhNmYyMDkyN2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.kQHQ7IhTuYO4OdBwKkUyYAhB91XdzwpGq5RgetEra1g)
The only file that is downloaded is
SurfaceGo2_Win10_19044_23.093.19290_0.msi
Surface Pro 6 Commercial and Consumer (Same File Name) is there a difference here?
SurfacePro7+_Win10_19044_23.091.9841.0.msi
SurfacePro8_Win10_19044_23.093.30318.0.msi
SurfaceBook2_Win10_19044_23.092.25730.0.msi
SurfaceBook3_Win10_19044_23.092.28627.0.msi
SurfaceGo2_Win10_19044_23.093.19290_0.msi (it shows 3X Dublicate)
SurfaceGo3_Win10_19044_23.093.36099.0.msi (it shows 3X Dublicate)
SurfaceLaptop5_Win10_19044_23.094.39987.0.msi (it trys to download 4 X)
SurfaceLaptop4_Intel_Win10_19044_23.091.11395.0.msi
SurfaceLaptop4_AMD_Win10_19044_23.092.16939.0.msi
I am aware that it must be models sharing the same drivers. And probably, this means nothing. However, since i found an issue here is the report.
To Reproduce
Steps to reproduce the behavior:
- Go to '...' Run update-osdcloudusb -Drivers Microsoft
- Click on '....' Select all (No matter, In my case All Surface 3)
- Scroll down to '....' Click ok
- See error
VERBOSE: SourceUrl: https://download.microsoft.com/download/7/5/7/757B0C6E-0C22-400B-90EA-D8AFBD64CC16/Surface3_4GLTE-NorthAmericaUnlocked_ Win10_18362_1902003_0.msi VERBOSE: DestinationName: Surface3_4GLTE-NorthAmericaUnlocked_Win10_18362_1902003_0.msi VERBOSE: DestinationDirectory: D:\OSDCloud\DriverPacks\Microsoft VERBOSE: Overwrite: False VERBOSE: WebClient: False VERBOSE: Directory already exists at D:\OSDCloud\DriverPacks\Microsoft VERBOSE: Destination Directory is writable at D:\OSDCloud\DriverPacks\Microsoft VERBOSE: DestinationName: Surface3_4GLTE-NorthAmericaUnlocked_Win10_18362_1902003_0.msi VERBOSE: DestinationFullName already exists VERBOSE: SourceUrl: https://download.microsoft.com/download/4/C/7/4C7DA85D-03DE-4B89-B8E0-386437331C46/SurfacePro_Win10_19044_23.092.28606. 0.msi
Screenshots
![image](https://private-user-images.githubusercontent.com/29134216/278209114-c66baa5c-f5f4-4042-aa82-b6b011d30944.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwOTYyMDMsIm5iZiI6MTcyNDA5NTkwMywicGF0aCI6Ii8yOTEzNDIxNi8yNzgyMDkxMTQtYzY2YmFhNWMtZjVmNC00MDQyLWFhODItYjZiMDExZDMwOTQ0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE5VDE5MzE0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTA4YzBhYzhlNjQzMjUyNmE2MDI1YmVhNGY5MmVkMTc2OGIzZTI3NGYyYTUzM2ViZWVhNGUyYzgzZjllODFjMmImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.LrGdUej5ueVZxhXUv9XKlNXm4HnQqcX6DJ66v-9H-00)
![image](https://private-user-images.githubusercontent.com/29134216/278209140-77ebebe9-6431-42c3-aeb8-ecbf5450ef06.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQwOTYyMDMsIm5iZiI6MTcyNDA5NTkwMywicGF0aCI6Ii8yOTEzNDIxNi8yNzgyMDkxNDAtNzdlYmViZTktNjQzMS00MmMzLWFlYjgtZWNiZjU0NTBlZjA2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODE5VDE5MzE0M1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNhOGQ1MmYyN2FlOTMxODg1NDdjYjhmZTQ2ZDNjMWNlNGVkYmMwMWY2MThkNjkyZjA4NjJjN2JlMjk3MWVhYjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.vXxh9hcFrXwoUs14CgqJMfUuIVMOxj1DTZPdGcLy5sQ)
Desktop (please complete the following information):
- OS: [e.g. Windows 10 22H2 19045.3448]
- Version [e.g. 22]
Additional context
Add any other context about the problem here.
|
"Component": "DriverPack", |
https://www.microsoft.com/en-us/download/details.aspx?id=49920
Also, adding a feature request Where we have the option to download the drivers locally, instead of always redownloading per USB,