This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am trying for the first time to boot my Windows 8.1 laptop from the internal CD-DVD drive. I have a bootable CD in there, and yes, I do have the bios set with CDROM drive as first in the list to boot from. But when I try to boot from the CD, it won't boot, instead the computer gives me this message:
"ATAPI CDROM has been blocked by the current security policy."
(Its actually a DVD drive.) All it lets me do at that message is hit the Enter key to OK the message, and then it boots from the hard drive.
I have no idea where "security policy" settings are or what they are set for. What do I have to do to get this to boot?
This is a Gateway laptop, 2.2 MHz Intel Pentium processor, 4 GB RAM, 64 bit OS, with Windows 8.1 fully updated, and Windows Defender running and fully updated.
I have already looked everywhere I can find, but nothing seems to address this message or issue, as follows:
*I went to Help menu to look up "Security Policy." While the computer is giving me the message about "security policy," the Help menu has no idea what "security policy" is, it just comes up blank!
*I went to Control Panels/System and Security/Action Center/Change Windows Settings/Smart Screen/... All I found in there that might be involved is a setting to block anything downloaded from the Internet until I give administrator access. Well, the booting issue didn't allow me to give administrator access (yes, I am the administrator) when I tried to boot, I only could hit the enter key to OK. Nonetheless, I changed to: notify me but proceed (not a quote).
With that, I tried again, but it still would not boot from the CD, got the same message, so that setting is not it. I changed the setting back.
I see no other setting there that could be related by even a stretch. And the control panels should be dealing with the OS anyway, and this is happening while trying to boot from the OS on the CD, not the hard drive. That is, this is something in the root.
*I then went into bios area (UEFI Firmware) by sweeping in from the right and into Settings/Change PC settings ..., and found a tab in bios for Security. Looking there, there is a list of things, but it lets me access only "Supervisor Password." It was currently set as "clear," meaning no password. I left it as that -- surely I can't need a password just to boot from a CD, and the message I got in trying to boot from the CD did not allow me to enter a password.
Other settings in the Security tab were not accessible. The only ones they included that might be remotely related were:
*Password on Boot, which was set as no password. But again, the message I get with this issue does not ask for nor allow me to enter a password.
*Secure Boot Mode: Standard (It does not let me access to change that.)
Some others also were in the list that are not worth listing, not even vaguely related.
I then went into some other things elsewhere in the main settings called Startup Settings. The only thing in there that sounded the least bit vaguely related was "Enable boot logging." I punched F2 to go into that, but the machine instead restarted, and did not start from the CDROM, same message again. I went back to it, and it is still listed as Enable boot logging, does not instead say Disable - so I don't know if anything even got changed. I did not touch it again, left it as-is.
So, that's it. I've checked all the settings I know about. Nothing about this bit about "ATAPI CDROM has been blocked by current security policy."
I tested with two DVDs that I have booted from in the past on other Windows machines -- they also would not boot, but they did not give me that message.
I note, all three CDs/DVDs are being read fine by the DVD drive once the machine is booted in Windows 8.1 from the hard drive - so the issue is not that the DVD drive can't read the disks.
Where is this "security policy" set?! What do I need to do to get this to boot from the CD?
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi,
So everything is back to normal... or at least working to your satisfaction ?
You seem to know more about manipulating your email than I do, but though I may be able to help by describing what my screen looks like !
I know how that kind of conversation goes... Not so much with Microsoft, but with my internet provider sometimes..
Hi,
I considered the idea of deleting #1 and #2 and moving the 128MB partition to the very beginning of the drive... The problem is that I have never done that, and don't know if that is OK, or if there would be some type of adverse consequences...
The safest thing to do is leave it alone...
That is correct that the File Table needs to be there... or somewhere...
Most GPT drives I have seen usually have it at the very start or end of the drive... Then everything in between is free to be manipulated... For some reason Gateway didn't see fit to do that... I don't have a clue as to why...
I don't know how Partition Wizard rearranged your partitions either... Again, I can't duplicate that... That is why I suggested to Delete the partitions and then expand the #3 into the Unallocated free space, or manually resize the partitions one at a time as I had mentioned... It is too late now to do anything about it...
My guess is that whatever Partition Wizard did may cause a problem if you try to shuffle things around some more... My thinking is that if you delete #5 first it will undo anything that could be a problem... Delete the link or whatever... Then #3 would hopefully be back to normal, or at least in a condition it can be resized again without issues... Obviously, #4 would need to be deleted as well...
You use the term KILL a lot... is that term that Partition Wizard provides as an option, instead of Delete, or is that a Mac term ? I wouldn't want to confuse them...
The reason for Deleting\Killing the partition rather than Expanding, is that Partition Wizard may try to keep the files that are already in the partition.... OR simply not allow you to expand because there is a file there...
As far as Acronis goes... I doubt that Acronis Backup does anything when you are booting from a CD... Acronis Backup won't do anything regardless, if you haven't turned it on and set it up...
Acronis Backup makes Incremental Images... In other words, it only reimages the part of the HDD that has changed... Somewhere along the line if you want to restore an image, or save the image to a external drive or something, Acronis needs to assemble all of the pieces... That is probably the reason for Acronis Backup using extra space...
That is also the exact reason I don't use Acronis Backup, Windows File History, System Restore, or anything similar... I have only installed Acronis on a OS that I was going to delete anyway... Just long enough to create the bootable CD and Flash Drives...
I invest in external HDDs, or extra internal HDDs to do FULL IMAGES... I do them at my convenience, rather then when something else decides to use resources I need elsewhere... It requires that I keep a close eye out for deals on HDDs !!!
As an example using what you have done so far, I would have a minimum of six, and possibly more...
Win 8 before updates,
Win 8 after updates and before Win 8.1,
Win 8.1 immediately after the upgrade completes,
Win 8.1 after updates,
Win 10 immediately after the upgrade completes,
Win 10 after any updates...
Sorry about the rambling... Just wanted to mention my method, as opposed to what you read on the forum...
Hi,Hi,
I have posted the question on Acronis forums. Will let you know if and what I hear. I did a search of Acronis Knowledge Base first, tons of pages, much of it not even related to what I searched for, and the few that were related were not quite on the mark. But many people do seem to have an issue of lack of enough space.
However, I did find some saying that Acronis Backup -- and I'm using Acronis True Image 2016, not Backup -- puts a bunch of temp files on the destination disk while it is going through that time getting ready to write the image. It seemed to suggest that can be as much as 20% of the free space, and for 99.5 GB, that would be 20 GB. That could make an 83 GB Image need 103 GB of space; but a 72 GB Image would need only 92 GB, so should fit on mine, but doesn't. But I'm not sure that applies to True Image.
I found another on True Image item about not enough space, but it did not mention that temp file writing, and the rest did not help any. And, they were showing page views in that True Image 2016, but they didn't look like my page views.
Don't get bothered by any of this yet -- let me get something more certain and definitive.
Below,again, mine is in Capital:
If that 128MB partition was not a file table, I would think it could be like you suggest...
Expand it into #1 and #2...
But even then, I doubt it would be possible to expand everything into #3... The File Table would no longer be a separate and distinct area separate from the files it is logging...
I DIDN'T MEAN EVERYTHING, ONLY THE FREE SPACE. THUS, THE 128 MB WOULD BE LEFT BEHIND IN THAT PARTITION. YOU SAID I HAVE TO HAVE AT LEAST ONE PARTITION THERE, ALTHOUGH MAYBE YOU SIMPLY MEANT WE HAVE TO HAVE A TABLE PARTITION.
How would you modify your drive if the File table was inside what is being modified ?
It is separate for a reason...
ABOVE
In a way you are confusing what can be done with partitions with what could be done with a folder, for instance... It doesn't work that way...
It would be like trying to store your image on the same partition it was made from..
If you were to try expanding #5 into #4 at this point, it would probably just cause more trouble... This is because it would mess up the link from #3 to #5 most likely...
I WAS MENTIONING THAT. WILL IT LEAVE THE LINK BUT THE LINK IS DEAD, BUT IT IS THERE CONFUSING THINGS? OR MAYBE WE JUST DON'T KNOW.
You could probably delete #4 and #5 and expand #3 into the space... which is what I have been suggesting... But I also can't guarantee that will work because of the link...
SO, KILL THEM, THEN EXPAND? SO, I DON'T NEED TO EXPAND INTO THEM, JUST KILL AND THEN EXPAND? OK.
I tried very hard when you first started mentioning doing this, to explain to you that it was not possible to expand #3 into #5, or use part of the space from #5 to add to #3 because #4 was in the way...
A partition requires a continuous, uninterrupted area to function properly...
It is like a line you draw on a piece of paper... It needs to be continuous...
You can't erase something out of the middle and stick something else in there, nor can you skip a space at the end of the line, and then start it up again... It would not be continuous and uninterrupted...
YES TO ALL THAT. AND I WENT TO IT TO DO IT AS YOU SAID, INTO 4, THEN INTO 3. BUT PARTITION WIZARD OFFERED THE STRAIGHT FORWARD WAY -- ALTHOUGH I DON'T KNOW THAT THEY DIDN'T ACCOMPLISH THAT BEHIND THE SCENES BY GOING TO 4 THEN GOING TO 3, I DON'T KNOW HOW THEY DID IT. AND PARTITIONS IS WHAT THEY ARE SUPPOSED TO SPECIALIZE IN, THEY SHOULD KNOW HOW TO DO IT RIGHT.
I am sure there are people that know more about partitioning than I do... especially concerning GPT drives...
But when it comes to what works and what doesn't, I'm sure you are familiar with the term UNSUPPORTED... As in it might be possible for to do something in some fashion, but that fashion is not supported by everything and everyone... Simply because it is not the "Normal\Standard" method....
THAT'S WHY I WANTED TO SEE IF PARTITION WIZARD COULD DO THE IMAGE WHERE ACRONIS COULD NOT, OR IF THE OS COULD. UNFORTUNATELY, PARTITION WIZARD DOESN'T DO IMAGES, ONLY MIGRATES FILES.
I tried very hard to explain to you that it was not possible to expand #3 into #5, because #4 was in the way...
Either you did this before you read my reply, or you ignored my reply.... Now all this time later we are still dealing with the repercussions... I have already said that it may not be possible to undo the damage...
SEE ABOVE.
Everything I have since suggested has been responded to by countless alternative hypothetical solutions... Most of which I have already explained won't work, or are a very bad idea...
I'VE ONLY RAISED IDEAS THAT HAD NOT YET BEEN RAISED. I VERY MUCH APPRECIATE ALL YOU HAVE SAID.
Hi,
If that 128MB partition was not a file table, I would think it could be like you suggest...
Expand it into #1 and #2...
But even then, I doubt it would be possible to expand everything into #3... The File Table would no longer be a separate and distinct area separate from the files it is logging...
How would you modify your drive if the File table was inside what is being modified ?
It is separate for a reason...
In a way you are confusing what can be done with partitions with what could be done with a folder, for instance... It doesn't work that way...
It would be like trying to store your image on the same partition it was made from..
If you were to try expanding #5 into #4 at this point, it would probably just cause more trouble... This is because it would mess up the link from #3 to #5 most likely...
You could probably delete #4 and #5 and expand #3 into the space... which is what I have been suggesting... But I also can't guarantee that will work because of the link...
I tried very hard when you first started mentioning doing this, to explain to you that it was not possible to expand #3 into #5, or use part of the space from #5 to add to #3 because #4 was in the way...
A partition requires a continuous, uninterrupted area to function properly...
It is like a line you draw on a piece of paper... It needs to be continuous...
You can't erase something out of the middle and stick something else in there, nor can you skip a space at the end of the line, and then start it up again... It would not be continuous and uninterrupted...
I am sure there are people that know more about partitioning than I do... especially concerning GPT drives...
But when it comes to what works and what doesn't, I'm sure you are familiar with the term UNSUPPORTED... As in it might be possible for to do something in some fashion, but that fashion is not supported by everything and everyone... Simply because it is not the "Normal\Standard" method.....
I tried very hard to explain to you that it was not possible to expand #3 into #5, because #4 was in the way...
Either you did this before you read my reply, or you ignored my reply.... Now all this time later we are still dealing with the repercussions... I have already said that it may not be possible to undo the damage...
Everything I have since suggested has been responded to by countless alternative hypothetical solutions... Most of which I have already explained won't work, or are a very bad idea...
Hi,
Again, my responses in capital. Thanks for this further explanation. Let us take a breather for the moment though -- I'm not going to do this today yet, and I can't tomorrow anyway. I think today I will scout, maybe in an Acronis forum, to see if someone very unlikely has some special way to work around this, but I doubt it. I figure can't hurt to ask, although I think you've already said a lot more than anyone there will or can. Still before I do something irretrievable, I should at least look first, so I don't later kick myself for not having done so -- just a look before you leap thing. Then, when I surely don't find anything, I am figuring I will kill out partition #4, and then see if, without it between #3 and #5, I can do the image. Maybe I will expand #5 into an empty #4 first, so there is no leap over a partition or space. If the imaging still doesn't work for lack of space, then kill #5. And hope that eliminates any link, rather than leaving a confusing dead link behind, and that I can do the image. I still worry I won't be able to, since I can't even do the 71 GB Image, for which there is no dispute I should have plenty enough empty space for but can't get done now -- that is quite worrisome:
You had a ? mark after your statement concerning the 128MB partition...
YES, THAT WAS ASKIGN IF YOU AGREED WITH WHAT I PROPOSED, WHICH WAS TO KEEP THAT PARTITION AS THE FIRST PARTITION, KILL THE OTHER TWO OUT. YOU HAD INDICATED YOU DIDN'T KNOW WHERE THAT HIDDEN PARTITION WAS, BUT I DID, AND IT WAS IN THE APPROPRIATE SPOT TO DO THAT. BUT NOW YOU ARE EXPLAINING THAT PARTITION WON'T MOVE OVER TO THE BEGINNING, SO THAT OTHER SPACE FROM #1 AND #2 WILL BE LOST ANYWAY.
Technically it is not a indexing log... it is more accurately a file table...
On a MBR drive this would be called a MFT, or Master File table...
OK. AND SEEMS TO ME I'VE HEARD THAT TERM "MASTER FILE TABLE" BEFORE SOMETIME.
As I said... the space that was moved from #5 to #3 is still PHYSICALLY on #5...
YES, THAT IS WHAT I NOW UNDERSTAND YOU SAYING. EARLIER YOU HAD PHRASED IT SOMETHING LIKE "WHETHER MOVED OR LINKED," WHICH IS A PHRASE OF UNCERTAINTY BUT NOTING THAT DIFFERENCE DOESN''T MATTER.
That is why I first mentioned sliding #4 into #5 to make #4 larger and #5 smaller...
Then slide #3 over into #4 to make #3 larger.... So that all of the added space would be physically part of #3... but you did it differently...
I WAS LOOKING FOR A WAY TO DO THAT WHEN I WAS IN PARTITION WIZARD, AS I WENT THERE THINKING THAT IS THE ONLY WAY IT CAN BE DONE. I DID NOT SEE A WAY, BUT I STOPPED LOOKING WHEN I SAW THE WAY TO GO DIRECTLY FROM #5 TO #3, SO MAYBE THERE IS WAY TO DO AS YOU ARE SAYING TOO.
I NOTE, I DON'T KNOW WHAT PARTITION WIZARD DOES BEHIND THE SCENES TO DO IT -- IT TOOK MORE THAN A HALF HOUR FOR IT TO DO WHATEVER IT IS IT DOES. IT SAYS IT IS "MOVING" THE SPACE. BUT MAYBE IT ISN'T MOVING IT, MAYBE IT IS ONLY LINKING IT (I THINK THAT WOULD BE BAD COMMUNICATION AGAIN, THEY SHOULD SAY THEY ARE PROVIDING A LINK TO IT OR SIMPLY ACCESSING THAT SPACE, NOT SAY "MOVING" IT IF THEY ARE NOT MOVING IT. IF THEY HAD, I WOULD HAVE ASKED YOU BEFORE OPTING FOR THAT -- IN FACT, I WOULD NOT HAVE WANTED THAT). YES, MAYBE THEY DID SIMPLY LINK, NOT MOVE IT AS THEY SAID. BUT SINCE THEY DON'T EXPLAIN, I CAN'T KNOW THAT THEY DIDN'T DO A PROCESS OF MOVING IT THROUGH #4 AND THEN TO #3 EITHER -- IT TOOK LONG ENOUGH FOR THAT. THEY DON'T EXPLAIN WHAT THEY DO, SO I CAN'T KNOW. THEY SIMPLY SAY THEY MOVE IT.
It doesn't matter that something SEES the space... The sectors on a HDD are numbered... The fact that Partition Wizard used some trickery to LINK two different partitions doesn't change the fact that the sector number sequence is out of whack...
YES, IT MIGHT VERY WELL HAVE LINKED IT, AND WITH THE TROUBLE WE ARE HAVING, THAT SEEMS VERY LIKELY WHAT THEY DID. AND THEN ACRONIS CAN ONLY HALF READ THAT, SHOWING IT IN THEIR CHART AS MOVED TO #3, BUT NOT FINDING IT ON #3 WHEN IT TRIES TO DO THE IMAGE. SO MAYBE IT CREATES SOME INDICATOR THAT AFFECTS THE READING FOR THE CHART, BUT, THE ROUTE TO GET TO THE SPACE IS STILL INTERFERED WITH BY THAT NUMBERING SYSTEM YOU MENTION, AND ACRONIS CA'NT FOLOW WHATEVER IT IS THAT PARTITION WIZARD DID WITH THAT NUMBER SYSTEM.
It is like expecting Acronis to automatically put part of the image on one HDD, and the rest on another HDD... It doesn't work that way, and that is what you are not understanding... I don't know why the smaller 71GB image won't fit...
WELL, ACTUALLY, ACRONIS INDICATES IT DOES AND WILL AUTOMATICALLY SPLIT FILES AS NEEDED TO FIT SPACE. YOU HAVE TWO OPTIONS ABOUT THAT, BUT THER E IS NO OPTION NOT TO LET THEM BE SPLIT. BUT THAT WOULD BE WITHIN THE IMAGE, NOT MAKING TWO PARTIAL IMAGES. (ALTHOUGH ACRONIS ALSO WILL MAKE THE IMAGE TO A SET OF DVD'S, PROBABLY 20 IN ALL, AND THUS LINKING ONE DVD TO THE OTHER DOWN THE LINE -- SIMILAR TO LINKING FROM ONE PARTITION TO ANOTHER -- BUT THIS IS SIMPLY ACADEMIC FOR THIS DISCUSSION.)
You are also misconstruing what I am talking about when I say the 128MB type partitions are normally put first and last... That comment can be interpreted two ways...
I intended one meaning, and you are thinking of the second...
My point was that it is usually\best at the very beginning of the HDD space or the very end of the HDD space... By your interpretation, it can be made #1... which is true, but it is not at the beginning of the HDD...
As a result of this, the 1GB space between the beginning of the HDD and the 128MB partition can't be used as part of the #3...
OK, YOU SAY IT CAN'T BE MOVED -- I UNDERSTOOD YOU SAYING THAT LAST NIGHT. AT LEAST NOT SIMPLY BY KILLING OUT #1 AND #2. JUST OUT OF CURIOSITY, CAN'T THAT 128 MB HIDDEN PARTITION BE EXPANDED INTO #2, AND THEN #2 EXPANDED INTO #1, AND THEN #3 EXPANDED INTO THE EXTRA EMPTY OF WHAT IS NOW THE ONLY PARTITION TO ITS LEFT? (OF COURSE, I WOULD EMPTY OUT #1 AND #2 FIRST, LEAVING EMPTY PARTITIONS) ITS NOT A SIGNIFICANT ENOUGH AMOUNT OF SPACE TO WORRY ABOUT -- BUT GETTING RID OF UNNEEDED THINGS IS CLEANER. OF COURSE, IF I CAN'T DO WHAT I JUST PROPOSED, THEN WHY BOTHER DOING ANYTHING WITH #1 AND #2, JUST LEAVE THEM AS IS.
I should point out that everything I am describing concerning partitions, is the way MBR Drives work... and I know GPT Drives work a bit differently...
OF COURSE, MINE IS GPT.
So I can't say 100% for sure that trying to combine #3 with the 1GB of free space would cause a problem... I don't know for sure...
I am trying to prevent you from causing your 88GB Win 8.1 image to become useless.. I don't think trashing 1GB is a big deal as compared to the possibility of your 8.1 image being useless... Better safe than sorry...
YES! THIS IS WHY I'M NOT RUSHING AHEAD!
