PDA

View Full Version : Warning 1909, Device setup error code 25028.



noahfrenzy
01.01.2005, 09:26
Operating System: XP SP2
Burning Software: Nero 5.5, 6
Anti-virus Software: Norton AV 2002
DAEMON Tools Version: 3.47

Hello,
I've been having serious Daemon Tools issues since reformatting and upgrading to SP2. Usually I can get the program to install if it's one of the first things I put on the box, but somewhere along the line the installation starts to fail instead.

I usually get a Warning 1909, saying that Daemon Tools "could not create Shortcut DAEMON Tools.lnk" It then says "Device setup error: code 25028 (0x61C4), 998 (0x3E6) . Contact your support personnel."

I have the daemon install log; here's the last part, right before the install croaks and it rolls the install back:


MSI (s) (90:98) [04:47:46:359]: Created Custom Action Server with PID 2164 (0x874).
MSI (s) (90:A4) [04:47:46:406]: Running as a service.
MSI (s) (90:A4) [04:47:46:406]: Hello, I'm your 32bit Elevated custom action server.
MSI (c) (1C:28) [04:47:46:531]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg

Error 25001. Device setup error: code 25028 (0x61C4), 998 (0x3E6) . Contact your support personnel.
MSI (s) (90!D0) [04:47:49:421]: Product: DAEMON Tools -- Error 25001. Device setup error: code 25028 (0x61C4), 998 (0x3E6) . Contact your support personnel.

Action ended 4:47:49: InstallFinalize. Return value 3.

Any ideas what is going on? This has happened on a few of my computers, all of them which had SP2 installed.

noahfrenzy
03.01.2005, 09:16
Well, I seem to have resolved this issue after reformatting again and narrowing it down while configuring the fresh XP install.

I feel dumb now, but the issue was a corrupted shell32.dll. One of the programs (PE Resource Explorer) that I had used to replace some icons inside it apparently did more than just change the icons. I've tested since then, and the same kind of icon work done from Reshack seems to be fine.

I hadn't even considered the possibility that the modified shell32.dll could have caused the problem, as it was supposed to only be icons that were changed.