c0000218 Blue Screen Error (2000 Pro)

I had this question after viewing STOP: c0000218 (Registry File Failure) - Windows 2000 Server.

Hello everyone...after consulting with a few other forums on this topic, with limited success, I am hoping to find a definitive solution here on the Experts Exchange.

Having posted a number of topics on this issue elsewhere, I'll keep it brief: I have an HP Vectra desktop computer that runs Windows 2000 Professional, but the device was stricken with the c0000218 "Blue Screen Of Death" back in 2010. With the help of some online computer-repair forum users elsewhere, I've managed to make some progress in trying to troubleshoot the error In the past year-plus, but have unfortunately hit a bit of a standstill in the process, and no other forum users have been able to help me move forward. Which finally brings me here to the Experts Exchange page. To save some trouble, I will provide links to the other forum topics I've started, some of which have screen captures to illustrate my progress, at the bottom of this post.

Fortunately, much of the hard work has already been done by myself with the help of the other forums' users, so hopefully, that one helpful tip to get through my logjam can come from any one of you here on this site.

Thanks in advance for any helpful replies :-)

Microsoft Answers
Bleeping Computer [1] [2]
CNET Forums
Andre D.Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Joseph HornseyPresident and JanitorCommented:
Just holding on to that hold machine, huh?  LOL

Generally, if there was a problem reading a registry hive, you either:

A) Have a corrupt Win2K installation, or
B) Have a bad hard drive

I did see in your MS post that you were able to get the OS up, and there were some bad clusters which were remapped.  Then, you ran into other problems with profiles.

A great tool for profile stuff is called Transwiz from ForensiT.  In fact, I just used it today to migrate my old Windows 10 profile into my new logon.  It works beautifully.

Even if you get this up and running, you need to replace your hard drive immediately.  If you're running Windows 2000 and that's an original machine, you're most likely running an IDE hard drive.  SATA came out around that time, but was only just gaining momentum (if I remember correctly).  You'll have difficulties finding IDE hard drives.  Also, on IDE drives, don't forget to set the jumper to "Master".

Hope this helps!
Andre D.Author Commented:
Let's just say it has sentimental value...LOL :-)

Please forgive the lateness of my reply; I've been preoccupied with the fallout of a recent family emergency. But thank you very much, Joseph Hornsey; I am very glad you responded as quickly as you did, as users on other forums weren't nearly this swift with a helpful, useful response. I managed to see your response fairly recently before being free to reply; it was a little jargon-y, so I didn't catch on right away, but I largely got the gist of what you were trying to tell me. Plus, anybody who uses Professor Hubert Farnsworth as their profile pic has to know what they're talking about! X-D

The Microsoft Answers topic got me to where I am presently: it was based on a variant of this Microsoft troubleshooting topic that had been passed along to me by another user there. I had some questions and misgivings about the process that went unanswered there, so perhaps you might be able to put some things into perspective for me. Don't be off-put if I ask for clarifications on whatever you might say back -- I just want to be certain about your advice and make sure I understand it so that I won't make things worse.

  • I tend to get lost most easily when there's an overload of technical jargon, which may require me to read instructions a couple of additional times in order to get a better grip of what is to be done. On the troubleshooting web page, I was a bit thrown by the part which reads, "If you do not have a tape backup, include the backup of network servers and production workstations." I eventually took that to mean an external backup of the profile (sorry if I'm wrong about that; no one on MS ever bothered to clarify or correct this assertion). I asked what type of backup device would be suitable to carry that part of the troubleshooting process out (full disclosure, I have some external hard drives I might be able to use), but never got an answer about it. Perhaps you could be so kind to enlighten me?
  • I read in your reply about Transwiz being a possible vehicle to perform the phase of the repair in which the healthy new registry files could be transplanted into the damaged registry. How would I go about using it in this way? Feel free to be as intricate as you need to be, step by step by step if necessary, as it would be my first time using such a program for such a purpose. Again, I don't want to mess anything up and make a bigger mess of the problem.
  • Another comment you had made was in regards to the type of hard drive my device has: IDE versus SATA. To be honest, I'm not sure which kind of drive I have in this machine; this bad boy has had a few past dates with computer repair technicians over the years before its last (and current) error, with its most recent fix being done in 2006. With such repairs being done, its operating systems, and possibly its hard drives, have changed with each fix, so it may be possible that it has the SATA presently, but again, I'm not entirely sure. I suppose if you think it would be a good idea, perhaps I could create a backup of the hard drive once the error is fixed, and get a new hard drive for the device at some later point anyway, possibly using the Transwiz program you've suggested earlier. Feel free to respond with your suggestion on what to do once its up and running again.
  • To be honest, I have some misgivings about the troubleshooting strategy given to me on Microsoft Answers; I can't help but think that there could be a chance at some unintended consequences that may come from overwriting or replacing files in the damaged registry. Perhaps I'm concerned over nothing, but I provided some screengrabs on the forum post that showed that there was a subtle difference in the two files (understandably, since one of them is new), and wanted to know if doing the transplant of registry files might cause loss of some files or functions in the profile that needs the fix. Maybe the change is negligible, or could possibly be more serious, but I'd never heard from anyone who may have tried it before and could have given me some insight on what to expect. Again, probably making a mountain out of a molehill, but I would like to get a "benefit-versus-cost" understanding of what could come from carrying this out, if you've got some kind of an idea about it. Again, no one ever bothered to answer that for me anywhere else.
  • Lastly, I am always looking for a better and easier way to accomplish the goal of fixing the error. In fact, some pages I found in the course of my own research have advised against trying to pull something like this off, in the risk of causing damage to the overall operating system (which I really don't want to do, obviously). I don't pretend to be a flawless computer whiz by any stretch of the imagination, so I am always willing to ask for the help from those who know better. My last unanswered replies on some of the other forums gave a list of software programs and disks I'd found online which make claims to correct such errors as mine automatically, but I am understandably skeptical: if it were that simple, I wouldn't have waited this long to get the registry error fixed, nor would I have gone through the trouble with the current troubleshooting measures until now. Long story short, if there's a far easier, less complex, inexpensive (or free) way to fix this c0000218 error that I don't know about, please do not hesitate to tell me about it ASAP. I will be all too happy to give it a try once I get a chance to do so.

Again, thanks very much for caring enough to spare time to help me out with this. Apologies in advance if I don't reply right away. I look forward to getting your reply as soon as you can do so!
your drive is an ide drive - in the win2000 days sata did not exist yet
for fixing the problem - you best make a clone of this drive to another one, and work on the copy for security reasons
if worst comes to worst - copy the windows folde r over from a windows 2000 fresh install (delete the Original windows folder first)
5 Ways Acronis Skyrockets Your Data Protection

Risks to data security are risks to business continuity. Businesses need to know what these risks look like – and where they can turn for help.
Check our newest E-Book and learn how you can differentiate your data protection business with advanced cloud solutions Acronis delivers

Joseph HornseyPresident and JanitorCommented:

Here is the basic checklist I'd recommend you follow:

1.) Take a look at the hard drive in your computer and get the make and model.  Look it up online and see what kind of hard drive it is, etc.  If you're not sure how to do this, look for a video on YouTube.  You can also see how to compare IDE to SATA.

2.) Get drive cloning software (there are free ones out there) and make a copy of your existing drive onto a new hard drive.

3.) Install the new hard drive in your computer and see if it works.

If you can get both hard drives in the computer and read them, you can use the software I mentioned to transfer your profile settings into your new logon.

Hope this helps!
Andre D.Author Commented:
Greetings, nobus and Joseph Hornsey! Again, forgive the lateness of my reply; to repeat, I am presently dealing with a family emergency while simultaneously trying to find time to address this computer issue, so I'm not always free to respond swiftly to new comments.

I haven't had a chance yet to fully examine my computer's hard drive for you guys, as things have been hectic lately, but I've had a chance to give a cursory glance at some things: to specify, the computer which has the c0000218 error is a Hewlett-Packard Vectra VLi8 MT desktop model. I believe we got it secondhand in some way, so whatever modifications that may have occurred to the computer by its previous owners are unknown. And as I mentioned earlier, we had to submit the computers for repairs before, so if I remember the proper sequence, it went from Windows 2000 to Windows XP, and then to Windows 2000 Professional. I found the CNET specs for this model online, but there are some subtle differences with my particular version; when I have a chance, I'll take a closer look at my own equipment and give you the specifics later.

Another thing I wanted to ask, as far as correcting the error itself, relates to a number of possible alternative means other than the one I've already started using. To reiterate, the following link (https://support.microsoft.com/en-us/kb/156640) was what I'd been given to work with on the Microsoft Answers forum. In the course of my own digging of the subject, I found a number of links to assorted CD-ROMs and software download links which claim to correct such errors far easier than the method I'm currently trying to employ. I'll provide them below for you guys to look at and see if any of them are legitimate and may work better to remedy the problem:

That's all I have to share for now; once I'm able, I'll return to see what any of you have to share. Thanks a million in advance for all your help!

