Jump to content

Install windows on Mac (No bootcamp)

Sergey_Galan

By Sergey_Galan,
in Mac Applications

 Share
79 posts in this topic

Recommended Posts

Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted
9 hours ago, Max.1974 said:

 

Thanks @Sergey_Galan you are the one!! 

 

It's nice use this command, and only works from macOs that you are running !! God Bless you!! Im honored ;) 

I will try find way to put another languages !! My code works fine my friend? 

A program to install Tahoe using a command I found through AI research, and it's available to everyone—just log in and download it. But it installs from your currently running macOS, and in the end, it deletes the old macOS and replaces it with the new one! 

The code used is as follows. There are already variables set, the program has a script, the code can be seen. 

sudo -S "$2"/Contents/Resources/startosinstall --eraseinstall --newvolumename "$3" --agreetolicense --nointeraction --stdinpass

Thank you for finding this code and starting the process.
If you wish, write a warning in your native language, I will then insert it into the code (it's better than a translator).

10 hours ago, eSaF said:

@Sergey_Galan Hi, please forgive me if I misunderstood the action of this App.

My understanding is it does not allow you the choice of what Drive the installation goes.

 

It goes on your current boot Drive and over writes your current MacOS install when you reboot???

Yes, that's right. If you install a new system using an update, there may be various surprises. That's why I always do a clean installation when installing a new system, and then restore the data using Time Machine.
This program speeds up the process, since there is no need to create an installation flash drive.
Later, after testing, I will create a separate topic)))

  • Like 1
Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted (edited)

 I didn't find anything like that.
This is what the startosinstall utility can do 

--license, prints the user license agreement only.
--agreetolicense, agree to the license you printed with --license.
--rebootdelay, how long to delay the reboot at the end of preparing. This delay is in seconds and has a maximum of 300 (5 minutes).
--pidtosignal, Specify a PID to which to send SIGUSR1 upon completion of the prepare phase. To bypass "rebootdelay" send SIGUSR1 back to startosinstall.
--installpackage, the path of a package (built with productbuild(1)) to install after the OS installation is complete; this option can be specified multiple times.
--eraseinstall, (Requires APFS) Erase all volumes and install to a new one. Optionally specify the name of the new volume with --newvolumename.
--newvolumename, the name of the volume to be created with --eraseinstall.
--preservecontainer, preserves other volumes in your APFS container when using --eraseinstall.
--forcequitapps, on restart applications are forcefully quit. This is the default if no users are logged in.
--usage, prints this message.
--user, an admin user to authorize installation.
--passprompt, collect a password for authorization with an interactive prompt.
--stdinpass, collect a password from stdin without interaction.

 

Edited by Sergey_Galan
Anto65
Anto65
Posted
Posted (edited)

Yes , I searched too, there's nothing about it.

I've tried entering different codes several times... like this 

 

sudo -S "$2"/Contents/Resources/startosinstall --eraseinstall --volume /Volumes/Untitled   "$3" --agreetolicense --nointeraction --stdinpass

 

but it doesn't work. I get a prompt with the things , what I can do with startinstall
like in your screenshot
Usage..

 

Anyway, nice work came out... thanks 

 

 

 

Edited by Anto65
Anto65
Anto65
Posted
Posted (edited)

It seems pretty clear to me that the app installs on the volume the user is currently using, creating a new one.
Upon reboot, it will erase that old volume and install the new OS chosen based on the macOS Install app.
The warning is correct, as it deletes all user data on that volume.

 

Spoiler

IMG_20250714_095457.thumb.png.879b1e79fb425b4433a2ce0d4e7128c5.png

 

Edited by Anto65
  • Thanks 1
Anto65
Anto65
Posted
Posted
2 minutes ago, eSaF said:

Thanks Bro, maybe I am stuck in my old way of doing things but as you mentioned, that's the part I am not fond of.

My thinking either right or wrong, the App should have no or very little interaction with your current running Drive to minimised errors

 

Unfortunately, it's not the app, but the script or the "startinstall" command, which was designed that way and doesn't accept other variables
(having tried to modify it several times by adding other variables), e.g., installing on the desired volume and not the current one.
Which is what "createinstallmedia" does, but as we know, it creates the installation USB and doesn't preinstall on the volume... like the Windows Install app does, for example.

Anto65
Anto65
Posted
Posted

🤔

How can i make a preinstall on a macos volume without createinstallmedia ?

 

Spoiler

