click-click

Member
  • Content count

    118
  • Joined

  • Last visited

Community Reputation

1 Neutral

About click-click

Profile Information

  • Country

Recent Profile Visitors

220 profile views
  1. This happened using the latest version of WinNTSetup (3.8.6.0). On my W7 (Starter) system, I created a VHD via Disk Management. Initialized the disk and selected volume type 'New Simple volume'. I then mounted the volume and started WinNTSetup. Select location of Windows installation files: R:\Win10_1511_2_English_x86\install.wim Select location of the Boot drive: c: (Using current boot drive since VHD not allowed) Select location of the Installation drive: c:\W10_Home.vhd Edition: Windows 10 Home Once started, I got the standard message about changing the boot code. I selected BOOTICE in order to later see the boot info. Everything ran to near completion when I got the mentioned errors which most likely came from W7 since you don't use such a dialog . If I run the same configuration and select 'do not change boot code' I do not get any errors and can install and activate W10. I did notice that even though I selected 'do not change boot code', WinNTSetup shows a msg '"changing boot code" at the end of the setup stage.
  2. I just tried installing W10 to a vhd from an active system and towards the end, I see the following msg: The update operation may be unreliable since the volume could not be locked. Continue anyway? If I select yes, I get Write file failed! Access is denied. I'm not sure if I'm following the correct procedure for installing to a vhd. I've always used an empty partition up to now. Anyone know why I'm getting an error?
  3. Makes sense. All I ever added was the PosReady key to keep the updates coming. I never knew that the windowsembedded key served a similar purpose.
  4. Where did the windowsembedded key come from? I don't see it on a normal XP SP3 Pro install.
  5. Does anyone know how to temporarily change the service startup type for msmpsvc (Microsoft Antimalware Service) via the registry or otherwise? Everything I've tried gets access denied. Microsoft made some changes to the protection scheme for MSE. Running Regedit as TrustedInstaller doesn't work.
  6. I think WinNT has more that enough options in it as is. I don't always update when options get added if I can manage without them. The more you add, the more work it is for the developer and the more complicated it gets to maintain. Bite the bullet and use your three screw drivers.
  7. I can live with WU taking longer searching for updates as long as it does this in a reasonable way. What I can't live with, is the amount of CPU it uses to carry out the task. On a dual core T2300, it uses 50-51% CPU during the whole process which is unacceptable. If the system is fully up-to-date, WU is much quicker and If you are missing any updates, it is slow. Vista has the same problem. Win8.1 is better, but they all suffer the high CPU usage.
  8. It's off and on. Seems to be a website problem. [Error number: 0x8DDD0010]
  9. MU website is broken again after installing MS15-106 for IE. I Uninstalled it and the problem went away. Anyone else? Cumulative Security Update for Internet Explorer 8 for WEPOS and POSReady 2009 (KB3093983) Edit: It's not the update. Tried MU again and it's no longer working.
  10. Do you mean sysprep/capture the drive from a winntsetup install, or do I have install from the CD?
  11. I had to reinstall Vista on one of my partitions (Drive0 P0=XP, P1=Vista and Drive1 P0=W7 P1=W81 P2=W10) and I can't get it to boot as the c drive. Even though mount installation drive as C is set, the system drive keeps ending up being assigned to D. Volumes 0-6 are on Disk0 and volumes 7-10 on Disk1. Below is a list of volumes from setupcomplete.cmd. Not sure if I'm doing something wrong. i don't have this problem with the other systems because they all boot as C. Is there any way to change the Vista boot drive back to C ? Microsoft DiskPart version 6.0.6002Copyright (C) 1999-2007 Microsoft Corporation.On computer: 2082-52G Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- ------- Volume 0 K WinXP_Pro NTFS Partition 20 GB Healthy Volume 1 D Windows Vis NTFS Partition 20 GB Healthy System Volume 2 E SYS_Misc NTFS Partition 20 GB Healthy Volume 3 F Temp NTFS Partition 8 GB Healthy Volume 4 G Make_PE NTFS Partition 4511 MB Healthy Volume 5 H SysInstall NTFS Partition 67 GB Healthy Volume 6 I Lenovo NTFS Partition 10 GB Healthy Volume 7 C Windows 7 NTFS Partition 20 GB Healthy Volume 8 L Windows 8.1 NTFS Partition 20 GB Healthy Volume 9 M Windows 10 NTFS Partition 20 GB Healthy Volume 10 J SysMaint NTFS Partition 215 GB HealthyLeaving DiskPart...
  12. When I install XP from a source that has an $OEM$ dir with cmdlines.txt and ROE.exe, the files don't get copied to the target drive after running WinNTSetup. Is this correct?
  13. I hope it wasn't too much work. I would have accepted 'no longer supported' too. Thanks ... BTW, does WinNTSetup support upgrading on top of an installed system? For example, upgrading a Win10 build to a newer Win10 build without doing a clean install. All of my WinNTSetup procedures till now have been fmt -> install fresh, so I 'm not sure if upgrading is supported.
  14. Still getting same error using XP with v3.8. Installing Win10 using Win7 doesn't give you that error.
  15. I see someone had this problem before and it was related to XP. BCDBoot XP compatibility was put back in as stated here. Has XP support for this been removed again? I'm using V3.7.9. I know XP is EOL, but I'm using the POSReady 2009 version which doesn't go EOL until 2016