post the dmp file ple - find it in windows\minidumps
Andre D.Author Commented:
Hello again, nobus...could you elaborate, please? I'm not sure I fully understand what you're asking...
Andre D.Author Commented:
Also, for everyone else kind enough to spare time to read this topic, please feel free to take a look at the links I've provided in my earlier comment; if any of the alternate means found within them could work just as well, if not better, that the troubleshooting technique that is being employed at the moment, I would like to know about it :-)

I'd like to keep things as simple and as inexpensive as possible, so any alternative means of fixing the error are always welcome...thanks again in advance to the users of Experts' Exchange!

I will do my best to reply to any comments at my earliest possible convenience.
i ask you to post the dmp file
it is shown in the blue screen, and i posted where to find it
i don't know what you want more "elaborated"
Andre D.Author Commented:
My apologies, nobus...maybe I read your comment in a way that confused me, but I assembled the computer and figured it out eventually. I'm not sure if including a .dmp file would help much; the most recent file in that folder was from January 2009, but the c0000218 error that crippled the profile happened in March 2010, so I doubt posting that particular .dmp file would give any information on the present crash, considering the time gap.

Again, that's why I'm trying to weigh all possible options. If you still want that 2009 .dmp file anyway, just let me know, but other means to correct the error may need to be considered. I'm open to try whatever will work, as simply and inexpensively as possible.

Thanks again to everyone :-)
of course i want a dmp file file that relates to the actual problem
maybe your pc was reset for not making dmp files?see here how to set it  : http://blog.nirsoft.net/2010/07/27/how-to-configure-windows-to-create-minidump-files-on-bsod/
Andre D.Author Commented:
Welcome back, nobus! I'm glad to see your particular engagement on my issue, considering how little movement I've gotten from those on other forums.

I took a look at your link moments ago; I don't think my computer was reset in any way, but there just wasn't such a file created for the 2010 error. I'll try to take a closer look at the settings and such, and get back to you later about it once I'm free to do so. I also noticed that the link only shows tutorials for Windows 7 and XP, not 2000 Professional, so I don't know how well it would work in my situation, but again, I'll see what I can do.

As always, I welcome anyone's input, especially if it's easier than what I'm doing now lol.

Thanks again to everyone :-)
well afaik it works for all
Andre D.Author Commented:
Don't know if this would help anyone here, but I took a series of photographs and screen captures that might illustrate the issue a little better for everyone, just in case you may not have visited the "mirror" links provided in the original message. I will repost them here on Experts' Exchange for everyone's benefit; again, a lot of work has gone into this so far, so I can't imagine it would be too much trouble for anyone here to understand and offer possible solutions. To see the entire chain of messages in that forum post, feel free to visit the Microsoft Answers page by clicking the link provided in the original message.

The first image I will post is of the blue-screen error itself, which you can see below:

According to the error screen, the troublemaker that is preventing a successful boot is the "\SystemRoot\System32\Config\SOFTWARE" registry file. A user on the forum passed a link along to me for troubleshooting this error last year (which you will find has been provided in earlier posts here), but came across a snag, which is illustrated in the following image:

Of course, Joseph Hornsey has offered a possible work-around for this snag in an earlier reply, which I have not yet applied at this time, but hope to try eventually once I am able.

To reiterate, my progress thus far is based on the troubleshooting link given to me on the Microsoft Answers forum; to date, I haven't found any other known alternative fixes for the error, and I am always looking for a way to fix the error much quicker and easier than what I am undertaking presently. I'm not sure if the above information would be helpful to Joseph Hornsey, nobus, or any other user here, but perhaps the additional details will give someone a better understanding of the error so that a useful solution may be found.

That's all the time I can spare for now...I will check back on the forum sometime later once I am free, so I hope this latest message helps!

Thanks a bunch in advance for your replies
not sure, but try a system restore like this :
windows could not start because the following file is missing or corrupt:  \WINDOWS\SYSTEM32\CONFIG\SYSTEM
An easier way is to boot from a Bart PE CD (or UBCD4Win CD) and use the file manager for manipulating files. Here  the procedure :
1. rename c:\windows\system32\config\SYSTEM to c:\windows\system32\config\SYSTEM.bak
2. Navigate to the System Volume Information folder.
it contains some restore {GUID} folders such as "_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".
The restore points are in  folders starting with "RPx under this folder.
3. In such a folder, locate a Snapshot subfolder. This is an example of a folder path to the Snapshot folder:  C:\System Volume Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
4. From the Snapshot folder, copy the following file to the c:\windows\system32\config folder
6. Exit Bart PE, reboot and test

Use a fairly recent restore point from at least a day or two prior to problem occurring .

** you can add the other hives also with this procedure

http://www.nu2.nu/pebuilder/       BARTPE
http://www.ubcd4win.com/            UBCD4WIN
Andre D.Author Commented:
Hello again...please forgive the lateness of my reply, as I've been occupied by other matters in the last week.

As always, nobus, your comment is much appreciated. I've just had a chance to take a look at the links you've provided in regards to performing a system restore; I presume using the Microsoft support link you've given would work for Windows 2000 as well, since the tutorial focuses on Windows XP, but it seems a bit complex upon first read. I may need to read it a few more times before it makes enough sense.

According to you, the other strategy is much easier, using a CD-ROM to perform such a task.  I recall providing a list of links I'd found online which purported to do such a thing earlier in an earlier comment. While I would like to see if this strategy can be carried out, I've unfortunately discovered that neither of the links you've provided are currently active:  the Bart PE site has closed down, while the UBCD4WIN link redirects to a different website entirely.

Chances are, one of the links I posted before may lead to a CD-ROM that may perform that function, if not one of the specifics options made in the above comment...I will repost them below for everyone's consideration:


Again, sorry for taking so long to post a new comment, but the feedback has been promising so far. Hopefully, I will be able to get the job done and close this question with all of your help very soon!
best print out the procedure, and follow it step by step
Andre D.Author Commented:
Glancing over the Microsoft procedure again for good measure as we speak...

I've also run a quick search on "UBCD4WIN" and see that it is largely available as freeware now; I'm guessing I'd have to download it, open the .exe and burn its contents to a blank CD, and then boot the computer from the CD to make it work.

Of course, anyone is welcome to correct me
ubcd4win is an XP live cd, so you have access to to explorer, and can run commands
Andre D.Author Commented:
I've read the Microsoft procedure a few times, and some parts are beginning to make some sense, I believe. Luckily, I still have my Windows 2000 Professional CD-ROM from which I was able to install a healthy version of the operating system, so I might be able to carry out some tasks, such as creating the text files for the batch command. I'll still need to read the whole thing a little better, though before I feel confident enough to try anything...after all, the goal for me is to do no further harm.

As for the UBCD4WIN CD, I'm willing to give it a try since it seems simpler than the Microsoft troubleshoot -- I'm guessing it works just as well for Win2000Pro as it does for XP, and that it performs a more streamlined version of the same things suggested on the troubleshooting page. I'm always looking for an easier way to correct the issue painlessly, if possible...
i totally agree with you
back in time, these did not exist; you needed Norton commander
Andre D.Author Commented:
May I ask if there is any real difference between performing the system restore manually (as is suggested in the Microsoft link) or through the use of a CD-ROM such as the UBCD4WIN? I ask because both methods seem to employ the use of "restore points" to undo the registry error.

By my best recollection, the last best functional date for the computer was about March 9th, 2010, so if it would be as simple as winding the clock back to that date, then I'd like to lend myself to the safest possible means to carry it out.

To be safe, I'm still looking over the Microsoft troubleshooting link to make sure I really understand the process before I try it out, but I'm also seriously considering the "UBCD4WIN" option to minimize the threat of human error on my part (not that I have no confidence in myself to get it right, but Chaos Theory states that anything that can go wrong, will).

Thanks again
it is the same process - the cd makes it only easier ,to do, with less commands than the manual approach of MS
Andre D.Author Commented:
Great -- I appreciate the clarification.

I'm taking a hard look at both options, but I'm leaning towards the UBCD4WIN option; there's some subtle differences between the instructions posted in the Microsoft tutorial and the actual mechanics of my Windows 2000 Professional operating system, so I can't carry out the steps verbatim without trying to compensate for the differences. The theory is sound, though.

I'm also taking a good look at the Ultimate Boot CD for Windows option; unfortunately, the main website for the page doesn't seem to be around anymore (though the software lives on as freeware), so I'll have to do some digging to see how compatible it would be for my Win2000Pro OS (much of the reviews are predominantly for XP) before I go for it.

Never hurts to be as careful as possible; again, just trying not to make things worse :-)
i would just make the free cd - then boot from it, and check what you can do
if you want to be careful, make an image of the drive - or clone it to another disk, and work on that one
Joseph HornseyPresident and JanitorCommented:
So, I'm being a tiny bit sarcastic here, but considering the amount of time you've put into trying to get this ancient machine online, couldn't you have gotten a part-time job and made enough money to buy a new one?
Andre D.Author Commented:
I'll comment on Joseph Hornsey's response first, since this is the first new response you've posted in a while. I'll forgive your sarcasm to give you a genuine answer. :)