While createinstallmedia is the officially recommended and simplest method for creating a bootable macOS installer, it's possible to manually create a pre-install volume without it, although it's more complex and potentially error-prone. This involves manually creating a bootable volume, copying the macOS installer files, and setting up boot-related configurations. 
Here's a general outline of the steps involved: 

 

1. Prepare a Volume:
Use Disk Utility to erase a volume (e.g., a USB drive or partition) with the APFS or Mac OS Extended (Journaled) file system.
Give the volume a name, such as "MyVolume".
Ensure sufficient storage space for the macOS installer. A 32GB drive is usually sufficient.

 

2. Mount the Installer:
Locate the macOS installer application (usually in your Applications folder).
Open the installer package (right-click -> Show Package Contents) and navigate to /Contents/Resources.
You'll find the Install macOS application.

 

3. Copy Installer Files:
Copy the entire contents of the /Contents/SharedSupport folder from the installer package to the root directory of your prepared volume.

 

4. Configure Bootability:
This is the most complex part and involves setting up the necessary boot files. You'll need to use Terminal and potentially some specialized tools or scripts to:
Create a boot configuration file (e.g., boot.plist).
Copy kernelcache and other necessary boot files.
Adjust boot arguments.

 

5. Test the Installation:
Restart your Mac while holding down the Option key (or the correct key for your Mac model during startup).
Select the newly created volume as the startup disk.
Follow the on-screen instructions to install macOS.
 

 

LockDown
LockDown
Posted
Posted (edited) 
--newvolumename "$3"

Havent check the code (if there is one)

"$3" must be defined else it will target the current disk.

Just like @eSaF observation.

 

Update: checking the script, "$3" is going nowhere but in the current disk

Thats how i understood it at least as source is not available

Edited by LockDown
Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted 
sudo -S "$2"/Contents/Resources/startosinstall --eraseinstall --newvolumename "$3" --agreetolicense --nointeraction --stdinpass

No, you don't need to try this script in the terminal. ))) I just showed what commands are used. And $1, $2, $3 are variables from the user passed to the script.

Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted
26 minutes ago, LockDown said: 
--volume /Volumes/XXX --eraseinstall --newvolumename "YYYY"

--volume will be the target drive

--newvolumename will only be the name of the volume you specified if you add  --eraseinstall option

Like here:


Unfortunately, it doesn't work like that. If you search the internet, it probably worked before.

  • Like 1
Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted
6 hours ago, LockDown said:

--volume is not documented but still works to select target drive.

It cannot be used with --eraseinstall & --newvolumename because both refers to current booted drive

Screenshot 2025-07-15 at 8.13.41 AM.png

Screenshot 2025-07-15 at 8.37.34 AM.png

Oh, I see this command works for you, it still doesn't work for me. Describe in more detail what system you used, what format the volume is in, etc.

  • Like 1
LockDown
LockDown
Posted
Posted (edited)

I have tested it on both sequoia and tahoe environment. Target drive should already be a APFS.

You can do this in script before the startosinstall command

 

Your app might work if you exclude --eraseinstall --newvolumename (those wont work with --volume flag)

 

Also Change the function of the "please create volume name" to a drop down menu where you can select target drive which is for the APFS formating and --volume

 

Edited by LockDown
  • Like 2
Sergey_Galan
Sergey_Galan
Posted
  • Author
Posted
1 hour ago, LockDown said:

I have tested it on both sequoia and tahoe environment. Target drive should already be a APFS.

You can do this in script before the startosinstall command

 

Your app might work if you exclude --eraseinstall --newvolumename (those wont work with --volume flag)

 

Also Change the function of the "please create volume name" to a drop down menu where you can select target drive which is for the APFS formating and --volume

 

Maybe that's why the --volume command doesn't work for me
I have SIP enabled https://pikeralpha.wordpress.com/2017/10/11/sip-requirements-for-startosinstall-volume-path/

  • Like 1
LockDown
LockDown
Posted
Posted
7 minutes ago, Sergey_Galan said:

Maybe that's why the --volume command doesn't work for me
I have SIP enabled https://pikeralpha.wordpress.com/2017/10/11/sip-requirements-for-startosinstall-volume-path/

 

19 hours ago, LockDown said:

--volume "$3" 

Using that probably requires SIP disabled

 

  • Like 1
  • Thanks 1
  • 4 weeks later...
  • 1 month later...
 Share
Go to topic listing
×
×
  • Create New...