OT - Old (c.2011) Daz installers don't work on latest windows update.
pwiecek
Posts: 1,582
A week or so ago, I got a notice that Windows was reaching the end of support snd I should install the update. After the updare, Old Daz installers no longer work. I know I can redownload, but I'm concerned that other older programs will also stop working. I was able to run the installer under winXP on virtual box.
Has anyone noticed a similar problem?
Old Daz Logo.jpg
66 x 67 - 8K
Post edited by pwiecek on
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
You can unpack the exe using 3rd party software and manually install. Not sure about the rules for talking about such things, so I won't give out the name or link, but it's an open source github type thing.
FWIW I re-installed a couple of old .exe based products yesterday using the exe as the installer and didn't have a problem at all.
What I have found is that sometimes running the installer in XP or Vista compatibilty node as admin works.. On a few it appeared they were not working, but after about a 5 minute wait they pooped up and ran.. You could always install to a shared folder in a Virtual Machine and then copy to your library
Win10 gets worse and worse with its forced updates. I'm still on 1803 build, but no idea how long i can resist...
I delayed that update but will need to succumb soon
Well the last update (2004) improved Windows 10 a fair bit as far as Iray rendering is concerned. My 1080Ti now has 10.1 GB available for render, where as in the earlier versions it was 9.1.
Which Windows version were you on? The old Bitrock installers had been problematic for a while, the workaround was to cancel the "search for isntalled components" immediately (once it had run through and failed the installers were stuck until a system restart).
Interesting to know, thanks. I'm on gtx960 with 4 gb though (my pc is late 2015 config, with 16 gb ram and quadcore i5. one day will upgrade all.)
Didn't we have that issue some years ago with the old 16-bit installers? I thought all of them had been repacked to zips by now.
And no, @Gazzalodi - third party software will not work with them.
Funny, I keep using it. Extracts them just fine.
We might be talking about different installers then.
Never ran across any Daz .Exe package that didn't use the Bitrock installer.
the Bitrock installers can be unzipped with 7zip
Are you sure? I can't easily fish any out right now, but I'm pretty sure they were not self-extracting archives in a readable format last I tried.
am on my ipad and not starting up my PC to check but am pretty certain I extracted all the old archive freebies I had on a disc that way and merged them
I just tried that with 7zip. Looks like you can extract the payload separate from the install script if you open it as a "#" archive and grabbing it by the offset. The payload is all still a single file though, so it will need to be extracted again. The script probably has the offsets for each file built into it. I didn't get down into the weeds with it. The bitrock-unpacker is less cumbersome to use, but it still has its problems with the 32 vs 64 bit vfs that require the source to be rebuilt.
Before the Bitrock we had the InstallShield installer IIRC.
that might've have been what I was thinking of
and now I'm not sure which it was that had the searching for installed components dialogue that needed to be cancelled in later versions of Windows.
Probably InstallShield — I remember the relief when the Bitrock ones started coming out and I didn't need to have a quick mouse finger on the Cancel button.
Is this really off-topic though?
Installer VISE, not InstallSheild, I am told.
I've been doing that since 12:00:01 on the first day. That search was always useless unless The install was actually required to find something. Very problematic in Generation 2 and maybe 3. It got better in generarion 4 but Genesis backslid and turned turned it into a major pain.
Not to mention the pain in the "you know where", if the content you were installing, refused to install because you were not following the default installation paths... It was easy to fool the installers with a dummy "poser.exe", but some V4 addons required quite a lot of unnecessary work just to get them out of the container.