Just so you know, after the old desktop caught this error, we ended up getting a more contemporary desktop a few months later; it originally ran Windows 7 (or 8) before it met the qualifications for a free-of-charge upgrade to Windows 10. I also got a laptop computer as a birthday present in 2012, which runs Windows 7 (though it did not meet the Windows 10 upgrade conditions), so I'm not lacking in up-to-date equipment. However, the "ancient" machine is a bit of a passion project for Yours Truly: why not ask what makes somebody renovate classic cars when they can just get a part time job and buy a hybrid, for instance? Plus, as tends to be the case whenever a person's computer breaks down, I've got photos, Word documents, music files, videos, and the like that I would like to recover once I get past the booting issue (I've since invested in a number of external storage devices), and I believe I've shown quite a bit of patience with attempting to correct the issue on my own. As I commented originally, it's sentimental value.

In response to nobus, I agree. In doing my own digging, some places assert that all versions of Windows are compatible, while others assert that Windows versions starting with XP and going up to 10 are required. I personally find it hard to believe that Windows XP is the hard cut-off, at the exclusion of some earlier generations of the program, but I'm not afraid to do my due diligence and ask around a bit first.

Thanks again for your replies...TTYL
when i need to recover data, i Always hook the drive to a sata - or even ide cable
then copy out what i want
Andre D.Author Commented:
Certainly useful information for the next time, nobus...lol

Oddly, there's a lot of conflicting information about what operating systems will work with the UBCD4WIN, but some suggest that the OS doesn't matter and that such a program would work independently from it. Definitely good news, if it is accurate.

As always, I'll keep EE posted on how things go on my end.
>>   about what operating systems will work with the UBCD4WIN,   <<   you boot from the UBCD4Win, and are in a windows OS
so, it should work on all windows versions, afaik
i never had issues with the OS'es - but i must say i never used it very much
Joseph HornseyPresident and JanitorCommented:
Fair enough, my friend.  :)
Andre D.Author Commented:
Just back for a few moments...

Don't know how much this would help, but I took a few screengrabs while tinkering with the computer the other night and decided to post them here. I figured this might help give some insight on the registry files that are causing the problem.

In case you didn't know, I have two separate Windows 2000 Professional operating systems installed on the computer at the present time: the one damaged by the c0000218 error, and a duplicate installed last summer at the advice of a user on the Microsoft Answers forum. The first two show the two different profiles in the "My Computer" area, beginning with the affected "WINNT" profile and followed by the healthy "BKUP" counterpart:

Since the blue screen error itself specifically names the "SOFTWARE" file as the source of the problem, I took two other screengrabs of the file's properties in both operating systems. It also gave the actual file addresses, which might help in translating the Windows XP troubleshooting tutorial for the Windows 2000 Professional system, I would like to believe, Obviously, the newer one has less disk space consumption while the older one has more data (and thus, disk space) attached to it, which you can see for yourself in both images:

Also note the "Last Modified" dates; they're more in less in line with what I've shared already about when the error happened. The information in these images may be relevant to the discussion from somebody's view, so I'm submitting them for you all to examine at your leisure.

When I have more time, I'll be back to comment on developments...thanks :-)
is this when booting from the ubcd4win cd ?
can you copy your data ?
Andre D.Author Commented:
My apologies, nobus...I was booting normally this particular evening lol

However, I do have some intel on my research for the UBCD4WIN: since my last message on Experts' Exchange, I opened a couple of new discussions on the CNET and Major Geeks forums to clear up some of the confusion I had (there was a lot of conflicting information on whether or not it would work for my operating system), and I basically was given the okay on both fronts. The only stumbling block I've got ahead of me now was explained in the former thread about how to properly embed the program onto a disk. I initially figured it'd be as simple as download the program and then burn it onto a CD-ROM, but apparently I'll need to get hold of a separate program (IMGBURN was mentioned specifically) in order to execute the whole thing.

You ever use a Rubik's Cube and have a situation where you solve one side, but realize another side got jumbled in the process? It's a little funny, but I haven't come this far for nothing. Clearly, I'm a glutton for punishment, a sucker for pain, if you will...LOL. You all can check out the threads for yourselves if you'd like to give the thumbs-up or thumbs-down on what may have been said on either one.

That's all for now -- again, other matters keep me occupied, keeping me from pursuing this matter whole-hog. I'll be back eventually, everyone -- thanks in advance for all your help so far!

you said " how to properly embed the program onto a disk. "
what are you trying to do - and why do you need other soft???
Andre D.Author Commented:
I know, right, nobus?

As suggested to me by another user on the CNET forum, I apparently can't just download the UBCD4WIN program and then just burn it onto a CD-ROM; I'll just take a screengrab of what was posted there, and post that conversation snippet here so you can see for yourself. My portion of the commentary is found up top, while the response to which I'm referencing is bordered in red:

CNET forum discussion
IDK, perhaps I misunderstood what that user was trying to get across to me, but that's where things stand for the moment. Apparently, if I'm going to get a copy of the UBCD4WIN to work from, I'll need to follow those instructions to do it.

Of course, corrections are welcome here...perhaps that user is mistaken.
ifound the download here :  http://www.majorgeeks.com/mg/getmirror/ubcd4win,2.html
it is an exe file, and should create the cd without problem (did not do that)
Andre D.Author Commented:
Thanks, nobus; I presume the .exe version of the program can be burned onto a CD-ROM without the new software?
no - - you have to execute it - it makes the cd if i remember correct
here another one , in case you need it :  https://download.cnet.com/UBCD4Win/3001-2086_4-10550208.html?hasJs=n
Andre D.Author Commented:
Hello again, nobus; sorry for the long delay, but the last few weeks have been rough. Just now do I have the time to sit and get back to my various forums.

Thanks again for the links you've provided. Do I still need to create a CD, or do I just save a copy of the file to run on the computer itself? I'm a little burnt out with all the various things I'm handling (I'm tackling the computer problem in my spare time), so it doesn't matter to me if you feel you'd have to explain the whole process step-by-step.

Once I get the chance, I'll apply the fix and provide an update...thanks
again - you need to make a cd - why would the name be UBCD4Win ?
Andre D.Author Commented:
Hello again, everyone; again, sorry for the long delay. Had a few minutes to spare to revisit the thread...I've got a copy of the program and will try to burn a CD tonight to work with the computer for tomorrow. Once I get the chance, I'll apply the fix and provide an update.

As I said I would try to do once already, I'll simply open the UBCD4WIN application and subsequently move the contents onto a disk. Hopefully, that's all I'll need to do, considering the crossed wires I got on the subject before.
Andre D.Author Commented:
Back again...sorry to say with kind of a disappointing update. I've a lot to say, but I took quite a few screengrabs to illustrate what happened, so everyone can follow along step by step in the process.

As I said in my last message, I got hold of a copy of the program from one of the links provided above, so now begins the process of getting it onto a disk; full disclosure, I used my desktop computer which runs Windows 10 to do the disk-burning, and the type of CD-ROM I used were TDK-brand 80-minute/700-megabyte Data CD-R disks to conduct the CD creation. In the process of formatting the disks, I ended up receiving this message:

Possibly troubling, as the desktop I'm trying to repair is a generation older than XP, but I went ahead, selected the "Use as USB" option, and carried on. Being honest, I may have oversimplified it a bit; I started off by moving the application itself onto a disk, as seen below, and started the installation from the disk, as also seen below. It turned out to be a rookie mistake on my part, because the combination of the app and the files within was too much for the CD to handle, as is also seen below (there are three total images in a row seen below).

I hate to waste disks, so I tried to remove the application from the CD (lucky I had the forethought to keep several copies ready in different locations), but I can't seem to do that and free up space on the CD; every time I delete the file, it comes back inexplicably, and the "Erase This Disk" button is inactive in the folder for some reason, as you can see in the screengrab below. A bit off-topic, but if anyone can tell me how to clear the disk, I'd like to hear from you, if you please...

Ultimately, I had to format a second CD and start the install process from one of the copies of the UBCD4WIN Install applications, and the process went considerably smoother as a result; since I was creating a disk of the program, I saved the application's contents onto the newly-formatted second CD-ROM, as the sequence of screenshots below will show you:

From this point, the installation of UBCD4WIN seemed to go through without a hitch, but there were a few error messages that came up on some post-installation scans, such as the check for a WD5 hash that occurred soon after the setup completed. The next screengrab seen below was particularly concerning, because this is what happened when I tried to check the contents of the CD-ROM itself to make sure everything was installed to it properly:

Can't imagine that it takes an expert to see that this likely is not a good sign. The following morning, I tried to apply the disk to the affected computer; I first tried to boot from the CD-ROM, which didn't seem to work at all, and again, by booting through the OS and trying to run the disk from My Computer. Here's the screen capture I took from the latter:

I'm not sure if this is because of the formatting of the CD, or because of some corruption of the files saved to it, but the computer didn't acknowledge the presence of the disk at all, so apparently, something went wrong at some stage of this whole process. I'm not quite sure what, but that's where I stand right now.

I hope the inclusion of all these screen captures gives everybody a sense of the issue and what might've gone awry in the whole thing. I didn't come this far just to quit, so please feel free to chime in on where some misstep might've occurred, or what the next move should be from here.

