Win10 x64 1703: error 0x80070001 on winupdate/store as long as ImDisk...
Status: Inactive
Brought to you by:
w77
Menu
▾
▴
#9 Win10 x64 1703: error 0x80070001 on winupdate/store as long as ImDisk Toolkit is installed
This started with the update to 1703. After installing ImDisk Toolkit, everything seems to be working fine. However, after a reboot, any attempts to install windows or app updates results in error 0x80070001. Not setting the user or system TMP variables to the ramdisk does not seem to make any difference. Uninstalling ImDisk Toolkit and rebooting restores normal operation.
Things that might be of relevance:
the PC is a work PC part of a domain
the PC is getting updates via a local windows update server
It seems that what triggers the issue is the creation of the ramdisk itself (perhaps because then the imDisk driver is loaded?). I just disabled re-creation of the ramdisk on startup and the update is working without uninstalling the toolkit.
I didn't yet try this build of Windows, but a quick search suggests that it may be related to the file system. If the ramdisk is formatted with FAT or NTFS compressed, it could be enough.
Did you try to use NTFS without compression?
I actually never used compression before. Usually, I use NTFS, but I also tried FAT32 the last time I made the ramdisk, so that might not be it. I've found someone mentioning that the old ImDisk driver was causing this on an earlier win10 build [1], so maybe the issue re-surfaced with the current version?
[1] https://www.tweaking.com/forums/index.php?topic=5240.0
Unlike it is said in that topic, Virtual Floppy Drive has nothing to do with the ImDisk driver. The latter was first released in 2007, while VFD was released in 2003.
As you are the first one to report this issue, I suspect that it is related to "the PC is getting updates via a local windows update server".
In any case, I am not very optimistic about fixing this issue...
Well, the issue persists with 1709 for this PC as well. The confusing part is that it used to work with earlier win10 builds and the same configuration otherwise. I guess any kind of RAMdisk on windows is just wonky as always.
I just made a few tests with the build 1703 in a virtual machine and Windows Update seems to be working fine, even with the TMP variables pointing to the ramdisk, except for one update (Windows Defender - KB4052623). The error is 0x80070643.
My feeling is that Windows Update is more and more buggy with each new version/build of Windows...
I get 0x80246013 if I set system temp to the ramdisk and unmount the disk
I have the same issue; if I unmount the drive windows update/store works fine.
Repeatable accross every win 10 build I've tried and with multiple clean installs
The ram disk is 10gb, dynamic[automatic], ntfs, with temp parameters set and awe.
I use to use softperfect ramdisk; but the driver is stuck and won't let me completely delete it; and it won't let me reinstall it; so thats why I started using this.
Mostly using this to reduce drive writes; especially helps during some poorly optimized games .
Hope somone can make imdisk windows 10 compatible
Specs Windows 10 x 64 enterprise 1709 [currently 17083.1000]
i7 6700k
2x16gb Gskill 3200mhz ddr4 ram
asus z170a [& gigabyte z170mx gaming 5]
GTX 1080 Asus strix
I don't believe specs would be relevant; unless there's some incompitiblity with high frequency memory or skylake...
Still have the issue; any update?
A Microsoft's article says that this error number (0x80070001) comes from Windows Backup, which can be called by Windows Update.
Windows Backup seems not to like some reparse points.
Did you create junctions or symbolic links to the ramdisk?
Do you use a folder as mount point for the ramdisk, instead of a drive letter?
Hello.
I found, that this error happens, only when I set ramdrive letter before main disks letter ( in my case I use B: for it). When I have changed RamDrive letter to F: (after C:, D:, E:, used by hdd and dvd), then Windows Update and Microsoft Store apps starts work normally.
Nice find! I was able to reproduce the issue with the ramdisk on B:. Then the error disappeared when I changed the letter to R:. Thanks a lot for pointing that.
I can do nothing except to add a warning message for the A and B letters, but this bug could be fixed anytime. So for now, I think to leave things as they are.
I could also put that somewhere in a "known issues" list...
unfortunately this is not my case. i use R as the ramdisk drive letter and not able to get certain windows update installed. i have tried to change those temp/tmp path but still no luck. the only way is to set all temp/tmp path to a physical disk and reboot to install the updates
btw i have set all temp/tmp path to R:\Temp with junctions pointing to it as well like c:\temp etc
wanted to report this months early but due to some problems i couldnt get my account verified. sorry about that
I don't think this is related to the issue we are discussing here.
It seems that some updates are still relying on a permanent Temp folder.
Any competent developer knows that a Temp folder can be cleaned during a reboot, and even at any time. But not Microsoft.
but before i switched to ImDisk, there's no problem.
yeah i think it's looking for a temp folder located on a 'physical' disk, which the previous ramdisk software allows to treat the ramdisk as a physical one. is it possible to add this option also to ImDisk?
Wether it be a; G or z; the error persists
I agree with tt.johnsson here. I don't think this could be related to "reboot-persistent" temp directories, it is more likely related to some compatibility problems with the disk emulation. For temp directory, I have used another RAM disk driver that emulates complete disks in Windows 10 for a long timeand I have never had a problem with Windows updates.
any update?
No, this is probably not possible to solve using ImDisk as the virtual disk driver. It would require either that Windows Update install routines change the requirements for the disk driver that holds the temp directory or a virtual disk driver that emulates complete disks with Volume Mount Manager integration instead of the more "simple" way that ImDisk is designed.
I also had 0x80070001 errors when I was using a RamDisk with drive letter B: and with my user temp dir to B:\Temp. (I never modified the System temp var; it's still %SystemRoot%\TEMP)
ImDisk ToolKit 20170706 (NTFS, Allocate Memory Dynamically, launch at Windows Startup, Create TEMP Folder; nothing Advanced) I'm currently running 64-bit Windows 10 Enterprise 1803 (OS Build 17134.228)
Introducing a new variable seems to have resolved my Windows Update difficulty:
I ran "SystemPropertiesAdvanced.exe" from an elevated command prompt then clicked Environment Variables button.
Under User variables box, I set "TEMP" and "TMP" to have the value "%RAMDRV%\Temp"
* Under System variables, I created "RAMDRV" with a value of "B:"
Running "C:\Program Files\ImDisk\RamDiskUI.exe" I set TEMP Variables
TEMP: %RAMDRV%\Temp
TMP: %RAMDRV%\Temp
I rebooted for changes to take effect. However, I haven't tried changing the SYSTEM temp variables.
Thanks for the tip; I tried this; to no avail [at least in the windows store]; as there's no windows update currently available.
"A:\Temp. (I never modified the System temp var; it's still %SystemRoot%\TEMP[I have modieifed it before however it seems to have reset itself at some point])
ImDisk ToolKit 20170917 (NTFS, Allocate Memory Dynamically, launch at Windows Startup, Create TEMP Folder; nothing Advanced) I'm currently running 64-bit Windows 10 Enterprise 1809 (OS Build 17754.1)
Introducing a new variable didn't resolve my Windows Update difficulty:
I ran "SystemPropertiesAdvanced.exe" from an elevated command prompt then clicked Environment Variables button.
Under User variables box, I set "TEMP" and "TMP" to have the value "%RAMDRV%\Temp"
* Under System variables, I created "RAMDRV" with a value of "A:"
Running "C:\Program Files\ImDisk\RamDiskUI.exe" I set TEMP Variables
TEMP: %RAMDRV%\Temp
TMP: %RAMDRV%\Temp
I rebooted..."
Last edit: Chaython Meredith 2018-09-24
This issue still exists!
Can't install a .msi , nor windows update, nor windows store when imdisk is enabled.
Only solution is to disable it sign out and back in, download the updates etc then restart and enable ramdisk again...
Months to find out that ramdisk was the cause of updates not working. PLEASE put a warning when choosing A or B letter. Moved mine away from B and problem 0x80070001 was solved.