forums.wsusoffline.net

I have bought a used Dell XPS 15 with Win7 64bit.
I just reinstalled Win7 with the DVD, and wanted to install updates with WSUS. But the DVD looks blank, except for a *.ini file when i put it into the XPS 15, and there is also no autorun.
Then I loaded the DVD in my Desktop (Win XP 32 bit), and the DVD looks normal.
I have used WSUS many times without problems, so I don't understand this.
The ISO is made on my desktop which is 32 bit, but I made it for Win 7 64 bit. But I am not familiar with 64 bit Windows.
I presume that the DVD drive is working, since I am able to install a Win 7 DVD.
Please help me. Is this a 64 bit problem, a Dell problem or another problem?

What is the content of the .ini-file?

On the DVD, I only see Desktop.ini

Code: Select all

[.ShellClassInfo]
LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21815

Naturally I see no Desktop.ini when i load the DVD into my Desktop drive. Here the content of the DVD looks absolutely normal.

I think the laptop detects a blank DVD, because Win7 tells me that I can start adding files for writing on the DVD

I have now tried to feed the labtop with a 32bit WSUS DVD, and it looks normal....

I will therefore try to burn a new DVD from the ISO file, and will return here with the result.

Exactly the same with another DVD made from the same ISO file.
Is the ISO file corrupted, or can I not create a 64 bit WSUS on a 32 bit pc

Do the contents of other DVDs show?

Yes. As I wrote, I tried to put a 32bit WSUS DVD in, and it shows correctly and autostarts.

Please try to manually burn the client folder onto a DVD (do not include the folders "o2k*", "w60"/"w60-x64", "w62"/"w62-x64", "w63"/"w63-x64" and "ofc") using the default Windows burning software. Try to load that DVD.
Just to check, if it is a filesystem problem...

Is your x86 DVD older than the x64 one? If yes, how much (E.g. one year older, one month, I don't need the exact date).

The 32 bit one is from 07/2014 and the 64 bit one is from 09/2014.
I will try the folder burm methode tomorrow.
Do you want me to upload the iso image?

@aker: If we think alike, it could be something with the new mkisofs we use now.

@Pamela: No, the ISO is quite large. Essentially we all use the same mkisofs tool and thus do all generate the same ISO. We just have to check what your PC doesn't like. For example, it could be something with the UDF driver on your system. Please don't mind the technical mumbo-jumbo that follows.

Technical info @topic:
Old string (used in July):

Code: Select all

..\bin\mkisofs.exe -iso-level 4 -joliet -joliet-long -rational-rock -exclude-list %ISO_FILTER% -output %OUTPUT_PATH%\%ISO_NAME%.iso -volid %ISO_VOLID% ..\client

New string (used now):

Code: Select all

..\bin\mkisofs.exe -iso-level 4 -udf -exclude-list %ISO_FILTER% -output %OUTPUT_PATH%\%ISO_NAME%.iso -volid %ISO_VOLID% ..\client

Interesting... The old string used ISO9660 and Joliet. That means, an ISO created in July would work, even if the UDF driver was b0rked. The new string uses UDF exclusively so if UDF is broken an ISO created now doesn't work at all (theoretically there's still ISO9660:1999 but there seems to be a problem with it).

Changelog for that change:

- CreateISOImage.cmd and CreateISOImage.sh scripts will now create UDF instead of Joliet formatted ISO images (Thanks to "tapek")

I don't see the folders that I am supposed to exclude