Again, thanks in advance for any replies...
if the cd type is a cd rom -  that means it can be written only once - so you cannot remove anything from it
if you want to do that -you neeed rewriteable media, CD R/W   like these :  https://www.walmart.com/ip/Memorex-CD-RW-Rewritable-Disc/15268352
***note that not all applications will accept rewriteable media -  but it does not hurt to try

well - since you've been with this problem for some time - i tried it myself, in order to post some screenshots to make things easier
but -------------everytime i tried to install ubcd4win -  i got the hash error too
i don't know if it's corrupt, or a false warning - but i decided not to continue with this type of cd
 you can try the alternatives : https://alternativeto.net/software/ubcd4win/

or  : https://community.spiceworks.com/topic/504156-what-to-use-as-ubcd4win-replacement
Andre D.Author Commented:
In a twisted way, nobus, I'm glad that it isn't just me lol. Good thing I decided to include the screen captures to help illustrate how things went when I tried this. BTW, my heart isn't exactly broken over not being able to easily clear the disks; I just hate to waste them.

Believe me, I really appreciate all your help so far. I'll be sure to look over the alternative links you've provided and see what may be best moving forward once I have the chance to do so. I haven't a wealth of time on my hands with the craziness of my life right now, but it is something I want to get done very soon. :-)

I'll be back to post my update on the situation whenever possible...thanks
are you sure that old pc supports USB??  in the xp time there was only crude usb available = usb 1 very slow
so first i'd try the CD option
if you post the link you took it from, i will try it here, so i can better assist you
Andre D.Author Commented:
Sure it can...I used USB fairly often with that device, even nowadays for this repair effort: it's a Hewlett-Packard Vectra VLi8 MT desktop model with two USB ports in back. Probably not as swift or advanced as later models, but nonetheless effective. To answer your other question, I believe I used the Major Geeks link to the program:  http://www.majorgeeks.com/mg/getmirror/ubcd4win,2.html

Was lucky to have found a few minutes to check your message, nobus...again, very sorry for the wait.
well - i don't see usb mentioned here ::       https://www.cnet.com/products/hp-vectra-vli8-piii-550-mhz-monitor-none-series/specs/
you also mentioned formatting the cd -  inever had to format a cd
will try it for myself, and post back

the wait is nothing to me - i'm around
Andre D.Author Commented:
Sure thing...couldn't thank you enough. Also, thinking back, I might have used the CNET link you gave me instead:  https://download.cnet.com/UBCD4Win/3001-2086_4-10550208.html?hasJs=n

Not sure if that would make a world of difference, but I'll try whatever works.
i did install it on my fast pc - running windows 10
have to test making the the cd still; i must find the needed files for making the PE recovery
Andre D.Author Commented:
No problem, nobus...take your time. I've certainly waited long enough as it is.

I haven't checked out those alternate program links yet, but I may be free later in the day tomorrow to do so. Otherwise, let me know how things go from your end whenever you can.

Thanx again
ok - i made the UBCD
here's a shortlist of what i did :
1- do NOT make the UBCD on a windows 10 system; i was unable to make it work
2-i made it on a modern windows 7 system 64 bit
3-installing the software on the disk was - fairly- easy, some popups, but it worked
4-making the cd i ran the utility, and had to find an old XP cd, in order to have the files needed, i copied that into the UBCD4WIN folder in a separate XP folder
5-then i ran the the utility, i choose to make an iso (first selection) (because the iso is just a file on disk, and if everything is ok, you can burn it to cd
6-then i burned it to a cd using CDBurnerXP  and selected to burn an iso file
no problems  when booting

if you need more info - just ask
Andre D.Author Commented:
I read through your shortlist a few times, so I think I kind of get what you did. Almost exactly what was said in my CNET forum topic I'd mentioned before. I'm glad you were able to make it work for you, but on first glance, I may have some limitations to get around:

  • The first two points are pretty straightforward. Probably explained away everything that went wrong when I tried it. Using Windows 7 instead of Windows 10 seems the way to go, but on my end, there's a problem: the desktop from which I attempted the CD creation did run Windows 7 originally, but got a free upgrade from Microsoft to Windows 10 a few years back, so stepping back to the older OS might be more trouble than it's worth just to perform this one function. Ironically, my laptop (from which I compose this comment now) was not compatible for the Windows 10 upgrade, and thus still operates on Windows 7, but the problem is that the laptop doesn't come with a disk drive. Perhaps an external CD drive could be connected to my laptop, but I do not currently have one to use or borrow for this process.
  • As for "making the cd," that may be a challenge as described, because I don't have an XP CD to carry it out. Of course, I do have a disk of the 2000 Pro system, and have already created a separate profile on the affected computer (as past screengrabs posted here and elsewhere have demonstrated), but I'm not sure if it would work just as well for myself.
  • Everything else described in the process seems to make sense so far, nonetheless. I didn't create an .iso file, but instead burned the entire program to disk when I carried out the process shown in my comment weeks ago (https://www.experts-exchange.com/questions/29088298/c0000218-Blue-Screen-Error-2000-Pro.html#a42596206). I presume CDBurnerXP is part of the Windows XP operating system (been a long time since I last used it, and I'd never burned a CD with it when I had it), but maybe a suitable substitute could be found if needed, if not the program itself.

I'm not totally discouraged, though; I'm sure this could still work out somehow with a bit of brainpower and effort. If anyone has any ideas on how to make it happen with what I've got available to me right now, I welcome your comments. I'll try to find time to view and respond whenever possible -- thanks :-)
>>  but the problem is that the laptop doesn't come with a disk drive.    <<   you can create the iso file on it, and make the cd on the other PC
>>   Perhaps an external CD drive could be connected to my laptop,     <<   sure - at about 20$  - not a problem

>>   I do have a disk of the 2000 Pro system,   <<  take a screenshot of its contents, and post it here - maybe that works
otherwise look for some one that still has an XP cd, Original, or OEM does not matter

>>   CDBurnerXP is part of the Windows XP operating system    <<   NO - it never was, you can still download it
you can download it here  https://cdburnerxp.se/nl/download

no thanks needed - a beer will do!
Andre D.Author Commented:
With all I've got going on in my personal life right now, we'll split a pitcher or two lol

Money's a bit tight, but I suppose I could do some digging for a reasonably-priced CD drive for my laptop one of these days. Of course, if I could create the .iso file w/o one, I could do that, too; would probably be faster than waiting for me to buy a drive...

I'll work on that screenshot of the 2000 Pro contents fairly soon; I'm guessing they'd be found under My Computer on the desktop I'm working on? Otherwise, I'll just tinker around with it and see where that takes me (just want to be sure I give you the right stuff). I'll also see the CDBurnerXP link and figure out where I can possibly install it for this.

I'll try to be back to post again in a few days -- thanks
well on modern OS'es you can do that - create an iso file, and mount it
i'm not sure if windows 2000 supports that
on XP it goes like this :  https://software.berkeley.edu/faq/general/how-do-i-install-iso-file-using-windows-xpvistawin7
Andre D.Author Commented:
Finally had a chance to check out the link...as luck would have it, I actually have 7-Zip on my Windows 7 laptop. I installed it years ago to open some .rar files, but according to the Berkeley article, from what I can tell, it can be used for .iso files, too. I'll need to take a closer look at it, but it's a lucky coincidence for me!

If you come up with any new information before I do, please don't hesitate to reply -- thanks :-)
Andre D.Author Commented:
Talk about dumb luck...

Recently, I recalled something pretty significant: as it turns out, I actually have an external disk drive right now!

Back in 2015, I bought a Memorex Slim External CD/DVD Writer and a 30-pack of Memorex DVD+R disks from WalMart; the thing was, I had bought it with the intent to use it for a completely different purpose, as I was hurriedly trying to find a way to record programs off of a malfunctioning DVR satellite receiver, but since it wasn't compatible for what I was trying to do at the time, I kind of figured it would be useful nonetheless and just set it aside for when/if I got the computer fixed, and never really thought too much about it since. I never even used it, with the exception of removing it from its shrink-wrap and packaging just that one time.

Just out of the blue recently, the thought crept into my mind that I could bring it out of stasis and possibly use it to create this UBCD4WIN from my laptop; coupled with the fact that my Windows 7 laptop already has 7-Zip on it, this might work out perfectly. The CD/DVD Writer is USB-powered, and I may even be able to get away with using the blank TDK CD-ROMs from before (doubt I can use those unopened blank Memorex DVDs) to do this thing.

Long overdue to have some good fortune come along for this occasionally-frustrating effort.

I don't know when I can try this whole thing out; glancing at the box for the Writer, I'll need to set up some trial software which may or may not clash with my version of Windows 7, plus any other stuff that may come up to complicate everything, but so far, this development seems pretty promising!

If there is anything anyone would like to add or advise, I'll try to return ASAP for a reply -- thanks :-)
not at this time - just go ahead and see where it brings you
Andre D.Author Commented:
Hey nobus -- I took another look at that shortlist you posted, along with the Berkeley link as well; I think I'll take a crack at creating the UBCD4WIN .iso file from my Windows 7 laptop to get through the 3 most likely phases I'll have to take in correcting that c0000218 error:

  1. Use my Windows 7 laptop to create the .iso file for UBCD4WIN.
  2. Burn the .iso to disk, either on my Windows 10 desktop or with the CD/DVD Writer I recently posted about (the 7-Zip strategy in the Berkeley link may also apply).
  3. Run the CD-ROM on my Windows 2000 Professional desktop to correct the error.

I might need a little more instruction on what I may need to do, as far as phase one is concerned...using the CNET link to the program, I'm wondering how I would go about downloading the program to create an .iso file out of it. Doubt it is as simple as "Save File As: ISO" or something like that.

I figure it's better to take the risk of sounding a bit dumb in asking for the proper execution method, rather than fly in blind and really screw up.
you did not read it correct i fear; i executed the ubcd file, it makes a progam you have to run - and from that you make the cd, or iso file (whioch i choose)
Andre D.Author Commented:
Okey-doke...clarification requests help in situations like this one, obviously. So you're saying to just go through the normal UBCD4WIN install process like before (except in Windows 7 this time), and from there, create the .iso file when the "Save As" options come up?
NO that's not what i said :
>>>>>>>> i executed the ubcd file,
>>>>>>it makes a progam you have to run -
>>>>>>and from that you make the cd, or iso file (whioch i choose)
Andre D.Author Commented:
I can't help but think we're talking about the same thing, but each is explaining and understanding the other differently. Nonetheless, I gave it a shot, but something still hasn't clicked for some reason. To avoid confusion, I'll walk you through what I did and include screengrabs of the process.  To clarify, this was done on my laptop that runs Windows 7.

To start off, I used the CNET link to download another copy of the .exe file directly to my laptop, and right-clicked to Run As Administrator. After an initial timeout error, the second attempt got the install process started, and I just went ahead to save the program directly to my computer, as the following three screen captures will show.

run as administratorstart of setupready to install
Like last time, the installation took a while, and resulted in another WD5 error message pictured below, but I did see that the program did install on my desktop, as indicated by right-clicking "Properties" on the file. also pictured below.

MD5 hash failUBCD builder shortcut properties
Problem was, once I tried executing the UBCD -- once with "Run As Administrator" on the icon, and another from the Start menu (screen-captured below) -- the following error messages came in, which are pictured below:

UBCD4WIN in Start menuubcd4winbuilder.exe missing shortcutubcd4winbuilder.exe shortcut problem
It looked like everything had downloaded properly, but the program of which you spoke didn't come in. Why, I don't know. But that's what happened so far. If there's anything to add, I'm all ears.
well - i got the hash error too - but the program was installed; i started it and made from it the cd
Andre D.Author Commented:
Might I ask how you did it, exactly? For whatever reason, the UBCD4Win Builder doesn't seem to be on my laptop at all, despite the whole install, and I'm trying to work backwards now to finally use the UBCD to make that .iso I need.

Omit no detail: what link you used to get the .exe of the program, any screen caps you took (if any)...whatever might help me grasp why it didn't go as smoothly on my end, please.

If you need me to take a screen cap of the UBCD file folder to see its contents for yourself, let me know. Thanks.
Andre D.Author Commented:
OK...I've had a chance to go over these particular links from the Google search:

I'm wondering if it's possible to just download the UBCD Builder program separately (since the full program is already on my laptop) and continue from there. Ugh...I hate these stumbling blocks I keep hitting in doing this, but I'm still trying to make it work.

Of course, if anyone out there has anything to add on how to proceed instead, feel free to reply -- thanks :-)
sorry - was busy otherwise
will look into it asap
Andre D.Author Commented:
Much appreciated...I myself have also been fairly busy since my last message; so much so that I'm just now finding my way back onto the topic about a week later. If you find out anything that would be helpful, please get back to me when you can. I'll try to work/research solo whenever possible as well. Again, the help is greatly appreciated on my end.

it may take a couple of days more
Andre D.Author Commented:
Sure thing -- do what you have to. I'm getting a mite concerned, because the (incomplete) UBCD4WIN installation ate up a lot of disk space on my Win7 laptop, so I'm hoping to get the task done soon so I can free that space up again once that .iso file is created.

Again, get back to me as soon as you can, if you please -- thanks
i sure will do that, but still occupied with a couple systems, printers, and other things round the house, but next week, i'll find time i think
i'm not sure at what point you are, or what problem you have?
maybe post anothe rQ and close this? as its getting very long

in any case, when the ubcd is installed on my windows 10 PC, in order to run it it it must be in admin mode
best right click the UBCD4Win icon, select properties, > Advanced and click run as admin
also, make an XPCD folder on your drive, to which you copy the contents of the XP install CD
more instructions here :
Andre D.Author Commented:
Sorry for the wait, nobus (and whomever else might be following the topic) -- had some family troubles to address.

Just to recap briefly, I'd tried the UBCD4WIN install on my Windows 10 desktop before, but something about the process had caused the install to end in failure. You commented that the same thing happened to you as well, which led to your advice to try the process in Windows 7, since you got it to work successfully on your end. I did the install on my laptop, which runs Windows 7, but it didn't seem to work as well for me as it did for you, since the "UBCD4WinBuilder.exe" file somehow wound up missing following the install. That seems to be a critical fail in the process, since I apparently can't move forward in the creation of that UBCD .iso file without it.

All the hyperlinks above link back to earlier comments in this thread explaining the progress (or lack thereof) made so far; you're right about the topic getting long, so I didn't want to trouble you looking through the whole thread again yourself, but looking at those specific replies of mine a second time around might help you.

I've also glanced at your recent response about trying again in Windows 10 with "Run As Administrator" -- not sure how much of a difference it would make from the first time, but I'll see what I can do. I also browsed the RM Prep USB tuturial link a little, and will have to read it more thoroughly later; sorry, but it's half past 1AM where I am, and it's been a tiring few days to use my full level of focus right this minute.

Nonetheless, thanks a bunch -- will reply whenever possible later
ok - het has error i got too - but the UBCD was installed; and looks ok to me
when you run it you should make a folder XPCD ( did you read how to use it?) in which you copy the contents of a whole XP install cd
did you do that? it should work ok then
Andre D.Author Commented:
Oh okay...that part I didn't do, because I don't have an XP install CD handy. Don't know if I'd have to buy one, or if I can get said XP contents online (getting access to the XP system seems to be the trickiest part of this latest strategy), but it could make the difference, I think. Also, as an added bonus, my Windows 10 desktop has more available disk space for me to use than my Windows 7 laptop, so it might be more convenient to try it this way. That having been said, I'll just go ahead and uninstall the contents of that incomplete UBCD install from the laptop so I can get that disk space back.

Again, will try to reply when I'm free to do so -- thanks
check if none of your friends has an XP install CD
Andre D.Author Commented:
Will do. Not sure if I've got any friends with a Windows XP install CD, but there's a couple of computer shops near my house; hopefully one of them'll have it for cheap, so whenever possible, I'll ask around.

I also have a tab open on my browser dedicated to the RMPrepUSB link, and will try to find time to really look it over -- the article's pretty long, and I've got too much involved personal going on by the day to knock it out in one sitting. But I'll make it happen.

Don't know how soon I'll be back, but thanks for the reply
if you google windows xp iso , you get lots of sites to download it
Andre D.Author Commented:
Once again, sorry for the wait, nobus. But I'm glad to have caught your reply; you may have saved me a trip, not to mention anywhere between ten and ninety dollars.

Stop me if I get ahead of myself, but judging from what I've read of your suggestion, could I presume that this is what I'll have to do moving forward?

>>> Get a Windows XP .iso file
>>> Use the Windows XP .iso file to create an install disk
>>> Perform a Windows XP install on my Windows 10 desktop computer (or use the .iso to get a copy of the OS w/o a full install)
>>> After the install, carry out the UBCD4WIN installation as before
>>> Hopefully, be able to create the UBCD4WIN .iso, make the disk, and finally apply it to my affected computer

I'm just speculating, so if I'm wrong, please correct me -- thanks
no - you got it completely wrong
all you need is copy the files from the install disk to a folder in the UBCD4WIN folder
you don't have to install XP !
Andre D.Author Commented:
Cool -- just wanted clarification. Honestly, even I didn't think an entirely new OS install was necessary here, so it was better to ask exactly what the Windows XP .iso file's role was in the whole strategy. I still have the UBCD4WIN .exe files from before; now I just need to get ahold of the Windows XP .iso from the Softlay link you provided, and get the install files copied to the UBCD folder. Better to get it completely wrong before I tried anything, so I totally appreciate your correction.

Hopefully, Windows 10's disk burning software can allow me to make both disks from the Windows XP and (hopefully) UBCD .iso files. Since I still haven't been able to successfully do so yet in past attempts, I won't really know until I carry it out. Hopefully the next time I come back for a comment, I'll have already tried it and have some screengrabs ready again to share what happened. If there's anything I need to know beforehand, feel free to comment again -- thanks.
note that you'll have to unpack the files from the iso - or mount the iso first
Andre D.Author Commented:
Much appreciated -- it may be a while until I get a chance to try it all out, but hopefully, whenever I get back, my next message will be posted after I finally get around to it. As before, I'll try to include screengrabs and a step-by-step walkthrough on what was done, for better or worse.

I'll reply as soon as I can -- thanks a lot :-)
it's getting time to close this Q and start a new one Andre
Andre D.Author Commented:
OK...finally, I'm back, and just got finished with a couple attempts over the past weekend to try to get the UBCD4Win application working properly. As before, I took a series of screengrabs to help illustrate what I did (and linked back to older comments wherever necessary), and will do my best to explain everything step by step. As had been suggested before, I attempted the UBCD4WIN .iso file creation process on my Windows 10 desktop again.

For the first attempt a few days ago, the only real difference for this time was that I opted to try the whole process from one of my external hard drives to hopefully give me more disk space to work with. It shouldn't have made any difference, I figured. First things first, I went ahead and did the one thing I hadn't on the other attempts: I got hold of a copy of the Windows XP operating system, found at this link. After downloading the programs, I used 7Zip on my Windows 7 laptop to unpackage the files, as the next two screen captures will show.

From there, I took everything to the Windows 10 desktop and tried the UBCD program install with "Run As Administrator" selected (even though I'm certain that I have administrator's privilege on the computer anyway), and saved the program to the external hard drive; once the process completed, I took the recommended step to copy the Windows XP contents into the UBCD4WIN folder. Unfortunately, the problem that I had before when I tried to open the program was the same: the part of the program that apparently creates the .iso I need, the UBCD4Win Builder, wasn't installed when the process concluded. According to my computer, the closest match to the missing shortcut was from a program that had no ties at all to the UBCD installation. Again, you can follow the screenshots below; the last two are most telling, as you can see the XPCD folder added to the UBCD4Win folder, and the error message that came along at the end.

It wasn't until after I had called it a night for this attempt for me to realize that I'd made a modest mistake in copying the Windows XP contents to the UBCD4Win folder, so I gave it another try a few nights later; this time, I went ahead and did the whole process again, but decided to save the UBCD program directly to my desktop computer's C:// drive to erase all doubt. I was also careful to do the XPCD folder properly the second time around once the install got ready to wrap up. Despite a failed Integrity Check (the display ended up freezing), the UBCD4Win install process concluded again, and the Windows XP operating system got copied into the file folder properly; I even include a screen capture of the UBCD4Win file folder with the XPCD folder within it found below. Unfortunately, no change -- still got the missing shortcut error, and no UBCD .iso creation took place after this latest effort. All the screengrabs below chronicle most of the whole thing.

I'm kind of at a loss now; if I have any suspicion, it's that the .exe file I have of the UBCD4Win program is defective. For those who don't recall what I said in my last comment of which link I used to get it, I'm sure it was from CNET. Another option that might have to be applied is to get the missing item in the program as a separate download, as I'd suggested from some of the research i did solo a few months back. But clearly something has to be done differently, since practically nothing has worked so far. Feel free to look over what I've posted here and make whatever judgment you feel should be taken moving forward. Whenever possible, I'll try to apply it.

One final note regarding nobus' last comment, I may have to open a new topic and carry a parallel discussion in the near future, especially if my next series of moves is as heavily involved as the last couple fix strategies have been. If I go that route and open a new question, I'll post a direct link to it here in the hopes that those from here can follow along until the fix is ultimately completed.

That's all for now -- sorry that the news couldn't have been better. I'm as eager as anybody to finally close this topic. :-(
you should do as they say for the cd builder : make a folder for XP with the exact name they suggest in UBCD4Win folder
also - i would never use an external disk for such a thing -  i'm not sure that software handles external drives well; it may complicate things
Andre D.Author Commented:
Back with another update -- I've just made another effort to get the program working several minutes ago. As always, I've taken a few screengrabs to illustrate what happened, and I've also made a few changes in the routine this time around.

First and foremost, I did what I said I'd do in my last post and got a new copy of the UBCD4WIN application; this time, I used a copy of the .exe file I got from MajorGeeks instead of the CNET version I'd used up to this point. Another thing I did after the last failed attempt was to take a closer look at the RMPrepUSB link, seeing if I could follow the instructions a bit more closely or notice something I might have overlooked before. Once I got started, I was sure to copy the Windows XP content directly onto the C:// drive (something I hadn't done on past attempts), which the following image shows.

After that finished, I went ahead and tried anew to install the UBCD4WIN program, this time from the new .exe file, found highlighted in the image below. I did "Run As Administrator" from a USB Flash Drive rather than direct from the desktop, but I can't imagine it made that much difference.

I had to delete the UBCD4WIN folder created in the C:// drive from earlier attempts, but once the install process was underway, and after skipping the has check, a new element came up that hadn't been seen previously: the progress bar for enumerating files and folders, as seen below in this screen capture. It was a big deal to me, since this never came up on any of the other tries. I must've been on the right track, I thought, because the subsequent integrity check message suggested so. That screenshot is also found below. The clincher was the appearance of the license screen for the UBCD4WIN Builder, which booted after the install process finished -- something that had NEVER happened once in all the attempts made before. That screengrab is also seen below; take note of the fact that the "UBCD4Win" and "XPCD" folders are found in the C:// drive folder behind the license display.

Following the instructions found on the RMPrepUSB site, I tried carrying out the ISO build using the specifications found in the tutorial, as the first image below shows. The two images that follow show the construction of the registry files and the presumptive build of the ISO (apparently why the Windows XP operating system was so important in the beginning), but as the last image capture shows at the conclusion of this phase, something went wrong during the process, and the ISO file was never built.

Clearly, this attempt was the best so far, since the whole program got as far as it did with a few simple things done differently than all the other tries, but no matter what, I'm still stuck for whatever reason. I did take stake of a couple things in those last two images: in the middle image above, I noticed there were any number of CD-burning plug-ins that might've been helpful if I'd been successful in finally creating the ISO for the Boot CD earlier tonight, and in the bottom-most image, the content of the failed ISO build had been archived as a text document. I made a copy of it to attach to this post; hopefully, a more-trained, less-busy eye than mine might be able to see exactly what went wrong and why the ISO build failed. If anyone figures it out, feel free to reply, and I'll see what I can do to fix it the next time I get a chance to work with the program again.

Once again, I'm sorry that the news wasn't better -- I seem to be a bit closer than before, but I'm not quite there yet. |:-(
Trust me, I'm as eager to close this topic as anyone once the problem is resolved.
it looks like you have hard - or software errors somewhere
test everything, or try it on another PC
Andre D.Author Commented:
I'm afraid I don't have very much disk space available to try the whole process again on my Win7 laptop, so it looks like I'll have to test everything on my Win10 desktop and try again sometime later. If you notice the last screengrab in my previous post, there were only two errors, but they were apparently bad enough to derail the ISO build altogether. I'm not certain where the errors might be, nor what exactly could be done to correct them, but you are welcome to view the .log attachment at the bottom of my last post, and perhaps you could see where those 2 errors came in, since everything else seemed to coalesce just fine in the rest of the process.

Everything seemed to go by the book a couple nights ago, but it still hasn't clicked yet. To recap thus far, I went to WebForPC to get my copy of the WinXP operating system, and got my new UBCD4WIN application from MajorGeeks instead of CNET. Everything else was explained step-by-step in my last message, and the UBCD4Win Builder .log archive of the failed ISO build is added as an attachment at the bottom of the last message. I'll try to see what more I can do on my end as well, and perhaps I could try again sometime in the next several days, but feel free to reply in the meantime if anyone notices anything amiss.

Thanks again
when are you going to clos this Q?? it is VEEEERY long
i suggest you read carefully how to make the ubcd4Win, it works fine as described.
if it does not, you are making mistakes, or your OS is corrupted
Andre D.Author Commented:
OK, nobus -- wish granted. I surrender.

I won't close the question because it isn't answered yet, but since the topic has skewed towards getting the UBCD4WIN to work, I created a new topic to solve that question before I solve this one. I also give my word that I won't add any new replies until the UBCD4WIN issue is resolved and I'm ready to start actually working on the c0000218 error again.

To follow the new question, go here: https://www.experts-exchange.com/questions/29124967/Troubleshooting-UBCD4WIN.html
i'll monitor it, but will not post in it , in order to let others have their say
David Johnson, CD, MVPRetiredCommented:
why did you not go to the main site and get the .iso?

Whole bunch of alternate boot iso's
David, it's the UBCD4Windows he needs
David Johnson, CD, MVPRetiredCommented:
he doesn't need a windows environment all he needs is a command prompt to run regedit.. or am I missing something here
Andre D.Author Commented:
I've largely been going off of nobus' suggestions, as nobus has been by large the main contributing expert on this topic, but to address David's recent comment, I recall visiting the Ultimate Boot CD page once before (I still have my forum applicating pending, I believe), but not finding that download link; in fact, I think I found a forum post saying that their Ultimate Boot CD and the UBCD4Win were two totally different programs, so I wasn't so positive it would work to correct the issue. Since I haven't been activated on their forum to ask such questions, what's left except to try it, I suppose?

To address the other point David made, I'm not sure if I've ever tried the "regedit" suggestion, although I might have an idea what you may be driving towards; I'm almost sure that I've done something like it when I first opened the discussion on the Microsoft Answers forum, but as I recall, what I'd been advised to do was a scan command that didn't correct the actual error. If you have a link on how to carry out a "regedit" correction of the problem, please feel free to pass it along.
after rereading a bit your problems, you seem to like adding problems to the task.
you started using an USB drive - you should realise at the time the UBCD4Win was made, usb was nearly NOT  existing, so it does not recognise such drives
so i suggest to do ALL on the C: drive ( OS drive); if nneeded, free up the necessary space
it will make things a lot easier

i would say : uninstall everything you did ( but keep the good files and applications ( like the xpCD folder
then - with the new knowledge - redo it from scratch
Andre D.Author Commented:
Trust me, dear nobus, I am NOT interested in making more problems than I try to solve -- it just hasn't worked so far.

That's the main reason why I started the new "Troubleshooting UBCD4Win" topic at your repeated suggestion: I recall you saying that you would monitor the thread without participating, but my opening message in that thread was all about the most recent attempt to use the software, in which I did clear some of the clutter from earlier attempts, and did conduct everything on the C-drive, but in the end, all I got were a bunch of "incorrect function" messages before the program spat out an .iso file with nothing in it. I appreciate your latest suggestion, but it's been done already.

Additionally, one of the users on that other topic commented that not only was the Windows XP operating system likely a "contaminated" imperfect duplicate that couldn't sync well with the UBCD4Win program, it may not even work if I were to create a working CD of the UBCD4Win for that same reason, since the operating system in which I'm trying to fix is Windows 2000 Professional, and the UBCD4Win apparently still needs Windows XP to run its fix. Not that I wholly doubt your input on UBCD4Win being the probable solution, but so far, it's seeming like a square-peg-in-round-hole situation.

I'm sorry to have to expose you to all these failed attempts and updates, but I've been pretty concise in detailing what's been tried, and what went wrong. Again, if you want to comb over my last attempt with this builder, take a closer look at that alternate thread again: https://www.experts-exchange.com/questions/29124967/Troubleshooting-UBCD4WIN.html

Maybe you can leave a comment there, and we could centralize the entire UBCD4Win discussion on that page alone; once I get past that snafu, I'll be able to come back to this discussion after I deploy the program on my affected computer, and we can see where to go from there, for better or worse.
i hope you get a solution.
Andre D.Author Commented:
Believe me, I'm still working towards that solution; the UBCD4Win issue has been frustrating for no clear reason, but I'll hammer it out once I understand why it hasn't been working so far. Barring the UBCD4Win option, I repeat, I'm willing to try whatever will work, whomever offers it. I hope your latest message isn't implying that you are done trying to help with this particular issue, nobus; I haven't given up yet, so I hope you haven't either.

Sorry for the long wait between my last message and this one, BTW; just so you know, I'm having to help care for a couple of sick and elderly family members, so I don't have a lot of free time to monitor my topics and apply solutions, which is why I don't often return comments very quickly.
if you were near me, i'd gladly do it for you
Marc ZCommented:
Nobus, mail him a copy of the boot CD you were able to make.

Andre, you have copied the important data from this hard drive to those external hard drives you have purchased I hope.
i already deleted everything on that drive...
Andre D.Author Commented:
Hello everyone -- Happy New Year! Marc Z, welcome! As for nobus, you're always welcome lol

Again, forgive my lengthy absence, but at least I've returned with something positive to report: I've finally gotten around the kinks that have kept me from getting ahold of the UBCD4WIN program, which finally gave me the ability to close out the parallel topic I created on the subject.

In the lead-up to the Christmas holiday, I'd managed to free up a decent amount of disk space on my laptop and gave the UBCD4WIN install another chance; as a personal rule, I never call it quits on anything until all possible options are exhausted. All other attempts had been on my Windows 10 desktop, but using my Windows 7 laptop, things went significantly better. Not only that, I was able to finally able to create a proper .iso file on the very first attempt. Not too long into the new year, I went back to the Windows 10 desktop to use the Power2Go application to successfully burn the .iso to a disk, and finally got around to testing it out last week, and everything turned out okay. I admit there's a little bit of egg on my face, since this OS discrepancy had been brought up here before, but only recently was I able to free enough space on my Win7 laptop to carry it out properly. I've taken a bunch of pictures on my smartphone during the process, some of which I'll share here to show everyone how it went:

UBCD4WIN Boot ScreenUBCD4WIN Loading BarUBCD4WIN Desktop w/ Pop-ups
I looked back on this old message from nobus to try to move ahead with the registry correction process, not to mention scavenging around on the software to get a feel for everything, and I believe I may have found the program function to reset the registry to a restore point, as the pictures below show.

UBCD4WIN Programs-->Registry Tools-->Registry Restore WizardUBCD4WIN Specified C-driveUBCD4WIN Registry Restore Options
Thing is, as you can see in the last image above, the only restore point available is the point of origin for the operating system in 2004, which is obviously too far back from when the present error occurred. The ideal restore point would be early March of 2010, which brings me back to this earlier message...now that I have a functional copy of the Ultimate Boot CD for Windows, I need to know how to carry out the procedure to tweak the registry and restore the computer to right before the error occurred.

I'm glad I could finally come back with some positive news to share, so I hope someone can help coach me through using the UBCD4WIN to finally correct the registry error once and for all...

And thanks for your patience!
Andre D.Author Commented:
Decided to upgrade the question's priority to High -- perhaps this bedeviling question will finally get a bit more attention and involvement from fellow members with the upgrade.

Also, I wanted to post this screengrab of an earlier comment on this very thread for everyone's consumption:

As you may have seen in my previous post, I now have a functional disk of UBCD4Win (finally), but need a bit of coaching in how to conduct the above procedure. If anyone can help, please feel free to comment!

Thanks in advance!
did you try the above?  what happens?
Davis McCarnOwnerCommented:
Nowhere in this entire thread have we ruled out a hardware problem with the hard disk drive!  If there is one, nothing we do will ever fix it.
And, having done data recovery since the late 1970's on tens of thousands of disks, that is a crucial question.
UBCD4Win which I have used numerous times, by my recollection, includes the free version of HDTune.  You should run it, choose the error scan tab, and click Start.  It will take (possibly) hours to finish; but, if even one red box appears, the drive is toast and we need to proceed to a cloning operation to get away from failing hardware.  Please post back and tell me if the error scan was all green or not.
If it is clean, we can move on to restoring the registry files from the restore point (which I have also done several times); however, you will need to restore all of them as it is a set of files which should not be separated.
I, in this situation, would start by creating a \Winnt\System32\Config\RegBackup folder and copying the dysfunctional registry files to it for safekeeping. (*.) will get the system, software, security, and sam files.  Next we copy the registry files from the restore point snapshot folder to the config folder and delete the dysfunctional registry files.  The painful part is that we then need to rename every one of the REGISTRY_(whatever)_ (name) files to just plain (name) (i.e. REGISTRY_MACHINE_SYSTEM to SYSTEM) as those are what Windows looks for when it boots.
After that has been done and verified, you should be able to reboot and voilla, it should work.
A caution; though.  If the SAM and SECURITY hives have become 256KB, the PC got infected and you ought to look for an even older snapshot folder from before that occurred.
Davis, i have recovered hundreds of "bad" disks with HDDregenerator, and i even cannot rember if one came back
but if the disk surface is damaged or scratched, or anything else hardware wise - no software can remedy it of course
Davis McCarnOwnerCommented:
About once every year, I encounter a drive with "bad sectors" that can be "healed" by forcing a rewrite of those sectors; but, in most cases (99+%), a hardware failure in a drive cannot be repaired because the drive was either physically banged or had a substandard part used in it's manufacture.  Even if I have to do a heavy duty data recovery, I always start with a clone of the drive so the original is not touched.
i have other experience, sorry
Andre D.Author Commented:
Glad to see your responses, nobus and Davis McCarn -- happy that you guys are willing to spare time to help out.

Before I get started, I just wanted to include this image on my computer's startup screen to illustrate what I'm after: marked with the red arrow is the part of the computer I'm hoping to fix, while the blue arrow has a parallel install of the same Windows 2000 Professional operating system.

In response to nobus, I had a chance to rummage around the disk and get a feel for the software, but couldn't figure out the means to edit the registry files. I'd never worked with UBCD4Win before, and since the main UBCD4Win website has been inactive, there wasn't any real tutorial I could find in order to do that. However, I recently noticed that there was an "Offline NT Password & Registry Editor" boot option on the opening screen seen in my earlier message from this week -- would that be where I should go to do that? Please get back to me about that once you're able.

In response to Davis McCarn, thank you for contributing your knowledge to the matter. I never felt the registry error was related to the computer itself, so I never really considered the option to look at that. In fact, based on other disk scans done on the computer in past efforts to address the issue, everything came up fine generally, and the drive seems to work very well, considering its age before the error struck. I'm still convinced that the problem is with the software and not the hardware, but I went ahead and took your advice to conduct the HDTune error scan from the UBCD4Win program. I've taken pictures on my smartphone to keep track of what happened, and I'll post them below:

The scan didn't take very long, but admittedly, the results were less than ideal. The scan results are in the image below:

While the drive was largely healthy, a total of eight sectors came back red, accounting for 0.3% damaged sectors overall on the drive, as you can see in the image above. A 99.7% health diagnostic on the disk doesn't necessarily bother me, but in your assessment, even one damaged component is too many. I still have my doubts about that being the ultimate cause, and am still willing to give the registry restore a shot, but I'm presenting the results for your dissemination on whether or not to continue on that path. Again, having never worked with UBCD4Win before, I wouldn't know precisely what to do -- that's why I find pictures and screengrabs helpful to explain what progress I've made. Even if this setback can be overlooked, referring back to my earlier message about restore points, I'm still dwelling on how to conduct the editing process to make more restore points available. But in any case, please post back about it.

Thanks again to nobus and Davis -- let's keep things moving
Davis McCarnOwnerCommented:
UBCD4WIN has nothing to do with the fact that your hard disk drive is failing.  Since the mid 1990's, hard disk drives have been intelligent devices that, for one thing, have a set of "spare" sectors which they are supposed to automatically start using whenever one of the primary sectors is failing.  That mechanism is, at the very least, broken and has an 80+% probability of being the cause of your initial problem.
When the drive hits a "bad sector", Windoze has never dealt with it very well and Vista, for example, will give the user a perpetual "spinning wheel of death", stuck forever trying to read that sector.
The most common result of a drive's failure, for whatever reason, is bad writes so the best answer is to stop doing anything that might write on the drive.  I would have connected the drive to one of the four PCs I have here, all setup to do data recovery, and immediately "cloned" (sector-by-sector copy) the failing drive to one which did not have problems.  I would then have copied your data files to one of my drives for safekeeping before I even attempted to fix the SOFTWARE registry error you get when you try to boot it.
That process is still the same.  Backup the current set of registry files, find a copy in one of the SNAPSHOT folders that looks OK, copy them to the CONFIG folder, rename them to the correct names, and then try to boot it.
But; as a huge note (!!!)), the more you mess with that drive, the worse it will get and nobody can repair a modern hard disk drive so either cloning or backing up is your first priority (period).
Andre D.Author Commented:
Thank you for the response, Davis McCarn -- while this path seems more complicated than just fixing a booting issue, I guess I will have to try to carry out your instructions as best I can, and as quickly as possible. I've waited long enough to fix this problem, and I'm ready to get this over with very soon.

Since you say that the first step has to be a backup, how would I go about doing it? I have a pair of USB external hard drives (one from Seagate, the other from Western Digital) which I may be able to use for this. I primarily use both of them to keep video and picture files, but both have about a 5TB capacity and lots of available space to "piggy-back" a disk backup for the time being. The question is "how?" I may have noticed a means within the UBCD4WIN to back up a drive in the way you describe, but I'm not certain of that, having only fiddled around with it a couple times so far. Again, this latest setback has now made my efforts to fix the error far more complex, so you'll have to be concise in explaining this so that I won't make any mistakes.

Once the drive has been backed up, do we go ahead with the registry editing method we've discussed until now? If so, I would like to understand how to do so in as uncomplicated a way as possible, step-by-step, if need be. Forgive me if I sound snippy in my typing, but after so many false starts, re-starts, and setbacks, this one being the latest, it would make anybody a little grumpled, as I hope you understand.

Long story short, what I've gathered so far for your response is:

PHASE ONE: Back up the damaged drive as is to avoid further damage

PHASE TWO: After backing up the drive, conduct the tweaks to the registry to allow for proper booting of the program

Please feel free to confirm or correct me on how this process is supposed to go -- I'm as ready to get this dealt with as I can get, so please reply as soon as possible. Thanks
Davis McCarnOwnerCommented:
First, Windows 2000 will not recognize a drive larger than 2TB or if it has a GPT partition type.  It has to be an MBR partition which excludes O/S's below Windows 7.
You have a working installation of Windows 2000 on the existing drive.  Booting it ought to let you copy any of the files (videos, pictures, etc.) to some other drive just so you have them backed up.
It would be nicest if you could connect the drive as a secondary drive to another, working PC; but, IDE controllers that even work with 7, much less 10, are hard to come by.

PHASE TWO is actually copying what were the working registry files back to where they are supposed to be and then renaming them to match what Windoze wants them to be.  There was an article for doing this on Microsoft.com; but, it got yanked several years ago.
Andre D.Author Commented:
I appreciate your swift reply, Davis McCarn; I wasn't expecting one this soon.

Once again, I sincerely apologize if my last message came off a bit hostile; that was more out of frustration with the issue's latest turn. But I have to voice my appreciation for your acknowledgement of my ultimate goal of making the dysfunctional Windows 2000 installation functional again, which I still think is possible. I've picked up a few tricks for quick fixes over the years, but never had to deal with a repair effort this complex before, but I've been willing to take it on like the old Mustang in Dad's garage. Fatigue is kind of beginning to set in, though, admittedly.

The working installation was the product of a suggestion made elsewhere to conduct the necessary registry fixes by using the healthy OS to 'transplant" the files into the damaged OS, but I never quite figured it out. Also kind of a bitter pill to know that the external drives I mentioned before wouldn't help too much here. I suppose I could rescue some choice files in the interim as you've suggested, but it'd be much better to conduct the fixes that would make it so like the registry error never existed -- hope you can sympathize with that view. I believe I do remember seeing that Windows article once before, either here or elsewhere, but it is quite removed from my recent memory. I doubt an archived version of that article exists elsewhere...
Davis McCarnOwnerCommented:
You really should copy those "choice" files someplace else as the highest priority if you are loathe to go the cloning route to a replacement drive.  Many drives have a bad habit of suddenly becoming catastrophically worse, after which, you would need over $1,000 and a true data recovery lab to recover them.
The problem with that second installation is that none of the original software is installed nor are any hardware drivers or updates that may have been in the original installation.  Additionally, all of the permissions are for different users which is a whole different can of worms.
This article lists the steps and file operations needed to put back what Windows needs to work again on the original installation:
It says it's for XP; but, excepting the fact that your Windows folder is named WINNT, the process is the same.  Pay attention to the lower part of the article; the first part about using the C:\Windows\Repair folder has the same problem as your second installation in that none of the software, updates, or hardware will have been installed.
P.S.  I would be willing to bet that one of those bad sectors caused the SOFTWARE registry hive to be truncated which is what caused your C0000218 in the first place.
Andre D.Author Commented:
The Late "Rowdy" Roddy Piper once said, "As soon as you think you've found the answer, I change the question."

That quote's hung heavy in mind in the last several days...I don't believe in shooting the messenger, so please don't misread my frustration as personal, but I wish that this branch of discussion had come up at some earlier point in the past year; this topic will be a year old next month, and yet this latest prognosis only came up in the last few days, making for new depth in the problem. I'm not sure if you've had the chance to scour the entire thread, Davis McCarn, but there's been a lot of effort and subsequent frustration and disappointment on my part so far, both before and since the thread was opened, so my only regret is that this avenue couldn't have been discussed earlier in the process.

Nonetheless, I'll see what can be done about the matter in the time to come. Judging from earlier posts, it would seem that, in order to back up this drive, I'll have the daunting task of potentially scouring eBay and Amazon to buy a back-up disk drive (preferably USB), that is under 2TB in disk space, and is of MBR partition, according to the specifications previously mentioned. I'm not sure if I could find something like that on my own, so if anyone has any suggestions on where to look, what brand name to use, online tutorials on how to conduct such a drive back-up, how to use the back-up if something goes wrong, etc., please feel free to comment below. I will also be taking a look at the WinHelpOnline link Davis provided; again, I originally came around again in the hopes of asking how to conduct the process with the UBCD4WIN disk I recently managed to acquire, but if the article is just as helpful, I'll try finding the time to understand what's in it.

Which brings me to this bitter piece of news: this may possibly be my last post for the foreseeable future...as I posted a while back at the end of last year, I've been trying to carry out this whole thing while in the midst of some personal matters involving ill elderly members of my family, so I haven't had a lot of free time to address this issue to begin with as I've dealt with their care. Not only that, Experts' Exchange has recently made changes to aspects of its membership policies, so there may be some logistical issues I might have as far as being able to post regularly; with the help of a relative, I've been taking advantage of a narrow free-trial window that is due to end fairly soon, which explains the air of urgency that has come about in my recent efforts to resolve the issue within the past several days. I will do my best to observe whatever progress this thread may make in the time ahead and to get myself engaged whenever and however possible, so I hope to continue to see input from any of you and will respond when I am able. Alerts regarding this subject will appear in my email, and I believe my personal messages will still be viable, so I won't be gone or unreachable indefinitely. Again, I hope everyone here can stay engaged in this discussion, and I hope to come back as soon as I can.

Thanks for your patience, everyone
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.